Opened 19 months ago
Last modified 19 months ago
#67275 new defect
R-fs fails to build on Tiger (in libuv): error: void value not ignored as it ought to be if (unsetenv(name) != 0)
Reported by: | barracuda156 | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | tiger | Cc: | |
Port: | R-fs |
Description
CC src/unix/libuv_la-core.lo src/unix/core.c: In function 'uv_os_unsetenv': src/unix/core.c:1378:7: error: void value not ignored as it ought to be if (unsetenv(name) != 0) ^~~~~~~~~~~~~~ make[1]: *** [src/unix/libuv_la-core.lo] Error 1 make: *** [libuv-1.44.2/.libs/libuv.a] Error 2 ERROR: compilation failed for package ‘fs’
Change History (4)
comment:1 Changed 19 months ago by kencu (Ken)
comment:2 follow-up: 3 Changed 19 months ago by kencu (Ken)
Aside -- the SDK headers on Tiger are quite a bit different from Leopard+, and LOTS of things are headaches on Tiger that are not headaches on Leopard+, like @rpath handling, etc, etc, etc.
So Tiger is a mess/labour of love that you have be pretty invested in to bother fixing all the issues that come up.
comment:3 Changed 19 months ago by barracuda156
Replying to kencu:
Aside -- the SDK headers on Tiger are quite a bit different from Leopard+, and LOTS of things are headaches on Tiger that are not headaches on Leopard+, like @rpath handling, etc, etc, etc.
So Tiger is a mess/labour of love that you have be pretty invested in to bother fixing all the issues that come up.
Got it. I am not planning to spend much effort on Tiger, tbh: I rather do more for 10.5/10.6. I thought it would be nice to have a number of basic R
packages working, but it is not something that I gonna ever use personally.
- S. On a side note, why it enjoys that much of following, when nothing works?
comment:4 Changed 19 months ago by kencu (Ken)
TIger runs on all the really really old PowerPC systems (G3, etc) which gets some machines running that can't run Leopard -- and it runs MacOS9 in a very functional "Rosetta" emulator layer that works really quite well, so it opens the door to all the ancient stuff (and I have tons and tons and tons of ancient stuff from that era, for example). I have a couple of systems set up for Tiger.
to get the new unsetenv behaviour on Tiger, you need to have this defined:
by patch, flag, hack, compiler wrap, hook-or-by-crook, however you get it defined.
(The build seem to be hiding the build lines still, so you have no idea what is defined and what is not defined just now -- you have to disable silent rules, increase the verbosity, etc, etc ,etc to see what you are sending the compiler).