Date: Mon, 10 Jun 1996 15:03:22 +0100 (BST)
From: Shawn Hargreaves <slh100 AT unix DOT york DOT ac DOT uk>
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
Subject: Re: Allegro Compatibility
In-Reply-To: <9606101328.AA12154@clio.rice.edu>
Message-ID: <Pine.SGI.3.91.960610145105.26527A-100000@tower.york.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 10 Jun 1996, Charles Sandmann wrote:

> > > 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
> 
> 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.

How does libc handle it? It must define it somewhere (at least I assume 
so, because there is no linker error if a program doesn't provide it) but 
it can be overridden at will. I have a feeling that might be because libc 
defines it to be zero, but in that case my definition in Allegro ought to 
work the same because I'm currently just zeroing it to force the non-move 
sbrk() algorithm...


/*
 *	Shawn Hargreaves.        Why is 'phonetic' spelt with a ph?
 *	Check out Allegro and FED on http://www.york.ac.uk/~slh100/
 */