Andreas Schwab, le Tue 25 Aug 2015 09:23:40 +0200, a écrit :
> Why does install-headers depend on crt*.o?
Ah, sorry, I wasn't clear about it. It does not, it's the bootstrapping
process of debian which uses both install-headers and builds the crt*.o
files so that gcc can start linking basic stuff
Why does install-headers depend on crt*.o? That appears to be the
regression to fix.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Hello,
Andreas Schwab, le Sun 23 Aug 2015 08:54:31 +0200, a écrit :
> Samuel Thibault writes:
> > and this goes on at infinitum. Make -d shows that it is trying to build
> > /tmp/glibc-2.19/build-tree/hurd-i386-libc/mach/mach-shortcuts.h
> > and adding a $(warning) shows that the generated mach-s
Samuel Thibault writes:
> and this goes on at infinitum. Make -d shows that it is trying to build
> /tmp/glibc-2.19/build-tree/hurd-i386-libc/mach/mach-shortcuts.h
> and adding a $(warning) shows that the generated mach-shortcuts.h rule
> is for /tmp/glibc-2.19/build-tree/hurd-i386-libc/csu/mach-
Hello,
We are having trouble with bootstrapping glibc on Debian Hurd. To get
crt*.o, we run
/usr/bin/make cross-compiling=yes -C build-tree/hurd-i386-libc csu/subdir_lib
At some point it gets into
> /usr/bin/make -C ../mach mach-before-compile no_deps=t generating=t
then it builds a couple o
