Re: improved Mac OS X support in bootstrap: please test
Am 07.06.2007 um 21:21 schrieb Ralf S. Engelschall: On Thu, Jun 07, 2007, Olivier Kaloudoff wrote: ... Yes, for fixing those problems I really need direct access to the platform as I have to poke around in system headers and try many things manually. Usually, it is fully sufficient if you just open port 22 on such a Mac OS X box so that I can login via SSH to an unprivileged account. More is usually not required for getting such software pieces running... Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com Hallo Ralf, do you need still access on an MacOSX Box? Please mail me. greetings Thomas -- Thomas Lenz [EMAIL PROTECTED] __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
Olivier Kaloudoff wrote: Porting GNU binutils over to Darwin sounds like a big enough task with eyes open, so probably not worth trying to do it blindly... ? Ok could not go to bed without trying.. - untarred binutils-2.17.tar.bz2 - did not apply the openpkg patch. - ./configure - make ... compilation went fine ... PATH used: PATH=/bin:/sbin:/usr/sbin:/usr/bin isn't this quite a good news ? Sure, but does binutils then work for e.g. bootstrapping GCC ? I got an error with ar, since it didn't recognize the objects. --anders __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
Ralf S. Engelschall wrote: The latest "binutils" package now builds without as(1), ld(1) and strip(1) now under Darwin / Mac OS X. In case those three tools are the major problem makers under Mac OS X this now could solve the issue. Just install "binutils" and "gcc" the regular way and see whether a package which requires "gcc" now really builds fine and also _WORKS_ under run-time. The GCC build is hanging now for me, on Mac OS X... This is because it's trying to use GNU long options: + ld --version + grep '^GNU ld ' + as --version + grep '^GNU assembler ' ^C Here's the output when you run the tools directly: $ ld --version ld: unknown flag: --version $ as --version /usr/libexec/gcc/darwin/i386/as: I don't understand '-' flag! Apple Computer, Inc. version cctools-622.5.obj~13, GNU assembler version 1.38 ^CInterrupted by signal 2 So the assembler is waiting for input, until terminated. as(1): "If no files are specified, as reads from stdin." The virtual package approach is probably the easiest... --anders PS. The option to display the version number is otherwise -v: (Mac OS X like other BSDs doesn't always do long options) ld -v as -v http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
Ralf S. Engelschall wrote: Yes, for fixing those problems I really need direct access to the platform as I have to poke around in system headers and try many things manually. Porting GNU binutils over to Darwin sounds like a big enough task with eyes open, so probably not worth trying to do it blindly... ? Ok could not go to bed without trying.. - untarred binutils-2.17.tar.bz2 - did not apply the openpkg patch. - ./configure - make ... compilation went fine ... PATH used: PATH=/bin:/sbin:/usr/sbin:/usr/bin isn't this quite a good news ? Kalou __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
Ralf S. Engelschall wrote: Yes, for fixing those problems I really need direct access to the platform as I have to poke around in system headers and try many things manually. Porting GNU binutils over to Darwin sounds like a big enough task with eyes open, so probably not worth trying to do it blindly... ? Q: Do you really need FSF binutils and FSF gcc built for OpenPKG, or will using Apple cctools and Apple gcc from the system suffice ? --anders __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
On Thu, Jun 07, 2007, Olivier Kaloudoff wrote: > >>> http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.txt > >> > >> Ah, ok. I see. Some incompatibilities with the system headers. This is > >> usually easy to workaround, but unfortunately not blindly without system > >> access. One has to find the defintions in /usr/include and then apply a > >> workaround. If I would have temporary access to a Mac OS X box I can try > >> to fix this. Without it would require many many turnarounds. > > > > Ok, tried to workaround the problem. Can you retry to build > > the latest GNU binutils package again? > > Workaround worked ! ... until next failure.. log here; > > http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.2.txt Ohh | .././libiberty/getpwd.c: In function 'getpwd': | .././libiberty/getpwd.c:75: error: storage size of 'dotstat' isn't known | .././libiberty/getpwd.c:75: error: storage size of 'pwdstat' isn't known | .././libiberty/getpwd.c:79: warning: implicit declaration of function 'getenv' | .././libiberty/getpwd.c:79: warning: assignment makes pointer from integer without a cast According to the sources this means we have a major problem as this part of the source usually should be never active on any POSIX-style OS. I cannot believe Mac OS X has no getcwd(3) or getwd(3). The real problem seems to be that during running "configure" those functions are not found and hence the above fallback implementation is tried (which fails for various reasons). And in your logfile we even have "checking for getcwd... yes", so there has to be some other Autoconf problems here. This is usually easy to fix when one has access to the system, but remotely it is more or less impossible. > I wish I'll be able to give an access to my box soon, unfortunatelly > my local network setup is not optimal and I did not manage yet to open > the right port to the right machine inside .. Yes, for fixing those problems I really need direct access to the platform as I have to poke around in system headers and try many things manually. Usually, it is fully sufficient if you just open port 22 on such a Mac OS X box so that I can login via SSH to an unprivileged account. More is usually not required for getting such software pieces running... Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.txt Ah, ok. I see. Some incompatibilities with the system headers. This is usually easy to workaround, but unfortunately not blindly without system access. One has to find the defintions in /usr/include and then apply a workaround. If I would have temporary access to a Mac OS X box I can try to fix this. Without it would require many many turnarounds. Ok, tried to workaround the problem. Can you retry to build the latest GNU binutils package again? Workaround worked ! ... until next failure.. log here; http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.2.txt I wish I'll be able to give an access to my box soon, unfortunatelly my local network setup is not optimal and I did not manage yet to open the right port to the right machine inside .. __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
On Wed, Jun 06, 2007, Ralf S. Engelschall wrote: > > http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.txt > > Ah, ok. I see. Some incompatibilities with the system headers. This is > usually easy to workaround, but unfortunately not blindly without system > access. One has to find the defintions in /usr/include and then apply a > workaround. If I would have temporary access to a Mac OS X box I can try > to fix this. Without it would require many many turnarounds. Ok, tried to workaround the problem. Can you retry to build the latest GNU binutils package again? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
On Tue, Jun 05, 2007, Olivier Kaloudoff wrote: > Virtual package gcc needed gcc g++ and i686-apple-darwin8-g++-4.0.1 > i686-apple-darwin8-gcc-4.0.1 linked to /openpkg/bin Are the i686-apple-darwin8-g??-4.0.1 symlinks really required? All OpenPKG packages AFAIK search just for "gcc" and "g++" but never for those other variants. > [...] > Tried to install binutils, fails with the following; > > http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.txt Ah, ok. I see. Some incompatibilities with the system headers. This is usually easy to workaround, but unfortunately not blindly without system access. One has to find the defintions in /usr/include and then apply a workaround. If I would have temporary access to a Mac OS X box I can try to fix this. Without it would require many many turnarounds. > > 2. The replacement method: > > > > In case approach (1) fails, you can try to replace the "binutils" > > and "gcc" packages with virtual packages containing symlinks to the > > system commands. For this install OpenPKG package "openpkg-import" > > with options "with_binutils=yes" and perhaps even "with_gcc=yes" set. > > Hmmm. Just installed openpkg-import > ( openpkg build openpkg-import -Dwith_gcc=yes -Dwith_binutils=yes | sh ) > tried with space between -D and with, same result. No, the syntax is: $ openpkg build -Dwith_gcc=yes -Dwith_binutils=yes openpkg-import | sh It is a standard Unix-style command where all(!) options have to be before non-option arguments. > but this package seems to have no file .. don't understand how it > should behave .. did I miss something ? when I retry build nagios | sh > after installing openpkg-import, it triggers the build of binutils > once more .. It contains the files once the options are correctly passed. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
On Tue, Jun 05, 2007, Ralf S. Engelschall wrote: [...] for the moment, on the i386, I have to create two virtual packages, as suggested by Bill (binutils and gcc). A "gcc" package should be enough as this is the only one requiring "binutils". OTOH, is GCC or Binutils the actual problem under Mac OS X? I guess it is Binutils and stock GCC works, right? Or in other words: would it work if we use the "gcc" package but without the "binutils" package (instead the system ld/as etc are used)? Virtual package binutils was only a way to tell rpm db that it's installed. Virtual package gcc needed gcc g++ and i686-apple-darwin8-g++-4.0.1 i686-apple-darwin8-gcc-4.0.1 linked to /openpkg/bin With these two hacks I had a working openpkg instance. Ok, I've hacked "binutils", "gcc" and "openpkg-import" a little bit and now you can try out the following two things to get your OpenPKG instance working: 1. The regular method: The latest "binutils" package now builds without as(1), ld(1) and strip(1) now under Darwin / Mac OS X. In case those three tools are the major problem makers under Mac OS X this now could solve the issue. Just install "binutils" and "gcc" the regular way and see whether a package which requires "gcc" now really builds fine and also _WORKS_ under run-time. Tried to install binutils, fails with the following; http://www.kalou.net/openpkg/openpkg-build-binutils-failed.20070604.txt 2. The replacement method: In case approach (1) fails, you can try to replace the "binutils" and "gcc" packages with virtual packages containing symlinks to the system commands. For this install OpenPKG package "openpkg-import" with options "with_binutils=yes" and perhaps even "with_gcc=yes" set. Hmmm. Just installed openpkg-import ( openpkg build openpkg-import -Dwith_gcc=yes -Dwith_binutils=yes | sh ) tried with space between -D and with, same result. but this package seems to have no file .. don't understand how it should behave .. did I miss something ? when I retry build nagios | sh after installing openpkg-import, it triggers the build of binutils once more .. Olivier __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
On Tue, Jun 05, 2007, Ralf S. Engelschall wrote: > [...] > > for the moment, on the i386, I have to create two virtual packages, > > as suggested by Bill (binutils and gcc). > > A "gcc" package should be enough as this is the only one requiring > "binutils". OTOH, is GCC or Binutils the actual problem under Mac OS X? > I guess it is Binutils and stock GCC works, right? Or in other words: > would it work if we use the "gcc" package but without the "binutils" > package (instead the system ld/as etc are used)? Ok, I've hacked "binutils", "gcc" and "openpkg-import" a little bit and now you can try out the following two things to get your OpenPKG instance working: 1. The regular method: The latest "binutils" package now builds without as(1), ld(1) and strip(1) now under Darwin / Mac OS X. In case those three tools are the major problem makers under Mac OS X this now could solve the issue. Just install "binutils" and "gcc" the regular way and see whether a package which requires "gcc" now really builds fine and also _WORKS_ under run-time. 2. The replacement method: In case approach (1) fails, you can try to replace the "binutils" and "gcc" packages with virtual packages containing symlinks to the system commands. For this install OpenPKG package "openpkg-import" with options "with_binutils=yes" and perhaps even "with_gcc=yes" set. Please give feedback whether one of the above approach solves the Binutils/GCC problems under Mac OS X. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
On Tue, Jun 05, 2007, Olivier Kaloudoff wrote: > > So, please bootstrap a fresh instance again under Mac OS X and try to > > build up to Apache with SSL support or whatever else and give feedback. > > At least the problems under Mac OS X now should be a lot less than > > before... > > openpkg-20070604 bootstrap compiled without a single glitch on i386 and ppc > (g4) .. great work :-) > > openpkg-20070604-20070604.i386-macosx10.4-ope.sh > openpkg-20070604-20070604.ppc-macosx10.4-ope.sh Ah, good. OTOH, the i386 "architecture product" actually should be ix86 to be consistent with the other platform identifiers (who use i386 for the "architecture technology" but ix86 for the "architecture product"). Now fixed, too. > for the moment, on the i386, I have to create two virtual packages, > as suggested by Bill (binutils and gcc). A "gcc" package should be enough as this is the only one requiring "binutils". OTOH, is GCC or Binutils the actual problem under Mac OS X? I guess it is Binutils and stock GCC works, right? Or in other words: would it work if we use the "gcc" package but without the "binutils" package (instead the system ld/as etc are used)? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
Hi Ralf ! So, please bootstrap a fresh instance again under Mac OS X and try to build up to Apache with SSL support or whatever else and give feedback. At least the problems under Mac OS X now should be a lot less than before... openpkg-20070604 bootstrap compiled without a single glitch on i386 and ppc (g4) .. great work :-) openpkg-20070604-20070604.i386-macosx10.4-ope.sh openpkg-20070604-20070604.ppc-macosx10.4-ope.sh for the moment, on the i386, I have to create two virtual packages, as suggested by Bill (binutils and gcc). __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: improved Mac OS X support in bootstrap: please test
I ran tar on the .sh file and extracted the openpkg.tar.bz2 file to the correct location and I am able to use it, so it looks like everything is in order with the build. I have run build make binutils and gcc, so far so good. -thanks On 6/4/07, Doug Henry <[EMAIL PROTECTED]> wrote: bootstrap completes and the .sh file is built. Trying to run the bootstrap binary yields the following error: openpkg-20070604-20070604.i386-macosx 10.4.9-tools.sh: cannot execute binary file On 6/4/07, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote: > > Ok, the last days I've tried to (blindly) incorporate all your feedback > to improve the Mac OS X support in the bootstrap package. Today I've > finally enhanced the GNU shtool platform detection under Mac OS X and > also added some evil but necessary gcc/cc/ld command overrides which > pass option -search_paths_first to the system ld(1). Together with now > perhaps a dummy "gcc" package (as people tell me that the stock GNU gcc > has problems under Mac OS X while the system gcc works fine) one should > be able to build a rather complex OpenPKG instance under Mac OS X. > > But as I've no Mac OS X available myself, I cannot test it in any way. > So, please bootstrap a fresh instance again under Mac OS X and try to > build up to Apache with SSL support or whatever else and give feedback. > At least the problems under Mac OS X now should be a lot less than > before... > >Ralf S. Engelschall >[EMAIL PROTECTED] >www.engelschall.com > > __ > OpenPKG http://openpkg.org > User Communication List openpkg-users@openpkg.org >
Re: improved Mac OS X support in bootstrap: please test
bootstrap completes and the .sh file is built. Trying to run the bootstrap binary yields the following error: openpkg-20070604-20070604.i386-macosx 10.4.9-tools.sh: cannot execute binary file On 6/4/07, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote: Ok, the last days I've tried to (blindly) incorporate all your feedback to improve the Mac OS X support in the bootstrap package. Today I've finally enhanced the GNU shtool platform detection under Mac OS X and also added some evil but necessary gcc/cc/ld command overrides which pass option -search_paths_first to the system ld(1). Together with now perhaps a dummy "gcc" package (as people tell me that the stock GNU gcc has problems under Mac OS X while the system gcc works fine) one should be able to build a rather complex OpenPKG instance under Mac OS X. But as I've no Mac OS X available myself, I cannot test it in any way. So, please bootstrap a fresh instance again under Mac OS X and try to build up to Apache with SSL support or whatever else and give feedback. At least the problems under Mac OS X now should be a lot less than before... Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
