Title: Untitled Document
*** URGENT INVESTOR TRADING ALERT ***
WEEKLY STOCK PICK -- GLUV CORP. (Ticker: GLVP)
** BREAKING NEWS **
Coca-Cola and St. Jude Purchase Gluv Corp.'s Golf Gloves
RINGGOLD, Ga., April 6 /PRNewswire-FirstCall/ -- Gluv Corp. (OTC Pink Sheets: GLVP), a leading
Bill Jones wrote:
So the basic question is how do I specify a static import library with a
*.lib extension to be used by libtool for resolving the symbols provided
by a non-libtool DLL when building a dependent DLL with libtool?
The trivial solution is of course to make a copy of the third-party
On Tue, 2004-04-13 at 22:39, Alexandre Duret-Lutz wrote:
> Is it done or is there any obstacle to it? I'm dreaming about
> Automake 1.9, and if possible I would like to include support
> for this.
>
The current interface should be pretty good, trace for invocations of
_LT_TAG and the first argum
On Tue, Apr 13, 2004 at 10:42:05PM +0100, Gary V.Vaughan wrote:
> On 14 Apr 2004, at 18:55, Albert Chin wrote:
>
> >I already have it done for Solaris, HP-UX, Tru64 UNIX, and IRIX. My
> >patch is for the 1.5 branch. I'll forward-port to the 1.6 branch and
> >post the patch in a few days when I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14 Apr 2004, at 18:55, Albert Chin wrote:
On Tue, Apr 13, 2004 at 04:51:22PM +0100, Gary V.Vaughan wrote:
On 13 Apr 2004, at 15:46, Bob Friesenhahn wrote:
On Tue, 13 Apr 2004, Gary V.Vaughan wrote:
So, to accommodate this, how about we use cc to crea
Is it done or is there any obstacle to it? I'm dreaming about
Automake 1.9, and if possible I would like to include support
for this.
All we need is a (preferably documented) way to --trace for the
list of tags that will be understood by the configure-generated
libtool script.
(I think it would
I could not find any recent discussion of this topic in the list archives.
I am trying to use libtool to create a DLL which requires linking my
objects against a non-libtool MS Windows import library provided by a
3rd party vendor. The import library has the ".lib" extension and is in
a separa
On Tue, Apr 13, 2004 at 04:51:22PM +0100, Gary V.Vaughan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 13 Apr 2004, at 15:46, Bob Friesenhahn wrote:
> >On Tue, 13 Apr 2004, Gary V.Vaughan wrote:
>
> So, to accommodate this, how about we use cc to create shared
> libr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Apr 2004, at 15:46, Bob Friesenhahn wrote:
On Tue, 13 Apr 2004, Gary V.Vaughan wrote:
So, to accommodate this, how about we use cc to create shared
libraries on Solaris?
This problem is not specific to Solaris. The same problem occurs on
Digital
On Tue, 13 Apr 2004, Gary V.Vaughan wrote:
> >>
> >> So, to accommodate this, how about we use cc to create shared
> >> libraries on Solaris?
> >
> > This problem is not specific to Solaris. The same problem occurs on
> > Digital Unix, or any other OS where libtool doesn't currently use the
> > C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Apr 2004, at 23:16, Bob Friesenhahn wrote:
On Tue, 13 Apr 2004, Albert Chin wrote:
When linking a C program and using the Sun C compiler, we use the Sun
linker to create a shared libraries. The problem with this is if -mt
is passed to the Sun C co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tristan!
On 12 Apr 2004, at 23:45, Tristan Fillmore wrote:
I am interested in working on libtool to add support for shared
libraries on Interix. I've downloaded the 1.5.6 release, but I don't
see anything as far as a HACKING file...
No, we keep tha
katagenesis kashas keelboats kantars kaolinic kashas. kamperite keerogue kathodes kegler kassabah keelrake. katakiribori kamsin katowice kanga keitloa karyomitoic keenness katathermometer
kayaking karakuls katharses kamias katabella keepsake kampala kasher keenest
kashga kathodal katharsis kar
13 matches
Mail list logo
