DLL problem

DLL problem

[Stephane Mariel]

Hi,

I'm trying to port a unix network tool (at least the client) to Win95/NT ,
since there is a DLL to create, I tested the example provided on
www.cygnus.com.

It works fine, i got my foo.dll, main.exe, but moving to my real software
when I run ld for the first time I got

c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libccrt0.o)(.t
ext+0x8a):libccrt0.cc: undefined reference to `GetModuleHandleA@4'
c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
ext+0xc):libcmain.cc: undefined reference to `GetModuleHandleA@4'
c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
ext+0x15):libcmain.cc: undefined reference to `GetCommandLineA@0'
c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
ext+0x1e):libcmain.cc: undefined reference to `WinMain@16'

I probably should say to ld something like, there would be a winmain
elsewhere, and I will use the right winapi.dll when running the program?

It's probably not very difficult, but i'm not very familiar with all the
Win stuff, so  any idea?

Thanks,

stf

 

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: DLL problem

[Fergus Henderson]

Stephane Mariel, you wrote:
> I'm trying to port a unix network tool (at least the client) to Win95/NT ,
> since there is a DLL to create, I tested the example provided on
> www.cygnus.com.
> 
> It works fine, i got my foo.dll, main.exe, but moving to my real software
> when I run ld for the first time I got
> 
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libccrt0.o)(.t
> ext+0x8a):libccrt0.cc: undefined reference to `GetModuleHandleA@4'
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
> ext+0xc):libcmain.cc: undefined reference to `GetModuleHandleA@4'
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
> ext+0x15):libcmain.cc: undefined reference to `GetCommandLineA@0'
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
> ext+0x1e):libcmain.cc: undefined reference to `WinMain@16'

This occurs because there is no definition for `_impure_ptr' in your DLL.
See < http://www.cs.mu.oz.au/~fjh/gnu-win32/how-to-build-dlls.html >
for a brief explanation about `_impure_ptr'.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >   |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: DLL problem

[Charles Wilson]

Morris, Steve wrote:

>  > Maybe you should search the mailing list archive more
>  > often when you encounter a problem.
>  > 
>  > Just a quick hint - there was at least one post a day
>  > in the last week about your problem.
> 
> This kind of post to the list is a total waste of bandwidth. Reply in
> private if you can't merely find the delete key. This educates the offender
> without wasting everyone elses time. Otherwise if you are not willing to
> help just shut up. This is a prevalent problem on this list. There are as
> many people posting simple RTFM responses as there are people who are
> unwilling to RTFM. They are equally abusive of this list.

No.  RTFM responses (and STFW and STFMLA) SHOULD go on the list.  The 
problem is, you only need ONE.  There's no need to pile on.  If the 
obvious answer to a question is RTFM, and someone has already posted 
that, there's no need for you to do so.  The only time there should be 
multiple RTFM responses to the same person's question is when duplicate 
responses "cross in the mail".

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: DLL problem

[Morris, Steve]

 > Maybe you should search the mailing list archive more
 > often when you encounter a problem.
 > 
 > Just a quick hint - there was at least one post a day
 > in the last week about your problem.

This kind of post to the list is a total waste of bandwidth. Reply in
private if you can't merely find the delete key. This educates the offender
without wasting everyone elses time. Otherwise if you are not willing to
help just shut up. This is a prevalent problem on this list. There are as
many people posting simple RTFM responses as there are people who are
unwilling to RTFM. They are equally abusive of this list.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: DLL problem

[Mark Himsley]

On Thu, 29 Nov 2001 11:24:30 -0500 you wrote:

>Actually, I just starting subscribing to the list yesterday... when I
>figured out that something might be wrong.

Does that stop you from searching the mailing lists at
http://cygwin.com/ml/cygwin/ ?


>Anthony N. Gerkis
>SOMA Networks, Inc.
>312 Adelaide St. W, Suite 700
>Toronto, Canada M5V 1R2
>agerkis@somanetworks.com
>(416) 348-1591
>
>-----Original Message-----
>From: ptsekov [ mailto:ptsekov]On Behalf Of Pavel Tsekov
>Sent: Thursday, November 29, 2001 11:21 AM
>To: Anthony Gerkis
>Cc: Nicholas Down; cygwin@cygwin.com
>Subject: Re: DLL problem
>
>
>Maybe you should search the mailing list archive more
>often when you encounter a problem.
>
>Just a quick hint - there was at least one post a day
>in the last week about your problem.
>
>Anthony Gerkis wrote:
>>
>> I am also experiencing this problem. I had to move back vim 5.8.9 (still
>can
>> get off ftp servers) to make vim usage at all...
>>
>> -----Original Message-----
>> From: cygwin-owner@sources.redhat.com
>> [ mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
>> Sent: Thursday, November 29, 2001 10:23 AM
>> To: cygwin@cygwin.com
>> Subject: DLL problem
>>
>> Dear Cygwin,
>>
>>  I am getting the following message when trying to invoke "vi"
>>
>>  "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset
>>
>> I am running windows 95 and have just install cygwin from www.cygwin.com
>> Do you have any idea what might be causing it?

-- 
Mark Himsley
In Acton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: DLL problem

[Anthony Gerkis]

Actually, I just starting subscribing to the list yesterday... when I
figured out that something might be wrong.

Anthony N. Gerkis
SOMA Networks, Inc.
312 Adelaide St. W, Suite 700
Toronto, Canada M5V 1R2
agerkis@somanetworks.com
(416) 348-1591

-----Original Message-----
From: ptsekov [ mailto:ptsekov]On Behalf Of Pavel Tsekov
Sent: Thursday, November 29, 2001 11:21 AM
To: Anthony Gerkis
Cc: Nicholas Down; cygwin@cygwin.com
Subject: Re: DLL problem


Maybe you should search the mailing list archive more
often when you encounter a problem.

Just a quick hint - there was at least one post a day
in the last week about your problem.

Anthony Gerkis wrote:
>
> I am also experiencing this problem. I had to move back vim 5.8.9 (still
can
> get off ftp servers) to make vim usage at all...
>
> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [ mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
> Sent: Thursday, November 29, 2001 10:23 AM
> To: cygwin@cygwin.com
> Subject: DLL problem
>
> Dear Cygwin,
>
>  I am getting the following message when trying to invoke "vi"
>
>  "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset
>
> I am running windows 95 and have just install cygwin from www.cygwin.com
> Do you have any idea what might be causing it?


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: DLL problem

[Pavel Tsekov]

Maybe you should search the mailing list archive more
often when you encounter a problem.

Just a quick hint - there was at least one post a day
in the last week about your problem.

Anthony Gerkis wrote:
> 
> I am also experiencing this problem. I had to move back vim 5.8.9 (still can
> get off ftp servers) to make vim usage at all...
> 
> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [ mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
> Sent: Thursday, November 29, 2001 10:23 AM
> To: cygwin@cygwin.com
> Subject: DLL problem
> 
> Dear Cygwin,
> 
>  I am getting the following message when trying to invoke "vi"
> 
>  "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset
> 
> I am running windows 95 and have just install cygwin from www.cygwin.com
> Do you have any idea what might be causing it?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: DLL problem

[Anthony Gerkis]

I am also experiencing this problem. I had to move back vim 5.8.9 (still can
get off ftp servers) to make vim usage at all...

Anthony N. Gerkis
SOMA Networks, Inc.
312 Adelaide St. W, Suite 700
Toronto, Canada M5V 1R2
agerkis@somanetworks.com
(416) 348-1591

-----Original Message-----
From: cygwin-owner@sources.redhat.com
[ mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
Sent: Thursday, November 29, 2001 10:23 AM
To: cygwin@cygwin.com
Subject: DLL problem


Dear Cygwin,

 I am getting the following message when trying to invoke "vi"

 "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset

I am running windows 95 and have just install cygwin from www.cygwin.com
Do you have any idea what might be causing it?

Many Thanks,

Nick Down
UK SSO TS-CPS
UK Commercial Software Specialist
IBM Global Services. (Geomar)
Tel: (01926) 462587 Email: DOWNNI@UK.IBM.COM



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

DLL problem

[Nicholas Down]

Dear Cygwin,

 I am getting the following message when trying to invoke "vi"

 "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset

I am running windows 95 and have just install cygwin from www.cygwin.com
Do you have any idea what might be causing it?

Many Thanks,

Nick Down
UK SSO TS-CPS
UK Commercial Software Specialist
IBM Global Services. (Geomar)
Tel: (01926) 462587 Email: DOWNNI@UK.IBM.COM



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: DLL problem

[Charles Wilson]

Morris, Steve wrote:

>  > Maybe you should search the mailing list archive more
>  > often when you encounter a problem.
>  > 
>  > Just a quick hint - there was at least one post a day
>  > in the last week about your problem.
> 
> This kind of post to the list is a total waste of bandwidth. Reply in
> private if you can't merely find the delete key. This educates the offender
> without wasting everyone elses time. Otherwise if you are not willing to
> help just shut up. This is a prevalent problem on this list. There are as
> many people posting simple RTFM responses as there are people who are
> unwilling to RTFM. They are equally abusive of this list.

No.  RTFM responses (and STFW and STFMLA) SHOULD go on the list.  The 
problem is, you only need ONE.  There's no need to pile on.  If the 
obvious answer to a question is RTFM, and someone has already posted 
that, there's no need for you to do so.  The only time there should be 
multiple RTFM responses to the same person's question is when duplicate 
responses "cross in the mail".

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: DLL problem

[Morris, Steve]

 > Maybe you should search the mailing list archive more
 > often when you encounter a problem.
 > 
 > Just a quick hint - there was at least one post a day
 > in the last week about your problem.

This kind of post to the list is a total waste of bandwidth. Reply in
private if you can't merely find the delete key. This educates the offender
without wasting everyone elses time. Otherwise if you are not willing to
help just shut up. This is a prevalent problem on this list. There are as
many people posting simple RTFM responses as there are people who are
unwilling to RTFM. They are equally abusive of this list.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: DLL problem

[Mark Himsley]

On Thu, 29 Nov 2001 11:24:30 -0500 you wrote:

>Actually, I just starting subscribing to the list yesterday... when I
>figured out that something might be wrong.

Does that stop you from searching the mailing lists at
http://cygwin.com/ml/cygwin/ ?


>Anthony N. Gerkis
>SOMA Networks, Inc.
>312 Adelaide St. W, Suite 700
>Toronto, Canada M5V 1R2
>agerkis@somanetworks.com
>(416) 348-1591
>
>-----Original Message-----
>From: ptsekov [mailto:ptsekov]On Behalf Of Pavel Tsekov
>Sent: Thursday, November 29, 2001 11:21 AM
>To: Anthony Gerkis
>Cc: Nicholas Down; cygwin@cygwin.com
>Subject: Re: DLL problem
>
>
>Maybe you should search the mailing list archive more
>often when you encounter a problem.
>
>Just a quick hint - there was at least one post a day
>in the last week about your problem.
>
>Anthony Gerkis wrote:
>>
>> I am also experiencing this problem. I had to move back vim 5.8.9 (still
>can
>> get off ftp servers) to make vim usage at all...
>>
>> -----Original Message-----
>> From: cygwin-owner@sources.redhat.com
>> [mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
>> Sent: Thursday, November 29, 2001 10:23 AM
>> To: cygwin@cygwin.com
>> Subject: DLL problem
>>
>> Dear Cygwin,
>>
>>  I am getting the following message when trying to invoke "vi"
>>
>>  "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset
>>
>> I am running windows 95 and have just install cygwin from www.cygwin.com
>> Do you have any idea what might be causing it?

-- 
Mark Himsley
In Acton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: DLL problem

[Anthony Gerkis]

Actually, I just starting subscribing to the list yesterday... when I
figured out that something might be wrong.

Anthony N. Gerkis
SOMA Networks, Inc.
312 Adelaide St. W, Suite 700
Toronto, Canada M5V 1R2
agerkis@somanetworks.com
(416) 348-1591

-----Original Message-----
From: ptsekov [mailto:ptsekov]On Behalf Of Pavel Tsekov
Sent: Thursday, November 29, 2001 11:21 AM
To: Anthony Gerkis
Cc: Nicholas Down; cygwin@cygwin.com
Subject: Re: DLL problem


Maybe you should search the mailing list archive more
often when you encounter a problem.

Just a quick hint - there was at least one post a day
in the last week about your problem.

Anthony Gerkis wrote:
>
> I am also experiencing this problem. I had to move back vim 5.8.9 (still
can
> get off ftp servers) to make vim usage at all...
>
> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
> Sent: Thursday, November 29, 2001 10:23 AM
> To: cygwin@cygwin.com
> Subject: DLL problem
>
> Dear Cygwin,
>
>  I am getting the following message when trying to invoke "vi"
>
>  "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset
>
> I am running windows 95 and have just install cygwin from www.cygwin.com
> Do you have any idea what might be causing it?


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: DLL problem

[Pavel Tsekov]

Maybe you should search the mailing list archive more
often when you encounter a problem.

Just a quick hint - there was at least one post a day
in the last week about your problem.

Anthony Gerkis wrote:
> 
> I am also experiencing this problem. I had to move back vim 5.8.9 (still can
> get off ftp servers) to make vim usage at all...
> 
> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
> Sent: Thursday, November 29, 2001 10:23 AM
> To: cygwin@cygwin.com
> Subject: DLL problem
> 
> Dear Cygwin,
> 
>  I am getting the following message when trying to invoke "vi"
> 
>  "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset
> 
> I am running windows 95 and have just install cygwin from www.cygwin.com
> Do you have any idea what might be causing it?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: DLL problem

[Anthony Gerkis]

I am also experiencing this problem. I had to move back vim 5.8.9 (still can
get off ftp servers) to make vim usage at all...

Anthony N. Gerkis
SOMA Networks, Inc.
312 Adelaide St. W, Suite 700
Toronto, Canada M5V 1R2
agerkis@somanetworks.com
(416) 348-1591

-----Original Message-----
From: cygwin-owner@sources.redhat.com
[mailto:cygwin-owner@sources.redhat.com]On Behalf Of Nicholas Down
Sent: Thursday, November 29, 2001 10:23 AM
To: cygwin@cygwin.com
Subject: DLL problem


Dear Cygwin,

 I am getting the following message when trying to invoke "vi"

 "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset

I am running windows 95 and have just install cygwin from www.cygwin.com
Do you have any idea what might be causing it?

Many Thanks,

Nick Down
UK SSO TS-CPS
UK Commercial Software Specialist
IBM Global Services. (Geomar)
Tel: (01926) 462587 Email: DOWNNI@UK.IBM.COM



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

DLL problem

[Nicholas Down]

Dear Cygwin,

 I am getting the following message when trying to invoke "vi"

 "VIM.EXE Linked to missing export CYGINTL.DLL:bind_textdomain_codeset

I am running windows 95 and have just install cygwin from www.cygwin.com
Do you have any idea what might be causing it?

Many Thanks,

Nick Down
UK SSO TS-CPS
UK Commercial Software Specialist
IBM Global Services. (Geomar)
Tel: (01926) 462587 Email: DOWNNI@UK.IBM.COM



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: dll problem

[Larry Hall (RFK Partners, Inc)]

At 05:10 AM 2/14/2001, Fennec Keeprog wrote:
>Hello list, I'm trying to "port" a program from linux to 
>windows, using gtk. I've got a dll problem: when i launch 
>the programm from cygwin it load "well" but when i want to 
>debug it using gdb it tells me:
>  LDR: Dll gnu-intl.dll base 10 000 000 relocated due to 
>collision with c:\progra~1\cygwin\usr\src\jpilot\gdk-
>1.3.dll 
>
>it print this dialog box several times with different dlls. 
>Is'nt dll allocates themselves ? where can i find docs ? 
>thanks 



Ignore these messages.  They are not indications of problems.  The best
place to start for information on Cygwin is www.cygwin.com.  The best place
to get information on GNU tools is through man/info or the web site of the 
specific tool in question.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

dll problem

[Fennec Keeprog]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

Hello list, I'm trying to "port" a program from linux to
windows, using gtk. I've got a dll problem: when i launch
the programm from cygwin it load "well" but when i want to
debug it using gdb it tells me:
 LDR: Dll gnu-intl.dll base 10 000 000 relocated due to
collision with c:\progra~1\cygwin\usr\src\jpilot\gdk-
1.3.dll

it print this dialog box several times with different dlls.
Is'nt dll allocates themselves ? where can i find docs ?
thanks

_________________________________________________________
Le journal des abonnés Caramail - http://www.carazine.com

DLL problem

[Thieß-Magnus Wolter]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 7589 bytes --]

Hi,

I recently installed Cygwin and tried to port a library,
which was compiled with gcc and g++, to a Windows dll.

I followed the steps described under 'Building and Using
DLLs' and used this script to generate the DLL:

cd driver
make -f driver.mak libdrv.a >& ../make_driver.log
cp libdrv.a ..
cd ../fransch
make -f fransch.mak >& ../make_fransch.log
cp libfransch.a ..
cd ..

gcc -c fs_driver_lib.c -Idriver -o fs_driver_lib.o

gcc -s -Wl,--base-file,fs_driver_lib.base -o fs_driver_lib.dll
fs_driver_lib.o -Wl,-e,_DllMain@12 -Wl,-e,_FS_Driver_run -Wl,libdrv.a
-Wl,libFransch.a -Wl,libstdc++.a
dlltool --base-file fs_driver_lib.base --def fs_driver_lib.def
--output-exp fs_driver_lib.exp --dllname fs_driver_lib.dll
gcc -s -Wl,--base-file,fs_driver_lib.base,fs_driver_lib.exp -o
fs_driver_lib.dll fs_driver_lib.o -Wl,-e,_DllMain@12
-Wl,-e,_FS_Driver_run -Wl,libdrv.a -Wl,libFransch.a -Wl,libstdc++.a
dlltool --base-file fs_driver_lib.base --def fs_driver_lib.def
--output-exp fs_driver_lib.exp
gcc -Wl,fs_driver_lib.exp -o fs_driver_lib.dll fs_driver_lib.o
-Wl,-e,_DllMain@12 -Wl,-e,_FS_Driver_run -Wl,libdrv.a -Wl,libFransch.a
-Wl,libstdc++.a

Compilation and linking works without warnings.
The corresponding fs_driver_lib.lib is generated
as follows:

lib  /machine:ix86 /DEF:fs_driver_lib.def

and used in a VC++ 6.0 project to be linked against an other
DLL (FS_Driver), which in turn is called from Simulink.
DLL loading works fine, but when actually calling the exported
function, a segmentation violation is detected (see below).

It seems to be related to file I/O and print statements, but I can't
say for sure.

I've looked all over the FAQ and tried a lot of compiler and linker
switches, but without avail.

Has anybody an idea?

Does the commercial version cover such kind of support?


Best regards,

  Thiess



------------------------------------------------------------------------
       Segmentation violation detected at Wed Apr 12 19:56:01 2000
------------------------------------------------------------------------

Configuration:
  MATLAB Version:   5.3.1.29215a (R11.1)
  Operating System: Microsoft Windows 98
  Window System:    Version 4.10 (Build 2222:  A )

Register State:
  EAX = 00000000  EBX = 610625bc
  ECX = 61062380  EDX = 00000000
  ESI = 61064944  EDI = 01b37108
  EBP = 01b36c20  ESP = 01b36c14
  EIP = bff7b9a6  FLG = 00000246

Stack Trace:
  [0] KERNEL32.DLL:bff7b9a6(0x61062380, 0x610625bc, 0, 0x01b37108)
  [1] CYGWIN1.DLL:6105aa0d(0x61062380, 1024, 0x610625bc, 0x01b37020)
  [2] CYGWIN1.DLL:6105ebaa(0x610625bc, 0x08551040, 0x01b36f58,
0x6105851b)
  [3] CYGWIN1.DLL:6105b3b7(0x610625bc, 0x08551040, 0x01b37020,
0x01b37108)
  [4] CYGWIN1.DLL:6105851b(0x61062380, 0x610625bc, 0x08551040,
0x01b36f94)
  [5] CYGWIN1.DLL:6105845c(0x610625bc, 0x08551040, 0x01b36f94,
0x06d8d0f8)
  [6] CYGWIN1.DLL:61053f31(0x08551040, 0, 0x81708050, 0x8170800c)
  [7] FS_DRIVER_LIB.DLL:08551068(0x01b370e4, 0x83c46f74, 0, 0)
  [8] FS_DRIVER_LIB.DLL:08551259(0, 0x01b370e4, 0, 0)
  [9] FS_DRIVER.DLL:08512cc2(0x04e42fa8, 0, 0x06d8cf18, 0)
  [10] FS_DRIVER.DLL:085128e3(0xfffffffe, 0x04d6c270, 5, 0x06d8cf18)
  [11] MATLAB.EXE:_mexRunMexFile(0xffff127f, 0x04d6c270, 5, 0x06d8cf18)
+ 95 bytes
  [12] MATLAB.EXE:_psRunMexFile(0xfffffffe, 0x04d6c270, 5, 0x06d8cf18) +
458 bytes
  [13] MATLAB.EXE:_psCallMexFile(0xfffffffe, 0x04d6c270, 5, 0x06d8cf18)
+ 28 bytes
  [14] MATLAB.EXE:_psCallFunction(0xfffffffe, 0x04d6c270, 5, 0x06d8cf18)
+ 45 bytes
  [15] MATLAB.EXE:_psDoMatlabFcnCall(0xfffffffe, 0x04d6c270, 5,
0x06d8cf18) + 151 bytes
  [16] SIMULINK.DLL:_CMexSFcnOutputFcn(0x04d6bf38, 0x04cd34c0,
0x01b373ec, 0x007e5f77) + 571 bytes
  [17] SIMULINK.DLL:_ModelOutput(0x04d6bf38, 0x04d63710, 0x0467f8b0, 0)
+ 40 bytes
  [18] SIMULINK.DLL:_SFcnOutputFcn(0x04cd34c0, 0x06da586c, 0x0467f8b0,
0x04e150b4) + 247 bytes
  [19] SIMULINK.DLL:_BlockOutput(0x06da586c, 0x0467f8b0, 0x04d63710, 0)
+ 683 bytes
  [20] SIMULINK.DLL:_ExecSTaskOutputList(0x04d63710, 0x04dcd0a0,
0x04e150b4, 0) + 259 bytes
  [21] SIMULINK.DLL:_BdSystemOutput(0x0467f8b0, 0x02804278, 0x04dcd0a0,
0x0467f8b0) + 124 bytes
  [22] SIMULINK.DLL:_BdOutputFcn(0x04d63710, 0, 0x01b374d8, 0x00849af4)
+ 35 bytes
  [23] SIMULINK.DLL:_ModelOutput(0x04d63710, 0x04d63710, 0x0467f8b0, 0)
+ 40 bytes
  [24] SIMULINK.DLL:_slDoOutputAndUpdate(0, 0x026f8c28, 0x04d63710, 0) +
244 bytes
  [25] SIMULINK.DLL:_SimulateModel(1, 0x026f8c28, 0x01b3757c,
0x00a1df08) + 128 bytes
  [26] SIMULINK.DLL:_Simulate(0x01b3758c, 0x01b37588, 0, 3) + 497 bytes
  [27] SIMULINK.DLL:_sleCommandLineSimulation(0, 0x01b375d4, 3,
0x01b3789c) + 133 bytes
  [28] SIMULINK.DLL:_slFullSimulate(0, 0x01b375d4, 3, 0x01b3789c) + 26
bytes
  [29] MATLAB.EXE:_psStackOp(1, 3, 0, 0x01b39570) + 1194 bytes
  [30] MATLAB.EXE:_psInterPcode(1, 0x06d466b8, 2, 0) + 2180 bytes
  [31] MATLAB.EXE:_psInterPcode(1, 0, 0x026de848, 0) + 4441 bytes
  [32] MATLAB.EXE:_psWordsj(0, 0x01b39880, 0, 0x01b39b4c) + 1171 bytes
  [33] MATLAB.EXE:_psCallMFile(0, 0x01b39880, 0, 0x01b39b4c) + 170 bytes
  [34] MATLAB.EXE:_psCallFunction(0, 0x01b39880, 0, 0x01b39b4c) + 45
bytes
  [35] MATLAB.EXE:_psFullFevalFcn(0, 0x01b39880, 1, 0x01b39b48) + 201
bytes
  [36] MATLAB.EXE:_psStackOp(103, 1, 0, 0) + 1194 bytes
  [37] MATLAB.EXE:_psInterPcode(1, 0, 0x026dfcf8, 0) + 2426 bytes
  [38] MATLAB.EXE:_psWordsj(0, 0x01b3adec, 0, 0x01b3b0f8) + 1171 bytes
  [39] MATLAB.EXE:_psExecMFile(0, 0, 0x01b3b0f8, 0x026dfcf8) + 189 bytes
  [40] MATLAB.EXE:_psExecFunction(0, 0, 0x01b3b0f8, 0x026dfcf8) + 41
bytes
  [41] MATLAB.EXE:_psMMexExecute(685, 0, 0, 0x01b3cd18) + 611 bytes
  [42] MATLAB.EXE:_psInterPcode(1, 0, 2, 3) + 1678 bytes
  [43] MATLAB.EXE:_psInterPcode(1, 1, 0x026d95d8, 0) + 4441 bytes
  [44] MATLAB.EXE:_psWordsj(0, 0x01b3d028, 1, 0x01b3d2f4) + 1171 bytes
  [45] MATLAB.EXE:_psCallMFile(0, 0x01b3d028, 1, 0x01b3d2f4) + 170 bytes
  [46] MATLAB.EXE:_psCallFunction(0, 0x01b3d028, 1, 0x01b3d2f4) + 45
bytes
  [47] MATLAB.EXE:_psFullFevalFcn(0, 0x01b3d028, 2, 0x01b3d2f0) + 201
bytes
  [48] MATLAB.EXE:_psStackOp(103, 2, 0, 2) + 1194 bytes
  [49] MATLAB.EXE:_psInterPcode(0, 0x04d8c79a, 0, 0x02584a00) + 2426
bytes
  [50] MATLAB.EXE:_psEvalString(0x04d8c780, 25, 0, 0) + 537 bytes
  [51] MATLAB.EXE:_psEvalExpInWS(0x04d8c780, 0, 0, 0x01b3e3f8) + 94
bytes
  [52] HG.DLL:_goCallEventCallback(0, 0, 0x0074d7bc, 0x006fbcc0) + 321
bytes
  [53] HG.DLL:_goCallCallback(0x026e95a8, 0x04ad40e8, 0x0074d7bc,
0x006fbcc0) + 66 bytes
  [54] HG.DLL:_goControlActivated(0x026e95a8, 4056, 0x04ad4148,
0x01b3e6d0) + 80 bytes
  [55] UIW.DLL:_activate_control(4056, 0x04ad4148, 0x01b3e4e0, 34128) +
137 bytes
  [56] UIW.DLL:_PushButtonProc@16(4056, 0, 0, 4056) + 127 bytes
  [57] KERNEL32.DLL:bff7363b(0x66c78550, 26311, 0, 0xbff719b8)
  [58] KERNEL32.DLL:bff94407(0x84e66038, 0xbff7186d, 0x852a500f, 0)


Segmentation violation occurred within signal handler.
Unable to complete stack trace (stack was probably corrupted)

This error was detected while a MEX-file was running.  If the MEX-file
is not an official MathWorks function, please examine its source code
for errors.  Please consult the MATLAB API Guide for information on
debugging MEX-files.

-- 
-------------------------------------------------------------
Dipl.-Ing. Thieß-Magnus Wolter          Tel: +49 89 747377 33
TESIS DYNAware GmbH                     Fax: +49 89 747377 99
Implerstraße 26
D-81371 München, Germany                    t.wolter@tesis.de
-------------------------------------------------------------


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

dll problem

[Edward Maros]

When I try the demo program to create a non-relocatable dll, I get the
following warning message:

ld: warming: cannot find entry symbol _mainCRTStartup; defaulting to
00401000

When I run main, I get a message box with the following error:
The C:\HOME\EMAROS\DLLS\FOO.DLL file
can't load at the desired address, and is not relacatable.
Contact your vendor to get a version taht is compatible with this
version of Windows.

and at the command prompt:
bash.exe: ./main: (null)

When trying to run the relocatable version, I get:
bash.exe: ./main: (null)

with a prompt box of:

Unable to run c:\home\emaros\rdll\main.exe

I used: building-dlls.txt and building-reloc-dlls.txt from the cygnus
home page. I am using gnu-win32-b18.

Thanks,
Ed
------
Edward Maros				emaros@ligo.caltech.ed

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: DLL Problem

[Fergus Henderson]

Roland Geier wrote:
> [someone wrote:]
> > I'm trying to port a tcl module from unix to win95 as a dll to load within
> > wish.
...
> > ext+0x15):libcmain.cc: undefined reference to `GetCommandLineA@0'
> > c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
> >
> > ext+0x1e):libcmain.cc: undefined reference to `WinMain@16'
> >
> > This seems to be a reentrancy problem, since a simple call like :
> > fprintf(stderr, ...)
> 
> ...for me this seems to be a forgotten '-lkernel32' at link-time :). The
> undefined ref to 'WinMain' can be avoided with:
> 
>         echo 'int main() { return 0; }' > fixup.c;
>         echo 'asm (".section .idata$3\n" ".long 0,0,0,0,0,0,0,0");' >> fixup.c;
>         gcc -c fixup.c
>         # link fixup.o with your dll...

Defining main() will supress the link error, but it will not actually
fix the problem.  The startup file (crt0.o, I think) containing a
definition of `_impure_ptr' will be linked in, but _impure_ptr will
not be initialized.  This means that any reference to global variables
such as `stdout' or `stderr' from within your DLL will be broken, and
so your DLL will probably crash.

To avoid the problem, you need to initialize your DLL's _impure_ptr
from the main program.  See < http://www.cs.mu.oz.au/~fjh/gnu-win32 >
for an example of how to do this.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >   |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: DLL Problem

[Roland Geier]

> I'm trying to port a tcl module from unix to win95 as a dll to load within
> wish.
>
> So i tried to began with the example provided on cygnus.com , it works
> fine, i got my foo.dll, main.exe, but moving to my real software when I run
> ld I got:
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libccrt0.o)(.t
>
> ext+0x8a):libccrt0.cc: undefined reference to `GetModuleHandleA@4'
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
>
> ext+0xc):libcmain.cc: undefined reference to `GetModuleHandleA@4'
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
>
> ext+0x15):libcmain.cc: undefined reference to `GetCommandLineA@0'
> c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t
>
> ext+0x1e):libcmain.cc: undefined reference to `WinMain@16'
>
> This seems to be a reentrancy problem, since a simple call like :
> fprintf(stderr, ...)

...for me this seems to be a forgotten '-lkernel32' at link-time :). The
undefined ref to 'WinMain' can be avoided with:

        echo 'int main() { return 0; }' > fixup.c;
        echo 'asm (".section .idata$3\n" ".long 0,0,0,0,0,0,0,0");' >> fixup.c;
        gcc -c fixup.c
        # link fixup.o with your dll...

hth,

--- Roland.

---
Roland Geier                    Phone: ++49 (8505) 92182          
Universitaet Passau, GER 	Fax:   ++49 (8505) 922311
Lehrstuhl Prof. Dr. Donner      geier@forwiss.uni-passau.de	
D-94032 Passau                  http://www.uni-passau.de/~geier/





-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: DLL Problem

[Fergus Henderson]

"Stephane Mariel" <stf@hugo.int-evry.fr> writes:

>I'm trying to port a tcl module from unix to win95 as a dll to load within
>wish. 
>
>ext+0x1e):libcmain.cc: undefined reference to `WinMain@16'
>
>This seems to be a reentrancy problem, since a simple call like :
>fprintf(stderr, ...) 
>makes use of _impure_ptr which is a struct _reent* ptr that is provided by
>any process using the dll. So , probably the exact question is : how to say
>to ld: this symbol must not be search in libc, (libccrto.o, libcmain.o) but
>must be mapped to a symbol defined in the calling process?

With beta-18, you need to define _impure_ptr in your DLL.
See < http://www.cs.mu.oz.au/~fjh/gnu-win32/how-to-build-dlls.html >.

An extract:

# The DLL may also contain some references to _impure_ptr
# (e.g. stdin is defined as a macro which expands to _impure_ptr.stdin).
# We need to provide a definition for this (otherwise it will link in
# the definition in libccrt.o, which causes lots of problems,
# eventually leading to undefined symbol `WinMain').
# The main program needs to initialize all the _impure_ptr variables
# for the DLLs with its _impure_ptr.

--
Fergus Henderson <fjh@cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >   |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

DLL Problem

[Stephane Mariel]

[this is a repost, the first one should be lost, hope you will not recieve
it twice]

Hi,

I'm trying to port a tcl module from unix to win95 as a dll to load within
wish. 

So i tried to began with the example provided on cygnus.com , it works
fine, i got my foo.dll, main.exe, but moving to my real software when I run
ld I got:
c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libccrt0.o)(.t

ext+0x8a):libccrt0.cc: undefined reference to `GetModuleHandleA@4'
c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t

ext+0xc):libcmain.cc: undefined reference to `GetModuleHandleA@4'
c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t

ext+0x15):libcmain.cc: undefined reference to `GetCommandLineA@0'
c:/gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/lib/libcygwin.a(libcmain.o)(.t

ext+0x1e):libcmain.cc: undefined reference to `WinMain@16'

This seems to be a reentrancy problem, since a simple call like :
fprintf(stderr, ...) 
makes use of _impure_ptr which is a struct _reent* ptr that is provided by
any process using the dll. So , probably the exact question is : how to say
to ld: this symbol must not be search in libc, (libccrto.o, libcmain.o) but
must be mapped to a symbol defined in the calling process?

Any idea?

Thanks,

stf

 


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".