[parisc-linux] Cannot build 02/18/2001 glibc

[Rafael E. Herrera]

Matt Taggart wrote:
> 
> "Rafael E. Herrera" writes...
> 
> > Alan Modra wrote:
> > >
> > > On Mon, 19 Feb 2001, Rafael E. Herrera wrote:
> > >
> > > > checking for assembler line separator... *** You need a newer assembler
> > > > to compile glibc
> > > >[snip]
> > > >  /usr/i486-suse-linux/bin/as -V -Qy -v -o conftest.o conftest.s
> > >
> > > Oops, this is an x86 assembler.
> > >
> > > > The binaries called and the version numbers are shown. Do I need to
> > > > upgrade the assembler or is it a PATH misconfiguration? Thanks.
> > >
> > > You need the hppa-linux assembler installed and available on your PATH.
> >
> > The PATH needs to include both of these entries:
> >
> > PATH=~/palinux/bin:~/palinux/hppa-linux/bin:$PATH
> >
> > I had just first one before.
> 
> No, you don't want hppa-linux/bin in there because then the build will only
> use the cross-compiler and will fail if it needs to build any i386
> binaries(like intermediate build tools etc.). As long as you have --host and
> --build set right then the build will do the right thing.

If I use these to build glibc library:

export MACH=i386-linux
export DEST=~/parisk/palinux
export ROOT=~/parisk
PATH=~/parisk/palinux/bin:$PATH

$ROOT/source/glibc/configure --prefix=$DEST/hppa-linux --build=$MACH \
--host=hppa-linux --target=hppa-linux \
--with-headers=$ROOT/source/linux/include --disable-profile \
--without-cvs --enable-add-ons

I get the same error reported initially. 'configure' does not use/find
the cross compiler. From a previous post, If I use this instead:

HOSTCC=gcc CC=hppa-linux-gcc $ROOT/source/glibc/configure
--prefix=$DEST/hppa-linux --build=$MACH \
--host=hppa-linux --target=hppa-linux \
--with-headers=$ROOT/source/linux/include --disable-profile \
--without-cvs --enable-add-ons

Configure doesn't fail and one can start building. I did not have this
problem a couple of weeks ago when I first tried this, I used snapshots
(from early february, before the newest were available -- they were zero
length) that allowed me to build a kernel image  and boot my machine. I
run into other problems, but I'll post questions about them later if I
still have them with these updated sources.

I've looked briefly at the main configure script and compared it to the
last revision, but cannot figure out why it uses the x86 assembler.
Perhaps the mantainer can resolve this.

Thanks
-- 
     Rafael