Opened 5 years ago
Last modified 4 weeks ago
#58425 new defect
QGLE @4.2.5_12: fatal error: 'glu.h' file not found
Reported by: | majoc-at-astro (majoc-at-astro) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.5.4 |
Keywords: | mojave catalina | Cc: | |
Port: | QGLE |
Description
Please see enclosed build log, produced by port -v install qgle
on an otherwise-empty MacPorts installation, in which the punchline is:
3dviewer.cpp:30:10: fatal error: 'glu.h' file not found
The same port builds fine on our 10.12 and 10.13 builders. Trivial tests suggest this is because the headers have been moved from /System/Libraries
into /Applications/Xcode.app/Contents/Developer
(apologies: the correct terminology escapes me).
I have a truly horrible patch which uses <GL/glu.h>
and port:libGLU
, but this has the fails-to-fail nature. I'll sketch out a possible plan of attack in a followup submission.
Xcode 10.2.1
- Xcode: Build version 10E1001
- clang: Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Attachments (1)
Change History (6)
Changed 5 years ago by majoc-at-astro (majoc-at-astro)
Attachment: | qgle.log.2019-04-25_03.55.40.bz2 added |
---|
comment:1 Changed 5 years ago by mf2k (Frank Schima)
Keywords: | sysroot removed |
---|
comment:2 Changed 5 years ago by majoc-at-astro (majoc-at-astro)
Keywords: | sysroot added |
---|
comment:3 Changed 5 years ago by mf2k (Frank Schima)
Keywords: | sysroot removed |
---|
comment:4 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | mojave catalina added |
---|---|
Port: | QGLE added; qgle removed |
Summary: | QGLE @4.2.5_12: fails to find glu.h on 14.04 - build failure → QGLE @4.2.5_12: fatal error: 'glu.h' file not found |
Has duplicate #60789.
comment:5 Changed 4 weeks ago by ryandesign (Ryan Carsten Schmidt)
This will be fixed once QGLE is updated to 4.3.x. I'm working with upstream to resolve a variety of problems before we can update to that series.
Further experimentation with trivial CPP files at the command line suggests that the true fix would be to replace:
.... with:
.... which makes use of the
-isysroot/
phrase. (TheAGL.framework
header-inclusion phrase may need similar treatment, though I haven't tested that.)Methinks this headers-in-Xcode (headers-under-sysroot?) problem will turn up in other places (eg ticket:58378). I leave it to those who understand these things better to ascertain whether this needs to go in individual ports, into a portgroup, or both. Apologies for not being able to submit a known-working patchset for myself: it's taken me a week to get this far, and I'm out of oomph. Hope this helps.