On Sat, Apr 03, 2004 at 09:02:32AM +0200, Matthias Klose wrote:
> Sven Luther writes:
> > That said, i have close to zero deep understanding on how glibc and gcc
> > interact on this issue, and what is going on about libgcc. I am told by
> > the #ppc64 folk that i should compile gcc with the ppc64 target, but
> > have it default to 32bit code by default. My early tries for this try to
> > generate a lib64gcc1, and fails, as you said. Do you have any wisdom to
> > share with me about why this is the case ?
>
> comment out the --disable-multilib in debian/rules2, add a patch not
> to build the -nof libraries and disable some biarch libraries (see the
> sparc-config-ml patch for an example).
dpkg-deb : construction du paquet « libgcc1 » dans «
../libgcc1_3.4-0pre2_powerpc.deb ».
trap '' 1 2 3 15; touch stamps/08-binary-stamp-libgcc; mv
stamps/07-install-stamp-tmp stamps/07-install-stamp
dh_testdir
dh_testroot
mv stamps/07-install-stamp stamps/07-install-stamp-tmp
rm -rf debian/lib64gcc1
dh_installdirs -plib64gcc1 \
usr/share/doc/lib64gcc1 \
lib64
install -d debian/tmp/lib64
mv debian/tmp/usr/lib64/libgcc_s.so.1 debian/tmp/lib64/.
mv: ne peut évaluer `debian/tmp/usr/lib64/libgcc_s.so.1': Aucun fichier ou
répertoire de ce type
make[1]: *** [stamps/08-binary-stamp-lib64gcc] Erreur 1
Didn't work out, apparently.
I would like to ask a question about this. lib64gcc1 should contain the
needed stuff for the ppc64 target and is thus needed in this case, or is
it that since we are building a biarch compiler, it is not needed since
the appropriate code is moved to the libgcc1 library ?
Friendly,
Sven Luther
