This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Problem compiling cygwin1.dll from CVS


Even though your /cygdrive mount is binary, I'm a bit wary of building
outside of the cygwin root.  Try building in some directory under "/" (not
"/cygdrive/c"), and see if you still get this problem.  I remember seeing
something about files accessed through /cygdrive always being in textmode,
but I'm not too sure about that.  If anyone can confirm or deny this,
please do so.
	Igor

On Tue, 13 Jan 2004, Gabriel SOUBIES wrote:

> Hi!
> You are right, the problem I am referring to is the parse error in line 4 of
> cygwin.def.
> In fact, I even think that this very parse error is nothing but a side
> effect of the previous step failing (the generation of Cygwin0.dll, as you
> will see in the attached log).
>
> Here's what I did to re-build Cygwin:
> Download the sources via CVS and place them in /Cygwin/src
> Create a dir /Cygwin/obj where to build Cygwin, and a dir /Cygwin/install
> where to install it.
> I then moved into /Cygwin/obj and launched to following command lines:
> ../src/configure --prefix=/Cygwin/install -v > configure.log 2>&1
> make > make.log 2>&1
> And this is where is fails...
>
> The log files are attached to this mail, along with the result of
> cygcheck -svr.
>
> The last line of my make.log are the following:
> Making version.o and winver.o
> Version 1.5.6
> c++ -L/cygdrive/c/Cyg/obj/i686-pc-cygwin/winsup -L/cygdrive/c/Cyg/obj/i686-pc-cygwin/winsup/cygwin -L/cygdrive/c/Cyg/obj/i686-pc-cygwin/winsup/w32api/lib -isystem /cygdrive/c/Cyg/src/winsup/include -isystem /cygdrive/c/Cyg/src/winsup/cygwin/include -isystem /cygdrive/c/Cyg/src/winsup/w32api/include -B/cygdrive/c/Cyg/obj/i686-pc-cygwin/newlib/ -isystem /cygdrive/c/Cyg/obj/i686-pc-cygwin/newlib/targ-include -isystem /cygdrive/c/Cyg/src/newlib/libc/include -g -O2 -nostdlib -Wl,-T../../../../src/winsup/cygwin/cygwin.sc -Wl,--out-implib,cygdll.a -shared -o cygwin0.dll \
> -e _dll_entry@12 cygwin.def assert.o autoload.o bsdlib.o cxx.o cygheap.o cygthread.o dcrt0.o debug.o delqueue.o devices.o dir.o dlfcn.o dll_init.o dtable.o environ.o errno.o exceptions.o exec.o external.o fcntl.o fhandler.o fhandler_clipboard.o fhandler_console.o fhandler_disk_file.o fhandler_dsp.o fhandler_fifo.o fhandler_floppy.o fhandler_mem.o fhandler_nodevice.o fhandler_proc.o fhandler_process.o fhandler_random.o fhandler_raw.o fhandler_registry.o fhandler_serial.o fhandler_socket.o fhandler_tape.o fhandler_termios.o fhandler_tty.o fhandler_virtual.o fhandler_windows.o fhandler_zero.o flock.o fnmatch.o fork.o getopt.o glob.o grp.o heap.o init.o ioctl.o ipc.o iruserok.o localtime.o malloc_wrapper.o miscfuncs.o mmap.o msg.o net.o netdb.o ntea.o passwd.o path.o pinfo.o pipe.o poll.o pthread.o regcomp.o regerror.o regexec.o regfree.o registry.o resource.o scandir.o sched.o sec_acl.o sec_helper.o security.o select.o sem.o shared.o shm.o sigfe.o signal.o sigproc.o smallprin!
 t.o spawn.o strace.o strsep.o sync.o syscalls.o sysconf.o syslog.o termios.o thread.o times.o tty.o uinfo.o uname.o v8_regexp.o v8_regerror.o v8_regsub.o wait.o wincap.o window.o setjmp.o /cygdrive/c/Cyg/obj/i686-pc-cygwin/libiberty/random.o /cygdrive/c/Cyg/obj/i686-pc-cygwin/libiberty/strsignal.o malloc.o  version.o winver.o \
>  /cygdrive/c/Cyg/obj/i686-pc-cygwin/winsup/cygserver/libcygserver.a /cygdrive/c/Cyg/obj/i686-pc-cygwin/newlib/libm/libm.a /cygdrive/c/Cyg/obj/i686-pc-cygwin/newlib/libc/libc.a \
> -lgcc /cygdrive/c/Cyg/obj/i686-pc-cygwin/winsup/w32api/lib/libkernel32.a
> 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'
> make[1]: *** [cygwin] Error 1
> make[1]: Leaving directory `/cygdrive/c/Cyg/obj/i686-pc-cygwin/winsup'
> make: *** [all-target-winsup] Error 2
>
> As you can see, there is a segmentation fault in the c++ -o cygwin0.dll
> command and I think this is where the problem lies.
>
> Thanks for your help...
>
> Gabriel
>
> -----Message d'origine-----
> De : cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]De la part
> de Igor Pechtchanski
> Envoye : lundi 12 janvier 2004 18:57
> A : Gabriel SOUBIES
> Cc : cygwin@cygwin.com
> Objet : RE: Problem compiling cygwin1.dll from CVS
>
>
> By "exactly the same build problem" I assume you mean a parse error in
> line 4 of cygwin.def?  Could you please attach (*not* include inline) your
> generated cygwin.def, the output of "cygcheck -svr" on your system, the
> exact flags you're passing to "configure", and the exact command that
> fails?
>         Igor
>
> On Mon, 12 Jan 2004, Gabriel SOUBIES wrote:
>
> > I experienced exactly the same build problem and all my mounts are binary
> > mounts...
> > So far I have not been able go further than this error.
> > If someone can help us, he is really welcome!
> > Thx
> >
> > -----Message d'origine-----
> > De : cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]De la part
> > de Igor Pechtchanski
> > Envoye : vendredi 26 decembre 2003 17:12
> > A : Nuno Ferreira
> > Cc : cygwin@cygwin.com
> > Objet : Re: Problem compiling cygwin1.dll from CVS
> >
> > On Fri, 26 Dec 2003, Nuno Ferreira wrote:
> >
> > > Hi,
> > > while trying to find a problem with an application I'm using (that by
> > > the way was corrected by yesterday's snapshot) I tried to compile the
> > > DLL from CVS and it failed with this error:
> > > [snip]
> > > 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
> > >
> > > The created cygwin.def follows, do you have any ideia what can cause
> > > this problem?
> >
> > At a guess, judging from the CRLF line endings in the first 3 lines,
> > you're trying to build Cygwin on a text mount.  Thus, ld expects to see
> > all lines ending in CRLF.  However, gcc seems to write the defs with LFs
> > explicitly, so ld sees line 4 as one long line, and gives a parse error.
> > I'd suggest moving the build to a binary mount and trying again.
> >
> > > Also, I am experiencing some major memory leaks using the application,
> > > the same application runs flawlessly in linux, does anyone know any tool
> > > (something similar to valgrind) I can use to track the leaks under
> > > cygwin?
> > >
> > > Thank you
> > > --
> > > Nuno
> >
> > Doesn't Cygwin use Doug Lea's malloc?  I thought it had some leak
> > detection routines (or, at least, routines to print memory stats).  Take a
> > look at winsup/cygwin/malloc.cc...
> >         Igor

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]