[haiku-development] Re: BeOS Apps Crashing on Haiku (Bug #889)
- From: "François Revol" <revol@xxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 01 Jun 2007 11:21:47 +0200 CEST
>
> On 2007-06-01 at 00:09:18 [+0200], François Revol <revol@xxxxxxx>
> wrote:
> > > > Nice problem we ran into there :-)
> > > > I would actually think it would be best to implement both
> > > > options;
> > > > 1)
> > > > because it'll definitely solve the problem and makes us
> > > > compatible
> > > > with
> > > > BeOS - we could make the change a compiler option
> > >
> > > Come to think of it, if the loader was able to find out what
> > > compiler
> > > has
> > > generated the shared objects involved, it could even decide live
> > > what
> > > strategy to use.
> >
> > We could make use of ELF flags for this...
> > or better, really allocate an OS ID, as currently BeOS identifies
> > itself as SysV ABI, which is quite absurd.
>
> BeOS actually uses the System V ABI -- pretty much everyone does, I
> suppose. Or do I miss something?
AFAIR it was meant to actually be an OS identification field:
http://cygwin.com/ml/binutils/2000-04/msg00346.html
http://www.cygwin.com/ml/binutils/2000-11/msg00367.html
cf. the quite big list from FreeBSD:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/elf_common.h?rev=1.22
But it seems it's not so much used for this purpose and lazy ppl just
went for SysV by default because they didn't feel like registering an
ID at SCO.
http://gcc.gnu.org/ml/gcc/2000-12/msg00307.html
François.
Other related posts:
