RE: [Libevent-users] What's the story with cygevent-1-4-2.dll?

[Chris Brown <chrisb@xxxxxxxxxxxxxx>]

Looks like I was missing -static-libgcc!!!!

Using export CFLAGS='-static -static-libgcc' and everything compiled. Best part is the service started.

Thanks Nick

-----Original Message-----
From: owner-libevent-users@xxxxxxxxxxxxx [mailto:owner-libevent-users@xxxxxxxxxxxxx] On Behalf Of Chris Brown
Sent: Tuesday, 7 September 2010 9:12 AM
To: 'libevent-users@xxxxxxxxxxxxx'
Subject: RE: [Libevent-users] What's the story with cygevent-1-4-2.dll?

Thanks Nick,

I'd like give static linking a go in the short term and watch this space. It looks like this isn't as straightforward on Cygwin as I'd expected.

I've set CFLAGS=-static in order to do this but the configure script then fails
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/cygdrive/c/tmp/gearmand-0.14':
configure: error: C compiler cannot create executables
See `config.log' for more details.

The details from config.log are as follows ...

configure:3898: $? = 1
configure:3918: checking whether the C compiler works
configure:3940: gcc -static   conftest.c  >&5
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld: cannot find -lgcc_s
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld: cannot find -lgcc_s
collect2: ld returned 1 exit status
configure:3944: $? = 1
configure:3982: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "gearmand"
| #define PACKAGE_TARNAME "gearmand"
| #define PACKAGE_VERSION "0.14"
| #define PACKAGE_STRING "gearmand 0.14"
| #define PACKAGE_BUGREPORT "https://launchpad.net/gearmand";
| #define PACKAGE_URL ""
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }

Looks like I'll have to give the Cygwin list a go :(

Cheers
Chris
-----Original Message-----
From: owner-libevent-users@xxxxxxxxxxxxx [mailto:owner-libevent-users@xxxxxxxxxxxxx] On Behalf Of Nick Mathewson
Sent: Tuesday, 7 September 2010 2:28 AM
To: libevent-users@xxxxxxxxxxxxx
Subject: Re: [Libevent-users] What's the story with cygevent-1-4-2.dll?

On Mon, Sep 6, 2010 at 1:36 AM, Chris Brown <chrisb@xxxxxxxxxxxxxx> wrote:
 [...]
> The logfile contains the following ...
>
> /usr/local/sbin/gearmand.exe: error while loading shared libraries: cygevent-1-4-2.dll: cannot open shared object file: No such file or directory
>
> Can anyone explain why gearmand.exe runs from the commandline but not as a service?

I'd guess that the DLL search path is different when you're invoking
it from the cygwin command line and when it's getting run by the NT
service code.  This isn't a libevent issue per se.  To get you
started, you can check out the msdn article at
http://msdn.microsoft.com/en-us/library/7d83bc18(VS.80).aspx , and try
to figure out which of these options is under your control when
running as a service.

Alternatively, if disk space isn't too tight, you could just link your
program against libevent statically, and ignore the DLL issues
completely.

> I've tried running the service using my login credentials (just in case there is something about my environment I'm overlooking) but this fails with a login error.
>
> Also, the cygevent-1-4-2 dlls are in /usr/local/bin; is this correct?

Somebody else might be able to answer this one; I haven't used cygwin in ages.

Re the issues in your other message: it looks like we've got some
timing/DNS portability issues on cygwin.  None of them look like
they're going to break typical programs, but it would be neat if
somebody wanted to track them down sometime and fix them. We've been
doing our windows testing on mingw and msvc, but this is supposed to
be a portability library after all.

hth,
-- 
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.