Opened 3 months ago
Last modified 3 months ago
#70501 new defect
windowmaker@0.95.9_1 Portfile on Tiger PPC doesn't compile as-is.
Reported by: | garoffoli (garoffoli) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.3 |
Keywords: | windowmaker tiger ppc | Cc: | |
Port: | windowmaker |
Description
Trying to compile windowmaker as-is doesn't work, because apple-gcc42 doesn't correctly support C99.
It needs
PortGroup legacysupport 1.1
and
configure.compiler macports-gcc-7
and now it compiles fine.
Change History (8)
comment:1 Changed 3 months ago by barracuda156
comment:2 follow-up: 3 Changed 3 months ago by barracuda156
Replying to garoffoli:
Could you say what does it need legacysupport
for? What error do you get otherwise?
On 10.6 I did not need it.
Also, no need to use a newer gcc, this works:
configure.cflags-append \ -std=c99
comment:3 follow-up: 4 Changed 3 months ago by garoffoli (garoffoli)
Replying to barracuda156:
Replying to garoffoli:
Could you say what does it need
legacysupport
for? What error do you get otherwise? On 10.6 I did not need it.Also, no need to use a newer gcc, this works:
configure.cflags-append \ -std=c99
Adding legacysupport on packages that don't build it's the first thing I try. It's a "hack" that doesn't really resolve the issue. But it works fine.
comment:4 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to garoffoli:
Adding legacysupport on packages that don't build it's the first thing I try. It's a "hack" that doesn't really resolve the issue. But it works fine.
legacysupport adds functions that are missing or different on old macOS. If you are experiencing an error that points to such a function, adding legacysupport is a reasonable thing to try. You did not show us what error you got so we cannot say whether it was reasonable in this case.
legacysupport has nothing to do with what C standard the code will use or what the compiler will support. Apple GCC 4.2 supports C99 just fine but it defaults to C89. If you want C99 you have to ask for it with a -std
flag.
comment:5 Changed 3 months ago by Sergey Fedorov <barracuda@…>
comment:6 follow-up: 7 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)
Does that take care of it? Does it now compile on Tiger PPC? If not, please attach the main.log.
comment:7 Changed 3 months ago by garoffoli (garoffoli)
Replying to ryandesign:
Does that take care of it? Does it now compile on Tiger PPC? If not, please attach the main.log.
I currently can't compile windowmaker due to the pango dependency failing to install. #70515
comment:8 Changed 3 months ago by garoffoli (garoffoli)
I currently tried to install windowmaker@0.96.0 removing the "pango" dependecy (It seems to not be used at all). Wmaker just now crashes on startup.
XFree86 Version 4.4.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) [DRI] screen 0 installation complete Screen 0 added: 1280x854 @ (0,0) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! dyld: lazy symbol binding failed: Symbol not found: _secure_getenv Referenced from: /opt/local/lib/libWUtil.5.dylib Expected in: dynamic lookup dyld: Symbol not found: _secure_getenv Referenced from: /opt/local/lib/libWUtil.5.dylib Expected in: dynamic lookup Aug 9 14:11:23 PowerBook-G4 crashdump[14445]: wmaker crashed Aug 9 14:11:23 PowerBook-G4 crashdump[14445]: crash report written to: /Users/garoffoli/Library/Logs/CrashReporter/wmaker.crash.log Quitting XDarwin... X connection to :0 broken (explicit kill or server shutdown). xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0" X connection to :0 broken (explicit kill or server shutdown).
Host Name: PowerBook-G4 Date/Time: 2024-08-09 14:11:23.187 +0200 OS Version: 10.4.11 (Build 8S165) Report Version: 4 Command: wmaker Path: /opt/local/bin/wmaker Parent: wmaker [14437] Version: ??? (???) PID: 14444 Thread: Unknown Link (dyld) error: Symbol not found: _secure_getenv Referenced from: /opt/local/lib/libWUtil.5.dylib Expected in: dynamic lookup
Replying to garoffoli:
Does it work with passing
-std=C99
? If not, then old Xcode gccs should be blacklisted, but we need not hardcode a specific compiler (I am pretty sure it will build with gcc14 or gcc6 just as well).