[NTLUG:Discuss] Crosscompiling...

Opinionated opinionated at whoever.com
Mon Nov 22 20:23:04 CST 1999


I keep forgetting that there is quite a bit of talent here, so I think I
will ask my original question that I asked on gnu.gcc.help.

=================
Hello All,

I was having one specific problem compiling a cross-compiler for gcc.  I

finally got a cross-compiler on gcc-2.8.1 after I finally found the
patch which clears up a 'can't find stdio.h' error.  I have noticed that

gcc-2.95.2 has the exact same problem.  Is there a patch for the
configure.in file on 2.95.2 as well, or can someone give me a pointer as

to how to disable the building of the objc3 runtime module?

I appreciate any help.

Thanks in advance.
=====================

Unfortunately what I got is a bunch of people telling me that I should
learn how paths work....which really steams me, until I realized that
the majority of people posting on that newsgroup are people who are
making a crosscompiler for usually a Motorola 68K machine using a
Windows Host.....Anyhow, I'm still peeved since, yes, I do know what
paths are and after a lot of studying (which I don't really feel
shouldn't have been necessary since I would have expected GNU to have
their sources bundled better than this) I know where to put the
libraries....Anyhow....

Has anyone gotten been able to make a gcc v2.95.2 crosscompiler on a
RedHat 6.1 Laptop host for a Powerpc-elf target system?

Please don't refer me to the GNU cross-compiler FAQ/HOWTO as it is 1.
For gcc-2.8.1 (which I don't want to use), and 2.  It is Wrong for
gcc-2.95.2.  Funny that the gcc-2.95.2 Readme file refers to this Howto,
and then proceeds to tell you to make the crosscompiling different from
the FAQ.

======================
I am finally down to a multiplicy declared defined in the used Header
Files.  Before I proceed along, Does anybody have any other suggestions
just in case I can't see the forest for the trees?

Here's what I am doing:

<Note:  I have already made a cross-platform binutils tools for the
powerpc-elf....this worked with no problems>

<src-directory> = /usr/src/gcc-2.95.2
<build-directory> = /usr/src/build-gcc-cross
<target-directory> = /usr/local/powerpc-elf
<host> = i686-linux

I do all the builds in the build directory (as specified in the 2.95.2
readme).

The steps are:
1.   cd <build-directory>
2.   <src-directory/configure --target=powerpc-elf
--with-headers=/usr/linuxppc/include -v
(Note /usr/linuxppc/include is for me, a linux-2.2.12 kernel with the
links pointer to includes to the powerpc includes)
3.  make cross

I finally get to a message stating "conflicting types for 'sys_errlist'"
before termination...so yes I have to locate all the definitions and
figure out which header isn't supposed to be used.

I can write a whole dissertation as to what headers have to be used, and
I will if asked.  Suffice to say, I had to load down both sources for
kernel-2.2.12 and glibc-2.1.  (Why?  Big surprise, but the RedHat
included sources DO NOT have any other defines except for an Intel 386).

Anyhow, suggestions and help appreciated.








More information about the Discuss mailing list