On Tue, 2003-08-26 at 12:58, Albert Chin wrote:
Why not use $srcfile and $srcfile.lock as the lock file? So, rather
than:
They may be on different fs's.
Rob
--
GPG key available at: http://members.aardvark.net.au/lifeless/keys.txt.
___
Libtool
Why not put those functions in a shared library? That's more portable
too (not all platforms play nice with backlinking.)
Rob
-Original Message-
From: Robert Stone [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 12, 2002 5:19 PM
To: [EMAIL PROTECTED]
Subject: dynamic library link
Danny, I hope you don't object to being copied in...
-Original Message-
From: Charles Wilson [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 11, 2002 7:49 AM
To: Bob Friesenhahn
Cc: [EMAIL PROTECTED]; Robert Collins
Subject: Re: C++ exceptions don't work from Cygwin DLLs?
Bob
testoption_SOURCES = tests/testoption.cc
testoption_LDADD = libgetopt++.la
== configure.in ==
dnl
dnl Configuration input file for GetOpt++
dnl
dnl Robert Collins, [EMAIL PROTECTED]
dnl
dnl $Id: configure.in,v 1.5 2002/03/01 12:14:39 robertc Exp $
dnl
dnl
dnl
AC_INIT(src/GetOption.cc)
AC_PREREQ
-Original Message-
From: Michael Matz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 26, 2002 10:12 PM
On a related note. How long do we want to support that cruft
at all? I
mean the pre- and postdeps. Objects and libraries. I'm not
aware of any
current g++ version
- Original Message -
From: Guido Draheim [EMAIL PROTECTED]
Guido, can you succintely describe what impgen does - particularly
in a
cross- environment.
short explanation:
impgen.exe is the first part of an implib.exe - it scans a given dll
for
exported symbols and creates an
to do some
communications to get to know the name of someone who
could tell me by his profound knowledge of dlls and gnu-ld.
and:
Know a wizard who is equally wise on all sides?
Ask Chuck Wilson and Robert Collins from the Cygwin folks.
They have a great interest to get
- Original Message -
From: Jon Leichter [EMAIL PROTECTED]
You may be interested in looking into the auto-import capability
that is
hopefully going into libtool 1.5.
Should I be able to see this in the HEAD branch of CVS? I did a quick
check
for auto-import and didn't find anything
I forgot: The auto import libtool patch is awaiting my FSF contribution
form - which I receieved on Monday, and as the post office is now open
is going in the mail today.
Rob
___
Libtool mailing list
[EMAIL PROTECTED]
You may be interested in looking into the auto-import capability that is
hopefully going into libtool 1.5.
Also, with some automake perl magic the appropriate defines for
libraries can be added automagically to the compile line - I chose
*library*_DLL_IMPORT and *library*_DLL_EXPORT to allow
Interesting!
I'd say that this is because cygwin allocates head for the command line, and
doesn't have a built-in limit (AFAIK).
libtoolers - perhaps the max command line test should stop somewhere before
the multi-megabyte point ?
Rob
- Original Message -
From: Max Bowsher [EMAIL
- Original Message -
From: Guido Draheim [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 20, 2001 3:04 AM
Subject: dll compile, can not resolve with -module libs
As everyone knows, compiling a win-dll requires all references
to be resolved at link-time, and therefore
- Original Message -
From: Ralf Habacker [EMAIL PROTECTED]
To: Cygwin-Apps [EMAIL PROTECTED]; LIBTOOL-Mailinglist
[EMAIL PROTECTED]
Sent: Wednesday, June 13, 2001 10:01 PM
Subject: AW: ask for delivering cygwin 1.1.8 with kde 1.1.2
Ralf Habacker
EMail: [EMAIL PROTECTED]
[EMAIL
- Original Message -
From: Christopher Faylor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, June 11, 2001 6:11 AM
Subject: Re: ld --auto-imports
On Sun, Jun 10, 2001 at 08:35:05PM +0300, Paul Sokolovsky wrote:
RC Firstly the feedback. I'm using a
Paul's patch to ld to auto-import symbols seems to work well. I'm
currently putting it through all the tortuorus combinations I can think
of, that libtool would allow users to do. I've had no trouble so far,
except a small conflict with the dll base address, that was hard to find
but was easy to
The current cygwin shared library installation logic seems to be
install path../bin
This fails for things like l3 in depdemo where the install dir is
extradir = $(libdir)/extra
extra_LTLIBRARIES = libl3.la
I'm not sure what we should use as install logic... maybe walk up the
install path
- Original Message -
From: edward [EMAIL PROTECTED]
To: Robert Collins [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, June 07, 2001 1:22 AM
Subject: Re: dll installation logic
make it a module
cheers,
edward
What will that do for the test case? If the test case is checking
I'm stepping thru the failing tests. A number were automake-HEAD related
as I've mentioned already(*see the end for a refresher)
The current one I'm beating my head against is demo-make after
demo-shared.
Problem summary: libtool is having trouble with the .lo files.
It's finding nothing in
what's the expected behaviour for configure//automake//libtool when it
cannot build a program due to conflicting options
Ie:
1) -static is specified on the link line, but libtool was configured
with --disable-static
2) --no-undefined is specificed on the link line, but libtool was
configured
dlpreopen generates a list of symbols - say
extern char _imp__free;
skip
extern char nothing;
extern char printf;
extern char realloc;
from the source library - cyghello-2.dll
nothing here should be extern __declspec(dllimport) char nothing;
_imp__free shouldn't be present, because the actual
The attached patch auto defines -DLIBfoo_COMPILATION in the _CFLAGS
variable for libtool libraries.
This is a proof of concept patch only, it's probably the wrong way to do
it, there may be issues with always adding the define even if there are
userland defines present. Consider this a
- Original Message -
From: Gary V. Vaughan [EMAIL PROTECTED]
To: Robert Collins [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, June 05, 2001 6:51 AM
Subject: Re: cygwin libtool breakage
On Monday 04 June 2001 2:22 am, Robert Collins wrote
- Original Message -
From: Robert Collins [EMAIL PROTECTED]
- Original Message -
From: Gary V. Vaughan [EMAIL PROTECTED]
To: Robert Collins [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, June 04, 2001 11:25 AM
Subject: Re: cygwin libtool breakage
On Saturday 02
- Original Message -
From: Robert Collins [EMAIL PROTECTED]
- Original Message -
From: Gary V. Vaughan [EMAIL PROTECTED]
On Monday 04 June 2001 2:22 am, Robert Collins wrote:
-Original Message-
From: Gary V. Vaughan [mailto:[EMAIL PROTECTED]]
gary
-Original Message-
From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 05, 2001 10:55 AM
To: Robert Collins
Cc: Gary V. Vaughan; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: cygwin libtool breakage
Robert Collins wrote:
I _did_ have autoconf CVS HEAD
The runtime wrapper on cygwin produces lt-foo.exe.exe if libtool is
called with a target filename ending with .exe
AFAICT this is due to forcing the .exe exeext on cygwin to allow mv to
work. This patch trims .exe from the outputname if it is present.
Without this, changing a source file,
-Original Message-
From: Gary V. Vaughan [mailto:[EMAIL PROTECTED]]
On Saturday 02 June 2001 5:43 pm, Robert Collins wrote:
however, back to the failing tests.
the first failure, demo-make.test fails because ar is called with no
object files.
There was a bug in ltmain.in
Tonights the night for me to cause noise..
I just got the output of make check from another cygwin'er, and they
only see 6 failures, not the 35 I'm seeing.
I'll assume my machine is bust and work from there.
Rob
- Original Message -
From: Robert Collins [EMAIL PROTECTED]
To: [EMAIL
Is this a bug, or a non-existant feature?
symptoms:
automake's makefile calls libtool:
STRIPPROG='strip' /bin/sh ./libtool --mode=install -s hello.exe
/usr/src/hellolib/build/t
/usr/local/bin/hello.exe
libtool: unrecognized option `-s'
Try `libtool --help' for more information.
Rob
There is a current problem with automake and libtool on cygwin when
shared libraries are enabled.
The problem is in two parts. The root cause of the problem is that the
wrapper script for relinking binaries linked with .dll's when they are
run from the build directory, cannot have a .exe
- Original Message -
From: Bruce Korb [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, May 16, 2001 7:00 AM
Subject: Windowed Libtools
Wont be able to develop ... libtool *ON WINDOWS* any more.
So you're agreeing that the generated
- Original Message -
From: Boehne, Robert [EMAIL PROTECTED]
To: 'Robert Collins' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, May 03, 2001 2:30 AM
Subject: RE: to libtool or not: Windows Unix NSAPI program
Robert:
No, I haven't tried to run Libtool
-Original Message-
From: Gary V. Vaughan [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 02, 2001 12:43 PM
To: Libtool
Subject: [ANNOUNCE] libtool-1.3d
After 21 months in heavy development, the Libtool Team is
pleased to announce
alpha release 1.3d of GNU libtool. If this
Hi,
If I want to test libtool 1.4 (I develop on openBSD windows 2K (via cygwin) -
which may be an odd combination :-]), what's the
recommended autoconf version to get?
I saw a message recently about libtool CVS not being autoconf CVS ready which is what
has prompted my question.
Sometime
34 matches
Mail list logo
