This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: problems compiling current cygwin cvs release
- To: cygwin-apps at cygwin dot com
- Subject: Re: problems compiling current cygwin cvs release
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Sat, 13 Oct 2001 13:08:56 -0400
- References: <005a01c153be$743de6b0$fd1c440a@BRAMSCHE>
- Reply-To: cygwin-apps at cygwin dot com
On Sat, Oct 13, 2001 at 10:10:00AM +0200, Ralf Habacker wrote:
>Hi,
>
>I have problem compiling the current cygwin cvs release
>
>
>1.
>habacker@BRAMSCHE ~/src/cvs.cygwin.com/build/winsup/cygwin
>$ make
>gcc -c -gstabs+ -O2 -MD -fbuiltin ... glob.c
>../../../src/winsup/cygwin/glob.c:156: parse error before `*'
>../../../src/winsup/cygwin/glob.c:156: warning: type defaults to `int' in
>declaration of `g_opendir'
>../../../src/winsup/cygwin/glob.c:156: warning: data definition has no type or
>storage class
>../../../src/winsup/cygwin/glob.c: In function `glob3':
>../../../src/winsup/cygwin/glob.c:590: `DIR' undeclared (first use in this
>function)
>../../../src/winsup/cygwin/glob.c:590: (Each undeclared identifier is reported
>only once
>../../../src/winsup/cygwin/glob.c:590: for each function it appears in.)
>../../../src/winsup/cygwin/glob.c:590: `dirp' undeclared (first use in this
>function)
>../../../src/winsup/cygwin/glob.c:590: warning: statement with no effect
>../../../src/winsup/cygwin/glob.c:591: parse error before `int'
>
>A workaround is to add the following to glob.c:
>
>#include <cygwin/sys/dirent.h>
I'm not seeing this. It sounds like you are missing a '-I' on the command line
for some reason.
>BTW: This problem occurs with dir.cc too before I updated newlib today morning.
>
>2. On linking the cygwin dll the following file is used from the libiberty:
> /home/habacker/src/cvs.cygwin.com/build/libiberty/strsignal.o
>
>If one configure libiberty for using with ld the function strsignal() isn't
>defined,
>because configure finds a defined strsignal.
>If libiberty is shared between cygwin an ld/binutils, than there is a problem.
>???
Your build area is screwed up. cygwin is not supposed to share a libiberty with
'ld'. If you have cygwin in the same build area as 'ld' then the layout should
look something like this:
build/
bfd/
binutils/
ld/
i686-pc-cygwin/
libiberty/
newlib/
winsup/
cgf