Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Link problem when building cygwin1.dll (parsing cygwin.def)
Date: Tue, 26 Jul 2005 18:07:13 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <BAY106-F58FF850BF2A4ECBA799F1FBCD0@phx.gbl>
Message-ID: <SERRANO7sHGS7jIgGIh00000749@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Eitan Eliahu
>Sent: 26 July 2005 17:52

[  Hi Eitan; you only sent this reply to me personally, and I'm guessing
that's just a mistake from hitting the wrong reply button, so I've Cc'd the
list back in.  (If you did do it just to take the conversation private,
please see http://cygwin.com/acronyms/#PPIOSPE for why it's always better to
keep these discussions on the list.  Cheers!  ]

> Dave, I'm trying to build a fresh source code I cehcked out from the CVS.
> 
> I followed the indtsruction listed in the FAQ page:
> mkdir build
> mkdir /install
> cd build
> (../configure --prefix=/install -v; make) >& make.out
> make install > install.log 2>&1

  Hmm.  I was starting to wonder if you had some kind of autotools problem.
I notice that you don't have any of the following packages installed:

autoconf                2.59-2
autoconf-devel          2.59-2
autoconf-stable         2.13-6
autoconf2.1             2.13-1
autoconf2.5             2.59-1
automake                1.7.9-2
automake-devel          1.9.2-2
automake-stable         1.4p6-3
automake1.4             1.4p6-1
automake1.9             1.9.5-1

which would certainly prevent the build process from regenerating any
configure scripts it might need to.  (You really *need* to install the
autotools if you're planning on building code from CVS, anyway.)

 .... But then I noticed this line from your cygcheck output:

> .                  /cygdrive  system  textmode,cygdrive


  BINGO!  Come in Houston, we have a problem:

> collect2: ld terminated with signal 11 [Segmentation fault], core dumped
>/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld:
> cygwin.def:4: parse error
>make[2]: *** [cygwin0.dll] Error 1
>make[2]: Leaving directory
`/cygdrive/c/Cyg/obj/i686-pc-cygwin/winsup/cygwin'

  You can't build in a textmode directory.  ld doesn't handle DOS-style
CR/LF line ends in a .def file.  Personally I'd remount your entire system
(_particularly_ the cygdrive mount) in binary mode if it was me, but you
should just be able to create a binmode mountpoint subdirectory and download
the sourced and compile under there.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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