Date: Tue, 7 Sep 1999 13:40:20 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Keith McCormick <kdm98 AT spiritone DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Need help building Allegro!?!
In-Reply-To: <936578909.807231@ridge.spiritone.com>
Message-ID: <Pine.SUN.3.91.990907133948.27853A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 6 Sep 1999, Keith McCormick wrote:

> Here are the various crash dumps that I have gotten.  The allegro build
> process does not even want to finish.  The library completes, but when it
> startes creating exe's those crash and the build won't continue.

These are very weird crashes.  They seem to imply that something is
seriously wrong with how binaries are generated in your environment.

The programs crash inside the function `__main' (not your `main').
That function is where the static constructors are run.  The crashes
show that the stack is all messed up, perhaps because of some
alignment problem.

Questions:

  1. What compilation switches does the Allegro build process use?
  2. Is dat2s.exe a C program or a C++ program?
  3. Does dat2s.exe define or use functions that are declared with
     __attribute__((constructor))?
  3. Did you edit your djgpp.djl linker script, or replace it with
     some script that is generated by Binutils when they are built?