From: "Gary V. Vaughan" <gvaughan@oranda.demon.co.uk>
To: Jorrit Tyberghein <Jorrit.Tyberghein@uz.kuleuven.ac.be>
Cc: gnu-win32@cygnus.com, Geoffrey Noer <noer@cygnus.com>
Subject: Re: dlopen
Date: Fri, 30 Oct 1998 05:08:00 -0000 [thread overview]
Message-ID: <3639AEEB.855AC45C@oranda.demon.co.uk> (raw)
In-Reply-To: <36386742.E14F6F22@uz.kuleuven.ac.be>
Jorrit Tyberghein wrote:
>
> How can I use dlopen/dlsym/dlcose from CygWinB19 with EGCS 1.1?
> I can't find a reference to dlopen in any of the include files
> although it seems to be in some of the executables/libraries?
The dlfcn.h file from the source distribution never made it into
the cdk.exe. You need to get the cygwin32 sources from the same
place as you got the cdk and copy the dlfcn.h file into
$CYGWIN_ROOT/H-i386-cygwin32/i386-cygwin32/include. Then dlopen
and friend will (mostly) work as usual.
Geoffrey, I notice that the dlopen emulation doesn't handle a NULL
argument as per the POSIX spec (i.e. return an introspective handle
to the current process), yet the win32 GetModuleHandle does... will this
be fixed for b20? Too late for a patch?
Cheers,
Gary V. Vaughan
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1998-10-30 5:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-29 5:02 dlopen Jorrit Tyberghein
1998-10-30 5:08 ` Gary V. Vaughan [this message]
1998-10-30 16:19 ` dlopen Geoffrey Noer
1998-11-11 3:57 ` dlopen patch [was Re: dlopen] Gary V. Vaughan
1998-11-11 4:22 ` Christian Jullien
1998-11-15 23:41 ` Mumit Khan
1998-11-16 6:12 ` Christian Jullien
2001-02-01 14:33 dlopen Alejandro Conty
2002-01-28 1:58 dlopen BERTRAND Joël
2002-01-28 3:00 ` dlopen Pavel Tsekov
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=3639AEEB.855AC45C@oranda.demon.co.uk \
--to=gvaughan@oranda.demon.co.uk \
--cc=Jorrit.Tyberghein@uz.kuleuven.ac.be \
--cc=gnu-win32@cygnus.com \
--cc=noer@cygnus.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).