On 10/20/05, DJ Delorie <[EMAIL PROTECTED]> wrote:
>
> > Maybe a good place to get clues is to look at how GCC and binutils are
> > built for DOS, e.g. DJGPP. (I've asked DJ for some help).
>
> Except that DJGPP uses COFF, not a.out. DJGPP v1 used a.out, but most
> of that support has been remove
> Maybe a good place to get clues is to look at how GCC and binutils are
> built for DOS, e.g. DJGPP. (I've asked DJ for some help).
Except that DJGPP uses COFF, not a.out. DJGPP v1 used a.out, but most
of that support has been removed by now.
> Well, as far as I have seen, most of the internals are documented in the
> code itself. The best way to learn how it works, in my opinion, is to get
> a good code cross-reference tool. The files you mostly want to look at are
> in gcc/config in a build tree.
>
> Good luck and have fun,
> Jonathan
[EMAIL PROTECTED] said:
> Hi,
>
> I know that some people are working on a GCC port for Minix v3, but
> I'd like to work on a cross-compiler for my own purposes. I'd like
> the host and build to be i686-pc-linux-gnu, and the target to be
> i[3456]86-pc-minix3.
>
> Can anyone give me some advice on
Hi,
I know that some people are working on a GCC port for Minix v3, but
I'd like to work on a cross-compiler for my own purposes. I'd like
the host and build to be i686-pc-linux-gnu, and the target to be
i[3456]86-pc-minix3.
Can anyone give me some advice on where to begin and what info I need?
