Compiling, --target question...

Compiling, --target question...

[Andrew McCall]

Hi Folks,

I am currently trying to set up a build environment for Haiku (was
OpenBeOS) under Linux on PowerPC hardware so I can start porting to
some systems I have.  Someone has already written a howto on how to
compile Haiku on Linux which can be read here:

http://cvs.sourceforge.net/viewcvs.py/open-beos/buildtools/INSTALL-as-cross-compiler-on-LINUX?rev=1.1&view=markup

In here binutils is built using --target=i586-pc-beos, which builds
correctly for BeOS on Intel hardware.

There is a PowerPC version of BeOS, however this uses the PEF file
format.  If I was building a PowerPC version of Haiku I would want to
use ELF as backward compatibility isn't really an issue.

What do I need to do to be able to use a target command like
--target=ppc32-pc-beos, or --target=ppc32-pc-haiku so it will build
for PowerPC CPU's for BeOS using ELF?

-- 
Thanks,

Andrew McCall
andrew.mccall@gmail.com

Re: Compiling, --target question...

[Andrew McCall]

On 7/4/05, Andrew McCall <andrew.mccall@gmail.com> wrote:
> I am currently trying to set up a build environment for Haiku (was
> OpenBeOS) under Linux on PowerPC hardware so I can start porting to
> some systems I have.  Someone has already written a howto on how to
> compile Haiku on Linux which can be read here:
>
> There is a PowerPC version of BeOS, however this uses the PEF file
> format.  If I was building a PowerPC version of Haiku I would want to
> use ELF as backward compatibility isn't really an issue.
> 
> What do I need to do to be able to use a target command like
> --target=ppc32-pc-beos, or --target=ppc32-pc-haiku so it will build
> for PowerPC CPU's for BeOS using ELF?

Hi Again,

I think I have worked out my question, but before I go an do some work
can someone answer me:

As the target powerpc-*-beos already exists making coff's do I need to
create a new platform powerpc-*-haiku that will make elf's, or is
there anyway to specify that -powerpc-*-beos can produce elf's too?

-- 
Thanks,

Andrew McCall
andrew.mccall@gmail.com

Re: Compiling, --target question...

[Nick Clifton]

Hi Andrew,

> As the target powerpc-*-beos already exists making coff's do I need to
> create a new platform powerpc-*-haiku that will make elf's, or is
> there anyway to specify that -powerpc-*-beos can produce elf's too?

No sorry you need a new target.  powerpc-*-haiku is OK, but since there 
is already an i*86-*-beoself target supported you might prefer to use: 
powerpc-*-beoself.

Cheers
   Nick

Re: Compiling, --target question...

[Andrew McCall]

On 7/5/05, Nick Clifton <nickc@redhat.com> wrote:
> Hi Andrew,
> 
> > As the target powerpc-*-beos already exists making coff's do I need to
> > create a new platform powerpc-*-haiku that will make elf's, or is
> > there anyway to specify that -powerpc-*-beos can produce elf's too?
> 
> No sorry you need a new target.  powerpc-*-haiku is OK, but since there
> is already an i*86-*-beoself target supported you might prefer to use:
> powerpc-*-beoself.

I spoke to a few members of the Haiku project last night about this -
they are planning to use *-*-haiku and submit a patch to yourselves,
so its going to be best to use powerpc-pc-haiku, i586-pc-haiku or
sparc-pc-haiku (thinking a bit too far ahead here :) ).  All versions
are going to use elf.

I spent the night hacking around the build system, and I think I
managed to get it to target powerpc-pc-haiku using elf, but I don't
really know how to extract what I have done to make a patch.  If I
upload a tar.gz of what I have done, can someone take a look to see if
its right?

Thanks,

Andrew McCall

-- 
Thanks,

Andrew McCall
andrew.mccall@gmail.com

Re: Compiling, --target question...

[Nick Clifton]

Hi Andrew,

> I spent the night hacking around the build system, and I think I
> managed to get it to target powerpc-pc-haiku using elf, but I don't
> really know how to extract what I have done to make a patch.  If I
> upload a tar.gz of what I have done, can someone take a look to see if
> its right?

Well it really is a lot easier for us if you can provide a patch (or set 
of patches).

If you are using the binutils sources checked out of the CVS repository 
(which is what we would recommend for this kind of work) then all you 
need to do is run "cvs diff -cp" at the top level of the sources in 
order to generate a patch file.

If you only have a tarball then you can still create a patch by getting 
hold of another copy of the source tarball (from your backups, you do 
keep backups, right ? :-) and then running "diff -rcp <original> <new>" 
at the top level.

Cheers
   Nick