From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<9606101328.AA12154@clio.rice.edu>
Subject:	Re: Allegro Compatibility
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Mon, 10 Jun 1996 08:28:42 -0600 (CDT)
Cc:	slh100 AT york DOT ac DOT uk, djgpp AT delorie DOT com
In-Reply-To:	<Pine.SUN.3.91.960610080222.2508B-100000@is> from "Eli Zaretskii" at Jun 10, 96 08:06:15 am

> > BTW. does anyone know how I could make my definition overridable from 
> > user programs? If I define _crt0_startup_flags in liballeg.a and in a 
> > program itself, I get a linker conflict: is there any way to prevent that?
> 
> You can change the setting of the bit that controls `sbrk' behavior at
> runtime.  I think Charles Sandmann once told me that you can safely switch
> from the unixy behavior to the default one any time, but you cannot go
> back (am I right, Charles?).  If this is true, then you could set it to 
> unixy by default and then change at runtime if needed.

While this is true for the change of sbrk() algorithm, it's not true for
many of the other flags.  The multiple definitions of the startup flags
is a problem I don't know a good fix for.

- Raw text -