grass @8.4.1: configure: error: *** Unable to locate OpenGL library.

[news24lor]

I read the config.log and saw that the problem is the lack of the AGL framework.

In macOS Tahoe, this framework has been removed (-framework AGL), so it must be removed in Grass in the Build Settings.

I hope that will be sufficient.

[jmroot (Joshua Root)]

This was #73164 but apparently the committed fix didn't work. Please attach the config.log and main.log.

[nilason (Nicklas Larsson)]

​https://github.com/macports/macports-ports/pull/29955 will fix this properly.

[news24lor]

There are new problems.

I have attached the two log files.

[nilason (Nicklas Larsson)]

​This should be solved now, please close this ticket.

[ryandesign (Ryan Carsten Schmidt)]

You are patching both configure and the file it's generated from, configure.ac. Please patch either the generated files or the files they're generated from but not both, and arrange for the port to either regenerate the generated files (e.g. run autoreconf) or not accordingly.

Existing patchfile 01_patch-dyld-link.diff patches configure (and not configure.ac), therefore all other patchfiles must match this and also patch configure (not configure.ac), otherwise the effects of this patch will be lost when automatic regeneration occurs.

[ryandesign (Ryan Carsten Schmidt)]

You are patching both configure and the file it's generated from, configure.ac. Please patch either the generated files or the files they're generated from but not both, and arrange for the port to either regenerate the generated files (e.g. run autoreconf) or not accordingly.

Existing patchfile 01_patch-dyld-link.diff patches configure (and not configure.ac), therefore all other patchfiles must match this and also patch configure (not configure.ac), otherwise the effects of this patch will be lost when automatic regeneration occurs.

[news24lor]

The patch works and Grass installs perfectly.

The problem is solved.

Thank you.

[jmroot (Joshua Root)]

Ryan's comment is correct and should be addressed, however the issue reported in this ticket is no longer happening, so I'll close it.

[nilason (Nicklas Larsson)]

Replying to ryandesign:

You are patching both configure and the file it's generated from, configure.ac. Please patch either the generated files or the files they're generated from but not both, and arrange for the port to either regenerate the generated files (e.g. run autoreconf) or not accordingly.

Existing patchfile 01_patch-dyld-link.diff patches configure (and not configure.ac), therefore all other patchfiles must match this and also patch configure (not configure.ac), otherwise the effects of this patch will be lost when automatic regeneration occurs.

The 01_patch-dyld-link.diff file does patch the aclocal.m4 file, which is equally used to generate configure.

I just don't see the harm in patching both the source file(s) and the generated file. The builds are currently using the generated (and ready patched) configure, but–for whatever reason–it may be regenerated with autoreconf. I must add that I carefully considered the potential of failing patch (due to multiple passes), but in this case there is no such possibility. Besides, the new AGL patch is already applied upstream and will be removed by next update.