This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Problem after upgrade to gcc-3.3.3
- From: "Dave Korn" <dk at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Thu, 12 Aug 2004 17:51:52 +0100
- Subject: RE: Problem after upgrade to gcc-3.3.3
> -----Original Message-----
> From: cygwin-owner On Behalf Of Dave Korn
> Sent: 12 August 2004 17:45
> > -----Original Message-----
> > From: cygwin-owner On Behalf Of David Rothenberger
> > Sent: 12 August 2004 17:42
>
> > On 8/12/2004 4:38 AM, Johnny Willemsen wrote:
> > > I just upgraded to gcc-3.3.3 which was available from
> > setup. I now get the
> > > following error:
> > >
> > > g++: installation problem, cannot exec `gm2l': No such file
> > or directory
> > > make[2]: ***
> >
> > I'm seeing the same problem while trying to compile the
> > cygwin DLL from
> > CVS sources. It occurs while trying to link cygwin0.dll.
>
> I noticed in the first example that the g++ command line
> had a linker/dll
> .def file included as one of the files-to-compile.
>
> Apparently '.def' is the standard file extension for modula files, I
> guess.
And indeed it seems that we aren't the first to discover this.
http://floppsie.comp.glam.ac.uk/pipermail/gm2/2004-June.txt
I don't build dlls often, and even less so with gnu tools. What is the
meaning of passing a .def file to the compiler? Since there's nothing in
there to compile, but plenty of symbol names, I wonder, is this just to get
the same .def filename passed through to the linker command-line? Try
prefixing it with "-Wl," if that's the case.
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/