Elizabeth Barham wrote:
What is the MSYS-team's view on this?
I'm fine with it and will support the change to a constant. Should that
constant be adjusted based on w9x vs NT?
Earnie.
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.or
"Max Bowsher" <[EMAIL PROTECTED]> writes:
> Don't worry about me! I think we are working towards broadly similar goals -
> it shouldn't be much effort for me to merge the changes you are making into
> my stuff.
What I'm wondering is of there is a better variable to use with the
import library, as
Elizabeth Barham wrote:
>This patch allowed libMagick++ to compile on my machine.
>
>The one thing that concerns me is the name of the import library is
> hard-coded ${lib}.a, which is okay in that the import library looks
> like "qqq.dll.a" but Max has something going about putting DLLs wi
Support Request #100265, was updated on 2001-Dec-31 16:06
You can respond by visiting:
http://savannah.gnu.org/support/?func=detailsupport&support_id=100265&group_id=25
Category: None
Status: Open
Priority: 5
Summary: configure.in missing in CVS tree
By: rboehne
Date: 2002-Oct-11 16:11
Logged
On 11 Oct 2002, Elizabeth Barham wrote:
>This patch allowed libMagick++ to compile on my machine.
Great. I'll give it a try tomorrow.
>The one thing that concerns me is the name of the import library is
> hard-coded ${lib}.a, which is okay in that the import library looks
> like "qqq.dl
Bob, all,
This patch allowed libMagick++ to compile on my machine.
The one thing that concerns me is the name of the import library is
hard-coded ${lib}.a, which is okay in that the import library looks
like "qqq.dll.a" but Max has something going about putting DLLs with
the executables and
Bob Friesenhahn <[EMAIL PROTECTED]> writes:
> The exact same error message is reported without -shared.
>From what I can tell, during configure, there is a check for any
object files that are included in a C++ link. This object file is then
later used to build the shared archive.
If you look at
Hi y'all,
Sorry for being so quiet on this issue. I'm not going to say anything
about 1.4.2, since I'm only familiar with CVS.
Nice of Jaguar to use bash these days, but I still get a lot of broken
tests. I have a couple of fixes at home but I don't know whether they fix
causes or symptoms... an
Elizabeth Barham wrote:
>yes,mingw*)
> -library_names_spec='${libname}`echo ${release} | sed -e
>'s/[[.]]/-/g'`${versuffix}.dll'
> +soname_spec='$libname.dll'
> +library_names_spec='$libname.dll.a'
don't cut away the "release" spec.
libtool link --release 10.56 -o libfoo.la
This is a new patch in attempts to correct the strange behavior,
but note, IT DOES NOT WORK CORRECTLY YET.
I am posting this because I have a very specific question about the
naming of the library. This patch, as it is, causes configure to
print out:
checking which extension is used for shared l
test.
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
I think I have found my source of "unknown error" messages in my program. I
was checking the return value of lt_dlerror() to see if any errors might have
occured. I believe the autobook says this is a good idea. And it used to
work too.
The documentation for lt_dlerror() says:
- Function: cons
12 matches
Mail list logo
