[openbeos] Re: gcc for BeOS


On Friday, May 16, 2003, at 13:50 America/Los_Angeles, François Revol wrote:

En réponse à Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>:

"Bruno van Dooren" <bruno_van_dooren@xxxxxxxxxxx> wrote: 
maybe this is a silly question, but i couldn't really find the
answer:
do i need to do anything special to install gcc 2.95.3 for BeOS, or
do i just install
it like i would on linux (./configure && make bootstrap && make
install) or do i
need to do something special?

AFAIK, the BeOS specific portion in the official sources has stopped to
be maintained long before 2.95.3. So simply building gcc won't result
in a valid tool (if it doesn't even fail to build).

BTW, there is a binary on BeBits, but it is known to be seriously
buggy.

"Buggy" in what way? AFAIK Takashi did a lot of science to insure that the 2.95.3 toolchain works as advertised. I've noticed that the 2.95.3 toolchain on BeBits doesn't properly compile template functions, but that's ok because templates are evil. ;-)

 gcc maintainters refused patches for BeOS, under the
pretext that it was dead or something...
makes me wonder if they really deserves the term of crossplatform :^)

Yeah, I went through the same song-and-dance when I tried to provide a couple of bug fixes to gcc 3.1 for an Atmel processor target (AVR); my e-mails fell on deaf ears so I gave up trying to contribute and switched back to gcc 2.95.2 to support my development efforts for said processor.

maybe it would be easy to make a gcc binary for BeOS installer and
put it up for
download in the developer section?

It would be very nice, if someone did.

I'd do that if I had time, but I have bad memory of building gcc anyway :D

Pardon my public display of stupidity here but is moving away from the Be-provided toolchain to 2.95.3 such a good idea for R1? (I vaguely remember a discussion we had about a year ago that this wasn't such a keen thing to do.)

In any case if this is a viable option I'll take on the work. I've done a lot of embedded stuff and know my way around the gcc 2.x toolchain reasonably well.

Cheers,
Scott

Other related posts: