Re: problem compiling libzzip (PPC, Sorbet Leopard)
On 27/07/2022 8:52 pm, Hangglider wrote: MacOSX 10.5.9, http://macintoshgarden.org/forum/introducing-sorbet-leopard-105-reinvigorated http://macintoshgarden.org/apps/sorbet-leopard So an unofficial OS. We don't really support those... On 27.07.22 20:55, Chris Jones wrote: Btw. What the heck is ‘sorbet Leopard’ ?? On 27 Jul 2022, at 7:29 pm, Hangglider wrote: Hello, somewhere in the dependencies for some package I have to compile libzzip. That's less easy than it sounds: The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 and /opt/local/bin/ppc-apple-darwin9-gcc-7.5.0 == /opt/local/bin/gcc too) and tries to use it with -Warray-bounds. gcc-4.2 doesn't have that, but gcc7 does. Adding -DCMAKE_C_COMPILER=/opt/local/bin/gcc to the portfile didn't do the job. so some questions arise: Is there a well known way to enforce a given compiler? Would/should I have to replace or remove one of the system's (Xcode's) compiler(s) to clean things up a bit? Should I upgrade Xcode, and to which version (PPC32, Sorbet Leopard)? Thanks in advance for helpful responses. HG
Re: problem compiling libzzip (PPC, Sorbet Leopard)
As “Sorbet Leopard” is a non-standard release of MacOSX 10.5 Leopard for PowerPC with various modifications from the base system, MacPorts will not be able to support it. It is just too insane to try to keep these variant PPC systems sorted out, none of our common maintainers would use them, nobody would have ever thoroughly tested the tools out (gcc, cctools, ld64, etc) agains these systems, and so on. So use them if you want, but please be fair and only open tickets against the official released versions of MacOSX system software. If we sense there is a variant system in play, we won’t be able to help you. Ah, didn't see that facts, but it's well comprehensible and consequently makes me think about moving to an official version... thanks again. HG
Re: problem compiling libzzip (PPC, Sorbet Leopard)
> Hello, > > somewhere in the dependencies for some package I have to compile > libzzip. That's less easy than it sounds: > > The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 > and /opt/local/bin/ppc-apple-darwin9-gcc-7.5.0 == /opt/local/bin/gcc > too) and tries to use it with -Warray-bounds. gcc-4.2 doesn't have that, > but gcc7 does. Adding -DCMAKE_C_COMPILER=/opt/local/bin/gcc to the > portfile didn't do the job. so some questions arise: > > Is there a well known way to enforce a given compiler? MacPorts method of doing this is to first build a list of all known compilers that a system can support, and put them in preferred order. This is done through the interaction of several bits of tcl code that can be described later if you are interested. Then the Portfile will “blacklist” compilers or groups of compilers that are known not to work to build a given port. MacPorts base then chooses the first compiler on the list of possible system compilers that is not blacklisted. So — if libzzip will not build with gcc-4.2, then that compiler would be added to the port’s blacklisted compilers, with a statement like this in the Portfile: compiler.blacklist-append gcc-4.2 or if all the 4-series gcc’s won’t work, this: compiler.blacklist-append gcc-4.* etc. There are some other tricks that can be used, but for the purposes of how this is done, this is a reasonable way to start out. Chris mentioned a way to force a specific compiler, eg: sudo port -v install libzzip configure.compiler=macports-gcc-7 a list of all the known compiler names is here https://trac.macports.org/wiki/UsingTheRightCompiler although not all of those are available on 10.5.x PPC of course (eg none of the clang compilers is available there). > > Would/should I have to replace or remove one of the system's (Xcode's) > compiler(s) to clean things up a bit? > > Should I upgrade Xcode, and to which version (PPC32, Sorbet Leopard)? In general, to keep things sane, MacPorts assumes that you have installed the last possible version of Xcode that the system can support. There are a few exceptions to this rule just to keep you on your toes, of course, but none of the exceptions apply to Leopard. > > Thanks in advance for helpful responses. > > HG As “Sorbet Leopard” is a non-standard release of MacOSX 10.5 Leopard for PowerPC with various modifications from the base system, MacPorts will not be able to support it. It is just too insane to try to keep these variant PPC systems sorted out, none of our common maintainers would use them, nobody would have ever thoroughly tested the tools out (gcc, cctools, ld64, etc) agains these systems, and so on. So use them if you want, but please be fair and only open tickets against the official released versions of MacOSX system software. If we sense there is a variant system in play, we won’t be able to help you. Of course, you are free to fork MacPorts and/or use your own overlay of Portfile fixes that work on your variant OS version! It is a free country (still, more or less) and you can do anything you danged well want to do! Thx, K
Re: problem compiling libzzip (PPC, Sorbet Leopard)
MacOSX 10.5.9, http://macintoshgarden.org/forum/introducing-sorbet-leopard-105-reinvigorated http://macintoshgarden.org/apps/sorbet-leopard On 27.07.22 20:55, Chris Jones wrote: Btw. What the heck is ‘sorbet Leopard’ ?? On 27 Jul 2022, at 7:29 pm, Hangglider wrote: Hello, somewhere in the dependencies for some package I have to compile libzzip. That's less easy than it sounds: The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 and /opt/local/bin/ppc-apple-darwin9-gcc-7.5.0 == /opt/local/bin/gcc too) and tries to use it with -Warray-bounds. gcc-4.2 doesn't have that, but gcc7 does. Adding -DCMAKE_C_COMPILER=/opt/local/bin/gcc to the portfile didn't do the job. so some questions arise: Is there a well known way to enforce a given compiler? Would/should I have to replace or remove one of the system's (Xcode's) compiler(s) to clean things up a bit? Should I upgrade Xcode, and to which version (PPC32, Sorbet Leopard)? Thanks in advance for helpful responses. HG
Re: problem compiling libzzip (PPC, Sorbet Leopard)
> On 27 Jul 2022, at 7:54 pm, Chris Jones wrote: > > > >> On 27 Jul 2022, at 7:29 pm, Hangglider wrote: >> >> Hello, >> >> somewhere in the dependencies for some package I have to compile >> libzzip. That's less easy than it sounds: >> >> The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 >> and /opt/local/bin/ppc-apple-darwin9-gcc-7.5.0 == /opt/local/bin/gcc >> too) and tries to use it with -Warray-bounds. gcc-4.2 doesn't have that, >> but gcc7 does. Adding -DCMAKE_C_COMPILER=/opt/local/bin/gcc to the >> portfile didn't do the job. so some questions arise: >> >> Is there a well known way to enforce a given compiler? > > sudo port sync > sudo port upgrade outdated > sudo port clean libzzip > sudo port install libzzip configure.compiler=macports-clang-14 P.s. if v 14 is not available on your os, replace with whatever is.. > >> >> Would/should I have to replace or remove one of the system's (Xcode's) >> compiler(s) to clean things up a bit? >> >> Should I upgrade Xcode, and to which version (PPC32, Sorbet Leopard)? >> >> Thanks in advance for helpful responses. >> >> HG
Re: problem compiling libzzip (PPC, Sorbet Leopard)
Btw. What the heck is ‘sorbet Leopard’ ?? > On 27 Jul 2022, at 7:29 pm, Hangglider wrote: > > Hello, > > somewhere in the dependencies for some package I have to compile > libzzip. That's less easy than it sounds: > > The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 > and /opt/local/bin/ppc-apple-darwin9-gcc-7.5.0 == /opt/local/bin/gcc > too) and tries to use it with -Warray-bounds. gcc-4.2 doesn't have that, > but gcc7 does. Adding -DCMAKE_C_COMPILER=/opt/local/bin/gcc to the > portfile didn't do the job. so some questions arise: > > Is there a well known way to enforce a given compiler? > > Would/should I have to replace or remove one of the system's (Xcode's) > compiler(s) to clean things up a bit? > > Should I upgrade Xcode, and to which version (PPC32, Sorbet Leopard)? > > Thanks in advance for helpful responses. > > HG
Re: problem compiling libzzip (PPC, Sorbet Leopard)
> On 27 Jul 2022, at 7:29 pm, Hangglider wrote: > > Hello, > > somewhere in the dependencies for some package I have to compile > libzzip. That's less easy than it sounds: > > The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 > and /opt/local/bin/ppc-apple-darwin9-gcc-7.5.0 == /opt/local/bin/gcc > too) and tries to use it with -Warray-bounds. gcc-4.2 doesn't have that, > but gcc7 does. Adding -DCMAKE_C_COMPILER=/opt/local/bin/gcc to the > portfile didn't do the job. so some questions arise: > > Is there a well known way to enforce a given compiler? sudo port sync sudo port upgrade outdated sudo port clean libzzip sudo port install libzzip configure.compiler=macports-clang-14 > > Would/should I have to replace or remove one of the system's (Xcode's) > compiler(s) to clean things up a bit? > > Should I upgrade Xcode, and to which version (PPC32, Sorbet Leopard)? > > Thanks in advance for helpful responses. > > HG
