Brian Dessent wrote:
>
> "michael.a" wrote:
>
>> gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
>
> This belongs on gcc-help not here.
>
> Debian-based distros use a 32/64 bit /usr/lib configuration that is
> backwards from what the rest of the world uses and requires a patched
> gcc to multilib correctly. You'll probably need to --disable-multilib
> if you're building FSF gcc.
>
> Brian
>
>
Yeah, I know (mailing lists are so particular -- I guess I fail to see the
value beyond a noncentralized discussion)
In any case, without multilib it makes it to here:
make[2]: Leaving directory `/home/users/michael/gcc.obj/gcc'
echo timestamp > stmp-multilib
cp doc/gcc.1 doc/g++.1
cp: cannot stat `doc/gcc.1': No such file or directory
make[1]: *** [doc/g++.1] Error 1
make[1]: Leaving directory `/home/users/michael/gcc.obj/gcc'
make: *** [all-gcc] Error 2
Not sure exactly what is going on here. The gcc/doc directory is empty. I'm
assuming everything made it through. There are about a billion targets in
the Makefile and no explanatory header. Any suggestions for just building
the essentials?
I've only really recently taken on serious linux development and haven't
much actual build experience outside the usual routine. I have autotools
under my belt, but I glossed over most of the auxiliary stuff.
--
View this message in context:
http://www.nabble.com/I%27m-sorry%2C-but-this-is-unacceptable-%28union-members-and-ctors%29-tf3930964.html#a11186332
Sent from the gcc - Dev mailing list archive at Nabble.com.
