Re: dll load / rebase issue after 5/24 windows updates

On 5/24/2018 3:50 PM, Brien Oberstein wrote: Greetings, I installed the lastest windows updates on Win2k16 server and now I'm getting the fork/rebase issue. I tried running rebase-trigger / setup.exe multiple times and also reinstalling the libintl8 but the problem persists. Next step to

Re: dll links or pkgconfig/libtool information is wrong

$cygcheck -c libGL1 libGL-devel Cygwin Package Information Package VersionStatus libGL-devel 7.2-2 OK libGL1 7.2-2 OK I'll try to make a small lib that cause the error... but I think that anything that do opengl shall fail thanks JLM

Re: dll links or pkgconfig/libtool information is wrong

jean-luc malet wrote: > On Tue, May 26, 2009 at 6:00 PM, Dave Korn >> jean-luc malet wrote: >>> this dll use 2 others dll : -lglut -lGL >>> $pkg-config.exe --libs gl >>> -lGL >>> but /bin/ contain cygGL-1.dll >>> when static linking with -lGL this works fine because libGL.a exist >>> when creating

Re: dll links or pkgconfig/libtool information is wrong

On Tue, May 26, 2009 at 6:00 PM, Dave Korn wrote: > jean-luc malet wrote: >> hi! >> I'm creating a dll using gcc and cygwin >> this dll use 2 others dll : -lglut -lGL >> $pkg-config.exe --libs gl >> -lGL >> but /bin/ contain cygGL-1.dll >> when static linking with -lGL this works fine because libG

Re: dll links or pkgconfig/libtool information is wrong

jean-luc malet wrote: > hi! > I'm creating a dll using gcc and cygwin > this dll use 2 others dll : -lglut -lGL > $pkg-config.exe --libs gl > -lGL > but /bin/ contain cygGL-1.dll > when static linking with -lGL this works fine because libGL.a exist > when creating the dll -lGL don't work at all, I

Re: dll (.so) not compile

I uninstall and install the cygwin again and still the same thing! What can be? 2009/4/16 Joaquim Pedro França Simão : > Hello, I was trying to compile lighttpd, compile and install normal, > but when I would start, it appeared could not load the module (the > program). >  I also compile the php a

Re: DLL into .a (Metis problem)

Hello I have an experience to build the Metis from source on cygwin. It is not so tough work so that you can get everything if you build the METIS libraries by yourself. However, the Metis license is NOT compatible to GPL. Therefore, the octave community have decided not to use the Metis to con

Re: DLL into .a

Paulo Mota wrote: > Is there a tool to convert a DLL (which has no API Windows calls) into a > lib.a or lib.la ? That is not possible. A DLL is fully linked code. A static library (libfoo.a) is unlinked code. Linking is a one-way process, it removes information that cannot be recovered. A fil

Re: dll libraries marked for random execution?

Linda Walsh wrote: > I'd like to get rid of the "executable" bit being set on files that > are not really executable. Besides being bad practice, it also > creates problems when looking for completion values in the shell. Seem > to remember some other issues related to dll's being marked as > ex

RE: dll libraries marked for random execution?

On 10 July 2007 20:04, Linda Walsh wrote: > Pardon me, but I have some questions about libraries under > cygwin if anyone knows... If there's a doc somewhere that > answers these questions, a pointer to it would be appreciated. Umm, this is all standard stuff but is probably not as well documen

Re: dll link error using Cygwin gcc

Harold Mills wrote: > As Dave Korn and Brian Dessent both pointed out, my problem was that gcc was > compiling Hello.c with the default cdecl calling convention, but the library > I wanted to link to uses the stdcall convention. Adding __stdcall to the > function declarations in the header file ec

RE: dll link error using Cygwin gcc

On 13 June 2007 19:45, Harold Mills wrote: > As Dave Korn and Brian Dessent both pointed out, my problem was that gcc was > compiling Hello.c with the default cdecl calling convention, but the library > I wanted to link to uses the stdcall convention. Adding __stdcall to the > function declaration

Re: dll link error using Cygwin gcc

As Dave Korn and Brian Dessent both pointed out, my problem was that gcc was compiling Hello.c with the default cdecl calling convention, but the library I wanted to link to uses the stdcall convention. Adding __stdcall to the function declarations in the header file eci.h fixed the problem. Dave s

Re: dll link error using Cygwin gcc

Harold Mills wrote: > I'm trying to use Cygwin's gcc to link a small test program (Hello.c) > against a commercial DLL (ibmeci.lib), the source code for which I don't > have. I followed the instructions at www.cygwin.com/cygwin-ug-net/dll.html > to try to build a Cygwin-compatible import library:

RE: dll link error using Cygwin gcc

On 12 June 2007 16:47, Harold Mills wrote: > I get the ld error message "undefined reference to '_eciSpeakText'". The > Hello.c program calls a function 'eciSpeakText'. > > What can I do to fix this? > [EMAIL PROTECTED] Run "info ld" and look for "--enable-stdcall-fixup". cheers,

RE: DLL problems on fresh install

On 22 November 2006 16:38, Scott Hepler wrote: > On Wed, Nov 22, 2006 at 03:23:41PM -, Dave Korn wrote: >> On 22 November 2006 14:28, Scott Hepler wrote: >> >>> On Wed, Nov 22, 2006 at 01:15:44PM -, Dave Korn wrote: >> Or in other words > Problem reports: http:

Re: DLL problems on fresh install

On Wed, Nov 22, 2006 at 03:23:41PM -, Dave Korn wrote: > On 22 November 2006 14:28, Scott Hepler wrote: > > > On Wed, Nov 22, 2006 at 01:15:44PM -, Dave Korn wrote: > > >> Or in other words > >> > >>> Problem reports: http://cygwin.com/problems.html > >> > >> ... get busy wi

RE: DLL problems on fresh install

On 22 November 2006 14:28, Scott Hepler wrote: > On Wed, Nov 22, 2006 at 01:15:44PM -, Dave Korn wrote: >> Or in other words >> >>> Problem reports: http://cygwin.com/problems.html >> >> ... get busy with the cygcheck attachment, dude! > > Heh, cygcheck didn't work either, of c

Re: DLL problems on fresh install

On Wed, Nov 22, 2006 at 02:07:11PM +0100, Corinna Vinschen wrote: > On Nov 22 03:38, Scott Hepler wrote: > > Hi folks: > > > > Sorry to bring what is apparently a FAQ, but I'm stuck. > > > > I had an existing Cygwin install (1.5.?) which I upgraded to 1.5.21-1 via > > setup.exe. I started gettin

Re: DLL problems on fresh install

On Wed, Nov 22, 2006 at 01:15:44PM -, Dave Korn wrote: > On 22 November 2006 13:07, Corinna Vinschen wrote: > > > On Nov 22 03:38, Scott Hepler wrote: > >> Hi folks: > >> > > > > Since you said you searched the machine for another cygwin1.dll, but the > > above message is quite clear, I'm won

Re: DLL problems on fresh install

Corinna Vinschen wrote: > Since you said you searched the machine for another cygwin1.dll, but the > above message is quite clear, I'm wondering if you have some 3PP software > on your machine which installed a cygwin1.dll under another name > together with their 3PP stuff (obfuscating rulez). Di

RE: DLL problems on fresh install

On 22 November 2006 13:07, Corinna Vinschen wrote: > On Nov 22 03:38, Scott Hepler wrote: >> Hi folks: >> >> Sorry to bring what is apparently a FAQ, but I'm stuck. >> >> I had an existing Cygwin install (1.5.?) which I upgraded to 1.5.21-1 via >> setup.exe. I started getting that infamous erro

Re: DLL problems on fresh install

On Nov 22 03:38, Scott Hepler wrote: > Hi folks: > > Sorry to bring what is apparently a FAQ, but I'm stuck. > > I had an existing Cygwin install (1.5.?) which I upgraded to 1.5.21-1 via > setup.exe. I started getting that infamous error: > > -snip- > 7 [main] ? (336) C:\cygwin\bin\bash.exe ***

Re: DLL error messages suppressed under zsh/RXVT

Shankar Unni wrote: > Before sending your cygcheck.out, try checking the archives. > This problem was talked about a couple of months ago. Thanks for the reference. The problem I reported (check the OP) may be related but isn't exactly the same. AFAICT, suppression of those DLL error messages shou

Re: DLL error messages suppressed under zsh/RXVT

Williams, Gerald S (Jerry) wrote: $ mv cygcrypto-0.9.8.dll cygcrypto-0.9.8.dll.NOT $ ./openssl $ No popups or error messages, just silently exits. Before sending your cygcheck.out, try checking the archives. This problem was talked about a couple of months ago. See the thread starting w

Re: DLL error messages suppressed under zsh/RXVT

On Fri, 22 Sep 2006, Williams, Gerald S (Jerry) wrote: I recently ran into a problem where DLL error messages were apparently suppressed under zsh/RXVT though they appeared under bash/CONSOLE. How about under zsh/CONSOLE? I was trying to build Subversion 1.4.0, and it at one point configure

Re: DLL loading problem with binutils-20060709-1

--- Bill Metzenthen <[EMAIL PROTECTED]> wrote: > > > I have been developing a mixed python / C++ program > which uses SWIG to > handle the interface. This worked fine until I > updated binutils to > 20060709-1. Then when the python script tried to > load the DLL generated > with the help of SW

Re: dll version 1.5.19

at 4:39 PM, Karl M wrote: Hi Laura... If you are waiting on a particulay bug fix, you can verify that it works with a snapshot. Otherwise you may not get what you are waiting for. HTH, ...Karl From: Laura Schneider Subject: Re: dll version 1.5.19 Date: Mon, 19 Dec 2005 15:58:00 -0800 Than

Re: dll version 1.5.19

Hi Laura... If you are waiting on a particulay bug fix, you can verify that it works with a snapshot. Otherwise you may not get what you are waiting for. HTH, ...Karl From: Laura Schneider Subject: Re: dll version 1.5.19 Date: Mon, 19 Dec 2005 15:58:00 -0800 Thank you for the quick

Re: dll version 1.5.19

Thank you for the quick response! laura On Dec 19, 2005, at 3:52 PM, Larry Hall (Cygwin) wrote: Laura Schneider wrote: Hi, I am wondering if you can give me an idea of when the next dll will be released? We are waiting on a bug fix. Should be "soon" but I personally can't be more precise

Re: dll version 1.5.19

Laura Schneider wrote: > The information contained in this transmission is privileged and/or > confidential information intended for the use of the individual or entity > named above. If the reader of this message is not the intended recipient, you > are hereby notified that any use, distributi

Re: dll v so?

Siegfried Heintze wrote: > I'm confused about dll v. so and cygwin. I've used the documentation to > create and load dlls with g++. > > However, I notice that Apache Httpd uses ".so" files. Is the choice to > produce ".dll" or ".so" files purely a matter of who is going to load them? It's just t

Re: dll version mismatch

At 03:24 PM 3/17/2005, you wrote: >Hi, > >I looked around and couldn't find this info anywhere, sorry in advance if >it's a simple question. > >I am using GNAT GDB on windows. Apparently it was built with cygwin. > [EMAIL PROTECTED] /cygdrive/c/GNAT] $ cygcheck 'C:\GNAT\bin\gdb.exe' > C:/GNAT/

Re: DLL rebase required?

Maarten, Please post instead of sending private email. On Wed, Oct 06, 2004 at 01:10:53PM +0400, Maarten Boekhold wrote: > I wanted to run this by you before I hose my system with a potentially > unnecessary rebaseall... > > I'm porting XFCE to cygwin/X, most of it is running perfectly now. One

Re: DLL info

Emanuele, It is generally better to send questions and comments regarding Cygwin to the main Cygwin mailing list at . Not only will you get access to the combined expertise of the list, which is more than any one person can provide, but your questions, and answers to them, will also be archived o

Re: dll version collision - my old and now broken solution

On Sat, May 29, 2004 at 10:27:43AM +0100, Max Bowsher wrote: >Attached is my patch, updated to apply cleanly (though not to work!) >with current CVS. In case it isn't obvious, this patch is just a brute force kludge. Half of the changes aren't even necessary. I'm not sure what the patch buys you

Re: dll version collision - my old and now broken solution

Hello, Max! Thanks much for the info and the patch, this was much more than I'd expected. I'll try to look at this towards the end of June. With kind regards, Baurjan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Docume

Re: dll version collision

Hello, Igor! On Thu, May 27, 2004 at 06:33:20PM -0400, Igor Pechtchanski wrote: > > * It isn't possible with the current cygwin. > It is possible, but non-trivial. Well, I've meant the binary DLL installed using setup. > One way to have Cygwin automatically modify the shared memory area name is

Re: dll version collision

On Fri, May 28, 2004 at 03:58:09PM -0400, Christopher Faylor wrote: > UML is not linux. It is a mechanism for running linux in userspace. Well, the point was that it can be used for testing. I haven't said it was linux, although for me it more or less is, as long as my kernel module or applicatio

Re: dll version collision

On Fri, May 28, 2004 at 09:46:34PM +0200, Baurjan Ismagulov wrote: >On Fri, May 28, 2004 at 03:05:50PM -0400, Christopher Faylor wrote: >>You use the same technique as if you were testing another version of >>linux. Or you'd backup your system prior to updating cygwin. It is >>not likely that you

Re: dll version collision

Hello, Christopher! On Fri, May 28, 2004 at 03:05:50PM -0400, Christopher Faylor wrote: > You use the same technique as if you were testing another version of > linux. Or you'd backup your system prior to updating cygwin. It is not > likely that you could have two installations running on the sa

Re: dll version collision

On Fri, May 28, 2004 at 01:31:34PM -0400, Michael Hale wrote: >On May 28, 2004, at 1:15 PM, Christopher Faylor wrote: >>On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote: >>>The ideas suggested here are definitely beyond my current ability. I >>>hope someone else who would like this don

Re: dll version collision

On May 28, 2004, at 2:17 PM, Reini Urban wrote: Michael Hale schrieb: What is the correct way for someone to run multiple versions of cygwin on their machine then? There's none! That is too bad. I guess that means I will have to worry about varying environments in our build process. At least un

Re: dll version collision

Michael Hale schrieb: What is the correct way for someone to run multiple versions of cygwin on their machine then? There's none! > This seems like a very useful feature to me, since among other uses it would allow a new version to be tested along side an older but known version of cygwin. Kill

Re: dll version collision

On May 28, 2004, at 1:15 PM, Christopher Faylor wrote: On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote: The ideas suggested here are definitely beyond my current ability. I hope someone else who would like this done, and has the skill will take it up. If it is beyond your abilities t

Re: dll version collision

On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote: >The ideas suggested here are definitely beyond my current ability. I >hope someone else who would like this done, and has the skill will take >it up. If it is beyond your abilities then you shouldn't be considering this option. Thi

Re: dll version collision

The ideas suggested here are definitely beyond my current ability. I hope someone else who would like this done, and has the skill will take it up. On May 27, 2004, at 6:33 PM, Igor Pechtchanski wrote: On Thu, 27 May 2004, Baurjan Ismagulov wrote: Hello, Michael! On Thu, May 27, 2004 at 04:53:1

Re: dll version collision

On Thu, 27 May 2004, Baurjan Ismagulov wrote: > Hello, Michael! > > On Thu, May 27, 2004 at 04:53:17PM -0400, Michael Hale wrote: > > Is it possible to recompile a subset of the cygwin binaries to depend > > on cygwin1.dll renamed to something like build_cygwin1.dll? How would > > I go about doin

Re: dll version collision

Hello, Michael! On Thu, May 27, 2004 at 04:53:17PM -0400, Michael Hale wrote: > Is it possible to recompile a subset of the cygwin binaries to depend > on cygwin1.dll renamed to something like build_cygwin1.dll? How would > I go about doing this? This is a quite often-discussed topic, but ther

RE: DLL generation under Cygwin

On Wed, 5 May 2004, Ted Yu wrote: > Hi, Igor: > > . This is what you invoke when you give the > > -mno-cygwin flag to gcc. Incidentally, once you > > Does this mean I need to install MinGW runtime ? Yes, to be able to use "gcc -mno-cygwin". > > That's because you use "ld" in

RE: DLL generation under Cygwin

Hi, Igor: > . This is what you invoke when > you give the > -mno-cygwin flag to gcc. Incidentally, once you Does this mean I need to install MinGW runtime ? > That's because you use "ld" instead of "gcc". "gcc" > (with appropriate > flags, i.e., "-mno-cygwin") should do the

RE: DLL generation under Cygwin

On Wed, 5 May 2004, Ted Yu wrote: > Hi, Igor: > > So does MSVCRT.dll, which is what MinGW uses for its > > runtime. > > I am not familiar with MinGW. What is it ? . This is what you invoke when you give the -mno-cygwin flag to gcc. Incidentally, once you eliminate Cygwin from

RE: DLL generation under Cygwin

Hi, Igor: > So does MSVCRT.dll, which is what MinGW uses for its > runtime. I am not familiar with MinGW. What is it ? > Why are you linking in libc.a explicitly? The > appropriate version should > be automatically linked in by the compiler. If I omit libc.a, I get this: ld: warning: cannot find

RE: DLL generation under Cygwin

On Wed, 5 May 2004, Ted Yu wrote: > Hi, > I deleted .o files and compiled with -mno-cygwin. > cygwin1.dll is still needed because it contains > malloc() and free() which are used in my DLL. So does MSVCRT.dll, which is what MinGW uses for its runtime. > Here is my Makefile: > OBJS = \ >

RE: DLL generation under Cygwin

Hi, I deleted .o files and compiled with -mno-cygwin. cygwin1.dll is still needed because it contains malloc() and free() which are used in my DLL. Here is my Makefile: OBJS = \ 8d0.o 8d1.o 8d2.o \ 8c0.o 8c1.o 8c2.o \ 8r0.o 8r1.o 8r2.o \ 8u0.o 8u1.o 8u2.o \ 8

RE: DLL generation under Cygwin

> -Original Message- > From: cygwin-owner On Behalf Of Ted Yu > Sent: 04 May 2004 20:23 > Hi, Larry: > If I use your flag, I got the following: > ld: warning: cannot find entry symbol [EMAIL PROTECTED]; > defaulting to 10001000 > djbfft2d.o(.text+0x4d3):djbfft2d.cpp: undefined > reference

Re: DLL generation under Cygwin

Hi, Larry: If I use your flag, I got the following: ld: warning: cannot find entry symbol [EMAIL PROTECTED]; defaulting to 10001000 djbfft2d.o(.text+0x4d3):djbfft2d.cpp: undefined reference to `_imp___iob' djbfft2d.o(.text+0x50a):djbfft2d.cpp: undefined reference to `_imp___iob' BTW, I have this f

Re: DLL generation under Cygwin

y 2004 18:41:58 -0700 >Received: from [192.146.1.16] by web12103.mail.yahoo.com via HTTP; Mon, 03 May 2004 >18:41:58 PDT >Date: Mon, 3 May 2004 18:41:58 -0700 (PDT) >From: Ted Yu <[EMAIL PROTECTED]> >Subject: Re: DLL generation under Cygwin >To: DJ Delorie <[EMAIL PROTEC

Re: DLL vs. shared object linking behavior

At 06:19 AM 1/4/2004, Jani Tiainen you wrote: >Karl Robillard wrote: > >>I have a shared library which has undefined references to functions. On Linux I can >>build and use the library without problems, but when I build it as a DLL using >>Cygwin the undefined references are link errors. Can th

Re: DLL vs. shared object linking behavior

Karl Robillard wrote: I have a shared library which has undefined references to functions. On Linux I can build and use the library without problems, but when I build it as a DLL using Cygwin the undefined references are link errors. Can the Windows loader handle unresolved symbols in DLLs at

Re: DLL and external symbols

From: Jani Tiainen > > > Hi, > > I'm sure that this has been answered several times, but I'll ask again because couldn't find any solution by myself. > > I would like to build DLL (or any other sort of library) th

Re: DLL and external symbols

Jani Tiainen wrote: Larry Hall wrote: At 04:35 PM 12/30/2003, Jani Tiainen you wrote: Hi, I'm sure that this has been answered several times, but I'll ask again because couldn't find any solution by myself. I would like to build DLL (or any other sort of library) that refers to external symb

Re: DLL and external symbols

Larry Hall wrote: At 04:35 PM 12/30/2003, Jani Tiainen you wrote: Hi, I'm sure that this has been answered several times, but I'll ask again because couldn't find any solution by myself. I would like to build DLL (or any other sort of library) that refers to external symbols in main application.

Re: DLL and external symbols

At 04:35 PM 12/30/2003, Jani Tiainen you wrote: >Hi, > >I'm sure that this has been answered several times, but I'll ask again because >couldn't find any solution by myself. > >I would like to build DLL (or any other sort of library) that refers to external >symbols in main application. > >So far

Re: DLL and VB problems

The options I gave to gcc are: For building the DLL: gcc -c -o dllhello.o dllhello.c gcc -shared -o dllhello.dll dllhello.o -Wl,--out-implib,libdllhello.a For building the program: gcc -c -o hello.o hello.c gcc -mwindows -o hello.exe hello.o -L. -ldllhello The GCC version I am using is: gcc (GC

Re: DLL and VB problems

Hello, Please ignore my previous message; I made a mistake in the client C file. I corrected it, and the C client calls the DLL perfectly. But I tried calling from a VB client, and it works fine for the first time; Running again causes the application to close. Any insight would be greatly ap

Re: DLL and VB problems

Hello, I am sorry that I am not very clear... Below is the problem: I wrote C client to this dll and when I try to compile the client to use the dll using the command: gcc -o hello.exe hello.o -L. -ldllhello, I get the following error: /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libcygwin.a

Re: DLL and VB problems

On Thu, 16 Oct 2003, Paul Bezzam wrote: > Hello, > > I have created a DLL using gcc on Cygwin, and I wrote a client in VB > accessing this DLL. The application runs fine for the first time, but > when run again, it crashes. I have to close the application and run it to > work successfully. > > C

RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

Hmm... I can't remember if there is a equiv. of $@ in DOS/BAT-files... WinNT/2k/XP: %* is the cmd.exe equivalent to bash $@ Have fun, Felix -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro:K@N@!:

Exactly. That's why I mentioned using ctags directly in Doing so should remove the magic, mystery, and the problem. Larry Jeffery B. Rancier wrote: "Hannu E K Nevalainen (garbage mail)" <[EMAIL PROTECTED]> writes: The solution which should

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro:K@N@!:

"Hannu E K Nevalainen (garbage mail)" <[EMAIL PROTECTED]> writes: The solution which should have been much more obvious to me is to use ctags.exe with the '-e' option. I'm assuming etags is a link to ctags. Jeff >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf >> Of Igor Pechtchanski

RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro:K@N@!:

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Igor Pechtchanski --8<-- > What you could do is create an "etags.bat" that runs 'bash -c etags "%1" > "%2" "%3" "%4" "%5" "%6" "%7" "%8" "%9"', put it in your PATH, and you > should be able to call that from NTEmacs. > Igor Hm

RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

x27;s there for those cases when you need to write it in batch. stephan(); -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hannu E K Nevalainen (garbage mail) Sent: Sunday, July 27, 2003 5:17 AM To: [EMAIL PROTECTED] Subject: RE: DLL 1.3.22 - etags 5.5.4

RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

> From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] > Sent: Sunday, July 27, 2003 2:22 AM > On Sat, 26 Jul 2003, Hannu E K Nevalainen (garbage mail) wrote: > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf > > > Of Igor Pechtchanski > > > > --8<-- > > > What you could do is create

RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

On Sat, 26 Jul 2003, Hannu E K Nevalainen (garbage mail) wrote: > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > > Of Igor Pechtchanski > > --8<-- > > What you could do is create an "etags.bat" that runs 'bash -c etags "%1" > > "%2" "%3" "%4" "%5" "%6" "%7" "%8" "%9"', put it in your

RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Igor Pechtchanski --8<-- > What you could do is create an "etags.bat" that runs 'bash -c etags "%1" > "%2" "%3" "%4" "%5" "%6" "%7" "%8" "%9"', put it in your PATH, and you > should be able to call that from NTEmacs. > Igor Hm

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

On Thu, 24 Jul 2003, Jeffery B. Rancier wrote: > Igor Pechtchanski <[EMAIL PROTECTED]> writes: > > > On Wed, 23 Jul 2003, Jeffery B. Rancier wrote: > > > >> Larry Hall <[EMAIL PROTECTED]> writes: > >> > >> > It's not a bug, unless you consider a Windows program not being able to > >> > understand

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

Igor Pechtchanski <[EMAIL PROTECTED]> writes: > On Wed, 23 Jul 2003, Jeffery B. Rancier wrote: > >> Larry Hall <[EMAIL PROTECTED]> writes: >> >> > It's not a bug, unless you consider a Windows program not being able to >> > understand Cygwin symbolic links a bug. I don't think there is much >> >

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

On Wed, 23 Jul 2003, Jeffery B. Rancier wrote: > Larry Hall <[EMAIL PROTECTED]> writes: > > > It's not a bug, unless you consider a Windows program not being able to > > understand Cygwin symbolic links a bug. I don't think there is much > > chance of changing Windows to permit all applications a

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

Larry Hall <[EMAIL PROTECTED]> writes: > It's not a bug, unless you consider a Windows program not being able to > understand Cygwin symbolic links a bug. I don't think there is much > chance of changing Windows to permit all applications a proper understanding > though. I see. Why does it work

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

Jeffery B. Rancier wrote: [EMAIL PROTECTED] (Jeffery B. Rancier) writes: It appears the list maintainer zapped my text? Here it is again: I installed ctags 5.5 today, after having problems with the Gnus Emacs etags not recognizing my cygwin mounts. It seems to work OK, but three times I receive

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

Jeffery B. Rancier wrote: -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ As a note for future reference, it is generally ver

Re: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

[EMAIL PROTECTED] (Jeffery B. Rancier) writes: It appears the list maintainer zapped my text? Here it is again: I installed ctags 5.5 today, after having problems with the Gnus Emacs etags not recognizing my cygwin mounts. It seems to work OK, but three times I received the following Windows e

Re: .dll and .lib files

On Tue, 10 Jun 2003, Larry Hall wrote: > Paul G. wrote: > > > >>Is there a reason to respond to a posting with guesses? > >> > >>Just curious. > > > > > > Curiosity killed the cat... > > > > Guess it is safer to not say anything than to say what may be true... > > I'll buy that. Will

Re: .dll and .lib files

> Paul G. wrote: > > > >>Is there a reason to respond to a posting with guesses? > >> > >>Just curious. > > > > > > Curiosity killed the cat... > > > > Guess it is safer to not say anything than to say what may be > > true... > > > > I'll buy that. Will you take a dead cat as paym

Re: .dll and .lib files

Paul G. wrote: Is there a reason to respond to a posting with guesses? Just curious. Curiosity killed the cat... Guess it is safer to not say anything than to say what may be true... I'll buy that. Will you take a dead cat as payment? -- Larry Hall http://www

Re: .dll and .lib files

> Is there a reason to respond to a posting with guesses? > > Just curious. Curiosity killed the cat... Guess it is safer to not say anything than to say what may be true... Paul G. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

Re: .dll and .lib files

Is there a reason to respond to a posting with guesses? Just curious. Larry Paul G. wrote: Just a guess... You can't build MS .lib files using Cygwin utilities. You can link older .lib files using, at the very least, -mno-cygwin switch. Again, this is just a guess. As to .dlls, again, jus

Re: .dll and .lib files

Just a guess... You can't build MS .lib files using Cygwin utilities. You can link older .lib files using, at the very least, -mno-cygwin switch. Again, this is just a guess. As to .dlls, again, just a guess, you can build as many of those as you want, but they will not be th

Re: DLL calling a DLL: undefined reference when linking.

> That didn't seem to work. I'm still confused as to why the > --enable-stdcall-fixup flag doesn't appear to be working. > > [...] > > > > Both the extern prototype and the function call are in dllhello.C. > Thus > it > > does see the prototype. As a further note and after further testing, > if

Re: DLL calling a DLL: undefined reference when linking.

> "Elfyn McBratney" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > I think I'm making marvelous progress. Unfortunately, I'm getting > an > > > error that doesn't make sense: > > > > > > $g++ -shared -mno-cygwin -o dllhello.dll dllhello.o > > > other.dll -Wl,--out-implib,l

Re: DLL calling a DLL: undefined reference when linking.

"Elfyn McBratney" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I think I'm making marvelous progress. Unfortunately, I'm getting an > > error that doesn't make sense: > > > > $g++ -shared -mno-cygwin -o dllhello.dll dllhello.o > > other.dll -Wl,--out-implib,libdllhello.a -Wl

Re: DLL calling a DLL: undefined reference when linking.

> I think I'm making marvelous progress. Unfortunately, I'm getting an > error that doesn't make sense: > > $g++ -shared -mno-cygwin -o dllhello.dll dllhello.o > other.dll -Wl,--out-implib,libdllhello.a -Wl,--enable-stdcall-fixup > Creating library file: libdllhello.a > dllhello.o(.text+0x164)

Re: DLL calling a DLL: undefined reference when linking.

Wil Hunt wrote: Hello again, I think I'm making marvelous progress. Unfortunately, I'm getting an error that doesn't make sense: $g++ -shared -mno-cygwin -o dllhello.dll dllhello.o other.dll -Wl,--out-implib,libdllhello.a -Wl,--enable-stdcall-fixup Creating library file: libdllhello.a dllhell

Re: dll not found when "symlink" used?

On Wed, 27 Nov 2002, Max Bowsher wrote: > Please keep mail on list. > > Bob Tanner <[EMAIL PROTECTED]> wrote: > > On Tuesday 26 November 2002 04:39 pm, Max Bowsher wrote: > >>> I guess I'm looking for conformation that cygwin binaries do not > >>> honor the symlinks. > >> > >> Sure, cygwin binarie

Re: dll not found when "symlink" used?

Please keep mail on list. Bob Tanner <[EMAIL PROTECTED]> wrote: > On Tuesday 26 November 2002 04:39 pm, Max Bowsher wrote: >>> I guess I'm looking for conformation that cygwin binaries do not >>> honor the symlinks. >> >> Sure, cygwin binaries do. But *only* Cygwin binaries. And the >> Windows DLL

Re: dll not found when "symlink" used?

Bob Tanner <[EMAIL PROTECTED]> wrote: > Pretty new to cygwin, so I'm not 100% sure how these symlinks work. > View the symlink under cygwin-bash, things look right, but when I > look at the files under Windows Explorer, they are just .lnk file. > > My question is, do cygwin binaries understand and

Re: dll for Windows

Get the libtool packages from setup, then read http://www.gnu.org/software/libtool/libtool.html and http://sources.redhat.com/autobook/ G "Stefan Hansen" <[EMAIL PROTECTED]> wrote in message news:02102720005100.02282@;Poldi... > Hi, > > my last question about compiling a dll for Windows with cygw

Re: .dll question

On 10/2/2002 4:19 PM, Robert Collins wrote: > No it can't. In general, C++ compilers don't interoperate. The C++-Lite > FAQ has a section on this. > From memory, the issues are: > *VMT layout > [..] And before someone jumps up and asks why this can't be reverse engineered - apart from the gene

Re: .dll question

Thank you, Rob. On 3 Oct 2002 at 9:19, Robert Collins wrote: > On Thu, 2002-10-03 at 09:13, Paul G. wrote: > > > On a related note, can Cygwin generate c++ .dlls which are loadable by msvc++ >or > > does Microsofts' method of name mangling prohibit such things? > > No it can't. In gener

  1   2   >