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
