Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Tue, 1 Jun 2004 07:22:08 +0200
From: "Gerrit P. Haase" <gp@familiehaase.de>
Reply-To: "Gerrit @ cygwin" <cygwin@cygwin.com>
Organization: Esse keine toten Tiere
Message-ID: <1952081840.20040601072208@familiehaase.de>
To: cygwin@cygwin.com
CC: mingw-users@lists.sourceforge.net
Subject: Re: gcc-3.3.3 stage1 build error, undefined reference to `___do_sjlj_init'
In-Reply-To: <20040531212843.GA18899@coe.bosbc.com>
References: <4410562388.20040531210840@familiehaase.de> <1328366151.20040531231605@familiehaase.de> <20040531212843.GA18899@coe.bosbc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hallo Christopher,

Am Montag, 31. Mai 2004 um 23:28 schriebst du:

> On Mon, May 31, 2004 at 11:16:05PM +0200, Gerrit P. Haase wrote:
>>Hmmm, somehow, the rules from t-cygming were not included into the
>>Makefile, strange.  Do I need to sepcify --host && --target or s.th.
>>special to get it?

> Have you patched configure* to properly include the cygming stuff?
> IIRC, this wasn't part of the gcc 3.3.* branch.

I used the patch Danny provided at the MinGW site, but this is also
lacking some of the cygming branch unique files.  I think I'll need to
rework the build.

After patching the Makefile to include the defines from t-cygming, I
get still the same error (crtend.o: undefined ref...), it dissappears
when I include crtbegin.o manually.


Gerrit
-- 
=^..^=



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

