Bhaskar Reddy kirjoitti:
Bhaskar Reddy wrote:
I'm trying to build a cross compiler on i686 for i386.
Configure Line: configure --target=i386-linux-gnu
Here it is totally unclear what on earth is your $target !
I named it so, by looking at the following documentation.
http://gcc.gnu.org/install/old.html
Then you are also aware about the fact that you should have the target
C library available and
being prebuilt, not only the target binutils, BEFORE starting to build
GCC. In a target case like
Debian 3.0 "Woody" with its glibc-2.2.5, of course the "target C
library" means "target C library
for Debian 3.0", not for instance "target C library for Red Hat 7.3"
although also this uses the
same 'glibc-2.2.5'. Of course there surely is quite a lot binary
compatability between these two,
but if one can choose, one chooses to not experiment the compatability.
In the same way one
doesn't choose to replace the Debian's glibc-2.2.5 with a self-built
glibc-2.2.5...
there were options like i386bsd, or "i386 can be cpu type and system type
can be linux-gnu", then is it like that i should not use target system
name as "i386-linux-gnu"
It really doesn't make any difference whether one uses a
'i386-debian-linux', a 'i386-redhat-linux',
a 'i386-suse-linux' or the generic 'i386-linux-gnu' as long as one knows
that these aren't totally
identical Linuces from the same company. The GCC builder only must know
what the '$target'
is and one can just as well keep it being secret from others... The
point is that the builder knows
what to use as the "target components", nothing more. This was what I
tried to get being clear,
one cannot just start to build a crosstoolchain for 'i386-linux-gnu'
without knowing somehow
what the target is... Maybe "just for a fun"...
Sorry for this... here are the details.
Version of GCC: GCC-4.1.1,
Version of Binutils: binutils-2.13.1
Version of Build/Host compiler : GCC 4.1.1
and i'm trying to build a cross compiler.
Producing binutils-2.13.1 with gcc-4.1.1 may crash, the GCC is too new
for sources this old...
Yeah, actually before that, i'm trying to build binutils which would
produce suitable "as" required for i386 .
The native 'as' should work in your case... But producing the target
binutils as if they were for some
'alien' CPU, really is quite sane, if not for any other purpose, at
least for practicing these things.
