Re: GCC and kernel.osversion
On Sat, Jul 18, 2015 at 8:53 PM, Brandon Allbery wrote: > To make "cc" refer to the MacPorts gcc: > port select --set gcc mp-gcc47 (or whatever version you installed; > try "port select --list gcc"). > hash -r(this tells the shell > to look for "cc" again instead of using a cached location) > Sigh, missed something sudo port select --set gcc mp-gcc47 hash -r -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: GCC and kernel.osversion
On Sat, Jul 18, 2015 at 8:47 PM, Dave Horsfall wrote: > > On 10.10? > > You have an ancient Xcode installed and you are lucky it only spit out a > > complaint about kern.osversion instead of crashing. > > Do not bet on it being usable or stable. Get rid of it. > > I updated Xcode to 6.4 a couple of weeks ago; I always stay current. > You have stuff under /Developer, though. Xcode hasn't used /Developer since 4.0.1 came out, and /Developer should be removed with the command I mentioned; otherwise you can run into odd problems as things find the old Xcode and use it. (You may have to reinstall the Command LIne Tools afterward, since it sounds like something has pointed cc at the ancient Xcode under /Developer.) To make "cc" refer to the MacPorts gcc: port select --set gcc mp-gcc47 (or whatever version you installed; try "port select --list gcc"). hash -r(this tells the shell to look for "cc" again instead of using a cached location) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: GCC and kernel.osversion
On Sat, 18 Jul 2015, Brandon Allbery wrote: > On 10.10? > You have an ancient Xcode installed and you are lucky it only spit out a > complaint about kern.osversion instead of crashing. > Do not bet on it being usable or stable. Get rid of it. I updated Xcode to 6.4 a couple of weeks ago; I always stay current. > sudo /Developer/Library/uninstall-devtools --mode=all > If you really insist on gcc, install one from MacPorts and use `port select` > to make it default. I did install it from MacPorts, and that's what got installed... Sorry I didn't make that clear. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer" "The complexity for minimum component costs has increased at a rate of roughly a factor of two per year." -- G.Moore, Electronics, Vol 38 No 8, 1965 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: GCC and kernel.osversion
On Sat, Jul 18, 2015 at 8:30 PM, Dave Horsfall wrote: > As an aside, I thought that Linux was bad enough in trying to distance > itself from Unix, but Apple really takes the Tim-Tam; who would've guessed > that GCC would be installed under /Developer? > On 10.10? You have an ancient Xcode installed and you are lucky it only spit out a complaint about kern.osversion instead of crashing. Do not bet on it being usable or stable. Get rid of it. sudo /Developer/Library/uninstall-devtools --mode=all If you really insist on gcc, install one from MacPorts and use `port select` to make it default. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
GCC and kernel.osversion
OS/X 10.10.4 Installed GCC 4.2.1 because I find CLANG is far too fussy and badly documented, and I get this: ozzie:ssem dave$ make cc -g ssem.c -o ssem couldn't understand kern.osversion `14.4.0' ssem.c: In function ‘main’: ssem.c:66: warning: return type of ‘main’ is not ‘int’ Ignore the warning, as I insist that main() calls exit() instead of merely returning; I'm old-school. ozzie:ssem dave$ sysctl kern.osversion kern.osversion: 14E46 I can sort of see a connection there, but what is the real problem? The program runs just fine, once I figured out: a) how to enable coredumps, and b) where it puts them... As an aside, I thought that Linux was bad enough in trying to distance itself from Unix, but Apple really takes the Tim-Tam; who would've guessed that GCC would be installed under /Developer? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer" "The complexity for minimum component costs has increased at a rate of roughly a factor of two per year." -- G.Moore, Electronics, Vol 38 No 8, 1965___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Odd activation failure
On Jul 18, 2015, at 10:29, Wahlstedt Jyrki wrote: > > activating wxPython-3.0 leads to this: > === > ---> Activating wxPython-3.0 @3.0.2_4 > Error: Failed to activate wxPython-3.0: Image error: Source file > /opt/local/var/macports/software/wxPython-3.0/mpextracthReS3feC/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/wxPython/._printfw.h > does not appear to exist (cannot lstat it). Unable to activate port > wxPython-3.0. > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_wxPython-3.0-3.0.2_4_a394d4d57ce632ad8bc69986734a877ab83d26d48f87d4fe885b727d3c10cc3c-8722/wxPython-3.0/main.log > for details. > Warning: Failed to execute portfile from registry for wxPython-3.0 @3.0.2_4 > ---> Activating wxPython-3.0 @3.0.2_4 > Error: port activate failed: Image error: Source file > /opt/local/var/macports/software/wxPython-3.0/mpextract6B2a0Dk4/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/wxPython/._printfw.h > does not appear to exist (cannot lstat it). Unable to activate port > wxPython-3.0. > === > Has anybody else seen anything like this? Build goes just fine, other ports > have activated fine, too (I’m on 10.11, hence had to build base from source, > so if someone says I’m on my own, I’ll accept that:) So it failed to activate the port because the file ._printfw.h didn't exist. Files whose names begin with "._" are created when OS X tries to add resource fork or other extended attribute information to a file on a file system that does not support those features, in other words a file system other than HFS+. Is your system using such a filesystem?___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Odd activation failure
Hi, activating wxPython-3.0 leads to this: === ---> Activating wxPython-3.0 @3.0.2_4 Error: Failed to activate wxPython-3.0: Image error: Source file /opt/local/var/macports/software/wxPython-3.0/mpextracthReS3feC/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/wxPython/._printfw.h does not appear to exist (cannot lstat it). Unable to activate port wxPython-3.0. Error: See /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_wxPython-3.0-3.0.2_4_a394d4d57ce632ad8bc69986734a877ab83d26d48f87d4fe885b727d3c10cc3c-8722/wxPython-3.0/main.log for details. Warning: Failed to execute portfile from registry for wxPython-3.0 @3.0.2_4 ---> Activating wxPython-3.0 @3.0.2_4 Error: port activate failed: Image error: Source file /opt/local/var/macports/software/wxPython-3.0/mpextract6B2a0Dk4/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/wxPython/._printfw.h does not appear to exist (cannot lstat it). Unable to activate port wxPython-3.0. === Has anybody else seen anything like this? Build goes just fine, other ports have activated fine, too (I’m on 10.11, hence had to build base from source, so if someone says I’m on my own, I’ll accept that:) ! ! Jyrki ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
