This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: WinNT => FreeBSD cross compiler (CygWin compiled): is that possible?


Kai Ruottu wrote:

> > Thanks, now I think I understand what the problem was.
> > I didn't make a bootstrap gcc first, but tried to compile it full.
>
>  You doesn't need any 'bootstrap' GCC, but the 'full' one from the
beginning...

The reason of that I wanted to cross-compile the C-library is that I needed
to
produce two cross-compilers: one for FreeBSD and the other for Linux,
so I didn't need to take libs from those two.  I thought glibc would be
suitable
for both target systems.

> > And I also suppose I must compile newlib instead of glibc since the
latter is
> > only applicable for linux, right?
>
>  Wrong, and right, FreeBSD has its own 'BSD-like' headers and libraries,
which
> one receives as prebuilt with a FreeBSD-distribution. Of course the
FreeBSD C-
> library sources are also available, but there should be some sane reason
for the
> recompile, like after fixing many bugs in the C-library. Of course the
rebuild
> of the C-library can be a good test for the cross-compiler, but testing
the C-
> library after the rebuild may be quite time-consuming. So taking the
prebuilt
> libs from a suitable FreeBSD-distribution of from the target
FreeBSD-machine is
> much easier. The FreeBSD-distribution may not be newer than the one used
in the
> target system... Them being just the same is the ideal case, but backward-
> compatability should work and using '4.[1-3]' stuff in the toolchain
should say
> that the produced binaries will run on the current 'FreeBSD 4.4' or
something...
>

So if I need to make a FreeBSD-target cross-compiler, I need the FreeBSD
C-library,
since if even I compiled newlib the compiler would produce executables that
wouldn't run
on an arbitrary FreeBSD system, right?

>  You haven't mentioned the target FreeBSD-version... Some years ago also
FreeBSD
> started to use ELF and the target name is now 'i586-freebsdelf' or
something, not
> 'i586-freebsd', which means the older 'aout'-based FreeBSD before the
version 3.0
> which was ELF-based...

Thanks for this notice, I didn't know that.



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]