Re: [jamboost] Recent gcc shared lib changes...

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-03-29 19:13:12

----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Friday, March 29, 2002 7:07 PM
Subject: Re: [jamboost] Recent gcc shared lib changes...

> On 2002-03-29 at 06:35 PM, david.abrahams_at_[hidden] (David Abrahams)
wrote:
>
> >When linking shared libs with cygwin, I now get the following
message:
> >
> >gcc-Link-action
>
>c:\build\libs\python\bin\bpl.dll\gcc\debug-python\runtime-link-dynamic\
b
> >pl.dll
>
>c:\build\libs\python\bin\bpl.dll\gcc\debug-python\runtime-link-dynamic\
b
> >pl.lib
> >Creating library file:
>
>c:\build\libs\python\bin\bpl.dll\gcc\debug-python\runtime-link-dynamic\
b
> >pl.lib
> >ln: when making multiple links, last argument must be a directory
> >
> >....and linking fails. Clues?
>
> Arrggg! I really hate sonames now!
>
> It's trying to create the version/unversioned dlls. And failing
because "ln"
> is not a good command to use in CYGWIN. And here I thought it only did
the
> gcc-Link-action in Unix, and used the gcc-dlllwrap otherwise :-(
>
> I'll go fix this now.

Hang on; it might be simpler than you think. I've just checked in a
change which seems to fix it.

-D