public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Gary V. Vaughan" <gvv@techie.com>
Cc: <cygwin@sources.redhat.com>
Subject: Re: libtool
Date: Sat, 09 Sep 2000 19:44:00 -0000	[thread overview]
Message-ID: <014501c01ad1$232a36b0$f7c723cb@lifelesswks> (raw)
In-Reply-To: <20000909134149.T26790@demon.co.uk>

You might find this amusing

libtool 1.3.5 from ftp.gnu.org when configuring
...
checking dynamic linker characteristics... Win32 ld.exe
checking if libtool supports shared libraries... yes
checking if package supports dlls... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes

so it won't dllise itself :-]

Rob

----- Original Message -----
From: "Gary V. Vaughan" <gvv@techie.com>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <cygwin@sources.redhat.com>
Sent: Saturday, September 09, 2000 11:41 PM
Subject: Re: libtool


> On Sat, Sep 09, 2000 at 09:42:38PM +1100, Robert Collins wrote:
> >     Other than hanging on make check your tar.gz built fine for me...
>
> You need to force it to use the supplied getopts files -- the system
> ones seem to be buggy.  Try this:
>
>   ac_cv_func_getopt_long=no ./configure --with-modules --disable-nls
>
>
> > how can I take the libtool you have in that archive and apply it to
> > (say glib or orbit)?
>
> You can extract the parts of libtool.m4 and ltdl.m4 from aclocal.m4
> and add them to acinclude.m4 in your glib $top_srcdir.  This stuff is
> between the definitions of AC_PROG_LIBTOOL and the end of
> AC_LTDL_SYMBOL_USCORE.  You should then copy the ltconfig and
> ltmain.sh from m4-1.4p over the versions you have in glib.
>
> aclocal
> automake
> autoconf
>
> and be careful not to clobber your hard work by running libtoolize!
>
> > I realise exported variables need to be wrapped with declspec(dllexport)
> > before building the dll but I thought you had the functions being done
> > automatically? Is that an incorrect assumption?
>
> You assumption is correct.  Gcc takes care of non-data exports.
>
> HTH,
> Gary.
> --
>   ___              _   ___   __              _         mailto:
gvv@techie.com
>  / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___
gary@gnu.org
> | (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
>  \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
> home page:  /___/                      /___/                  gpg public
key:
> http://www.oranda.demon.co.uk
http://www.oranda.demon.co.uk/key.asc
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-09-09 19:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-07  6:34 libtool Earnie Boyd
2000-09-07 11:12 ` libtool Gary V. Vaughan
2000-09-07 14:02   ` libtool Robert Collins
2000-09-07 14:15     ` libtool Chris Faylor
2000-09-07 14:25       ` libtool Robert Collins
2000-09-07 17:56     ` libtool Charles S. Wilson
2000-09-07 17:28   ` libtool Gary V. Vaughan
2000-09-09  3:42     ` libtool Robert Collins
2000-09-09 14:15       ` libtool Gary V. Vaughan
2000-09-09 19:44         ` Robert Collins [this message]
2000-09-10 10:23     ` libtool Charles S. Wilson
2000-09-12  0:28       ` libtool Gary V. Vaughan
  -- strict thread matches above, loose matches on Subject: below --
2000-09-13  6:44 libtool Earnie Boyd
2000-09-05  6:47 libtool Robert Collins
2000-09-07  0:20 ` libtool Gary V. Vaughan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='014501c01ad1$232a36b0$f7c723cb@lifelesswks' \
    --to=robert.collins@itdomain.com.au \
    --cc=cygwin@sources.redhat.com \
    --cc=gvv@techie.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).