Date: Tue, 13 Mar 2001 12:02:10 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
cc: djgpp-workers AT delorie DOT com
Subject: RE: stubify and Windows ME
In-Reply-To: <CAEGKOHJKAAFPKOCLHDIGEHLCBAA.tim.van.holder@pandora.be>
Message-ID: <Pine.SUN.3.91.1010313120147.10085E@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 12 Mar 2001, Tim Van Holder wrote:

> > > Oh, I noticed something annoying: running binaries (such as stubedit)
> > > built in the DJGPP CVS tree crashed my system in a BIG way.  Turns out
> > > this is because my gcc uses 'const' sections, and djgpp.djl doesn't put
> > > them anywhere.
> > 
> > What are these sections?  Is your GCC based on a snapshot which added
> > them?  If not, where did those sections come from?
> You should know by now I like to customize my tools - I added it of
> course

If these are your private sections, why should stock djgpp.djl know
about them?  What if some other user defines some private feature
which conflicts with yours?

Can't you simply hack your private linker script in the same way you
hacked GCC?