Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Original-Recipient:	<cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Building cross compiler Linux host -> Cygwin target
X-message-flag:	Infected by Norwegian Cheese
From:	Andrew Markebo <andrew DOT markebo AT telia DOT com>
In-Reply-To:	<87smt6tqgy.fsf@prism.localnet> (Massimiliano Mirra's message
	of "Sat, 29 Mar 2003 11:30:21 +0100")
References:	<87smt6tqgy DOT fsf AT prism DOT localnet>
User-Agent:	Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.2 (gnu/linux)
Date:	Sat, 29 Mar 2003 20:33:44 +0100
Message-ID:	<m3wuii2civ.fsf@telia.com>
MIME-Version:	1.0

/ Massimiliano Mirra <mmirra AT libero DOT it> wrote:
| I'm trying to build a cross compiler to i686-cygwin.  Host is a i686
| Debian 3.0 Linux with gcc 2.95.4 and glibc 2.2.5.

Saw recently (yesterday?) one person posting what he did.. you should
be able to find the article in the archive.. ahh subject "Please
help. gcc 3.2.2 configure problem or what?"

[...]

| make[2]: Entering directory
| `/home/bard/workspace/cygwin/src/gcc2-2.95.3-10/build/i686-pc-cygwin/libiberty'
| make[2]: *** No targets specified and no makefile found.  Stop.

And well.. he did a rm -rf if the libiberty subdir.. 

|     $ i686-pc-cygwin-gcc hello.c
|     /home/bard/workspace/cygwin//bin/../lib/gcc-lib/i686-pc-cygwin/
|     2.95.3-10/../../../../i686-pc-cygwin/bin/ld: cannot find -luser32
|     collect2: ld returned 1 exit status

Is the libuser32.lib library really in the gcc source? ahh nope it is
delivered in the package "w32api"! Maybe can grab that from a already
existing cygwin installation, or download the source and compile.

| So I guess that the remaining part of gcc's making would have taken
| care of the linker side of the story, right?

Nope, not all of it, not the system libraries of the cygwin part.

|| Does anybody have an idea about what is going wrong in building
| libiberty.a?  I found messages about libiberty.a in the

It seemed as it wasn't needed, if you do make -k it will hopefully
chew on.

     /Andy

-- 
 The eye of the compiler rests on the code!


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -