Re: PowerPC and General Build Questions...

"Axel Dörfler" <[email protected]>
Newsgroups gmane.os.openbeos.kernel.devel
Message-ID <3524334104-BeMail@zon>
Andrew McCall <[email protected]> wrote:
> I set up a build environment under Linux PowerPC last night to see
> what would build and what wouldn't.  I used gcc 3.4, but I am writing
> a document to make a self contained build environment using gcc 
> 2.95.3
> and binutils 2.15.  Other than Subversion, is there anything else 
> that
> is required to build Haiku?

Not that I know of, if you've taken the Jam in our repository into 
account.

> A few things did build, but most things didn't as I expected. Is 
> there
> a list or knowledge of what is currently buildable on PowerPC
> hardware?

Not really, I was only trying kernel stuff yet. I seem to remember that 
libroot.so worked at some point in the past (at least with GCC 2.95.4/
debian), but I think it doesn't do so anymore.

> I was also thinking about things like ADB.  ADB would never need to 
> be
> built for x86 hardware, like wise for PS/2 (Unless things like 
> Pegasos
> use it) on PPC hardware.  Is there a place in the tree where things
> like this are split into architectures like
> 
> If I put abd in trunk/src/add-ons/kernel/busses wouldn't it be build
> for both architectures?

A hacked mouse/keyboard driver combo à la ps2_hid driver would be good 
enough for me, but you can a) put it in an arch directory, or b) you 
can tell Jam not to include the target on x86 systems. But as long as 
the driver can be built on x86, I wouldn't mind if it happened.

Bye,
   Axel.



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.