Frédéric ORMANCEY wrote:
> Thanks for this sample code => we are not far of the solution !
>
> Same sample compile on my platform gives the following :
> V:>gnatmake imp
> gnatbind -x imp.ali
> gnatlink imp.ali
> ./imp.o(.text+0x20):imp.adb: undefined reference to `_FormatMessage
Thanks for this sample code => we are not far of the solution !
Same sample compile on my platform gives the following :
V:>gnatmake imp
gnatbind -x imp.ali
gnatlink imp.ali
./imp.o(.text+0x20):imp.adb: undefined reference to `_FormatMessageA'
collect2: ld returned 1 exit st
> -Original Message-
> From: cygwin-owner On Behalf Of Cliff Hones
> Sent: 22 September 2004 23:38
> That was me - but it seems Dave Korn's post broke the thread.
Nah. My post had this header:
In-Reply-To: <[EMAIL PROTECTED]>
and as you can see perfectly clearly at
http://www.cygw
Larry Hall wrote:
> At 01:14 PM 9/22/2004, you wrote:
>
>>>-Original Message-
>>>From: Frédéric ORMANCEY
>>>Sent: 22 September 2004 18:07
>>
>>>I did it, but it don't work !
>>
>> Ah, ok, that was not clear from your last message!
>>
>>
>>>The --enable-stdcall-fixup option suppress one war
At 01:14 PM 9/22/2004, you wrote:
>> -Original Message-
>> From: Frédéric ORMANCEY
>> Sent: 22 September 2004 18:07
>
>> I did it, but it don't work !
>
> Ah, ok, that was not clear from your last message!
>
>> The --enable-stdcall-fixup option suppress one warning on top
>> of linker ou
> -Original Message-
> From: Frédéric ORMANCEY
> Sent: 22 September 2004 18:07
> I did it, but it don't work !
Ah, ok, that was not clear from your last message!
> The --enable-stdcall-fixup option suppress one warning on top
> of linker output trace :
> AVERTISSEMENT: résolution
I did it, but it don't work !
The --enable-stdcall-fixup option suppress one warning on top of linker
output trace :
AVERTISSEMENT: résolution de _GetModuleHandleA par un lien vers
[EMAIL PROTECTED]
and unfortunatly leave ALL other errors with no effect on it.
Dave Korn a écrit :
-Origina
> -Original Message-
> From: cygwin-owner On Behalf Of Frédéric ORMANCEY
> Sent: 22 September 2004 13:31
> problem seems coming from trailing @nn in library symbols.
> cygwin linker don't know how to translate a reference like
> _FormatMessageA to [EMAIL PROTECTED]
> the calling conventio
problem seems coming from trailing @nn in library symbols.
cygwin linker don't know how to translate a reference like
_FormatMessageA to [EMAIL PROTECTED]
the calling convention ( C, Stdcall, C++, ... ) has effect only on
underscore preceeding symbol name, not on @nn notation.
It seems there is
Larry Hall wrote:
> At 12:15 PM 9/21/2004, you wrote:
>
>>I think you're right, it seems to be a problem with trailing underscore in function
>>naming.
>>For example :
>>
>>in /usr/lib/w32api/libkernel32.a we found :
>>
>> T [EMAIL PROTECTED]
>> U __head_libkernel32_a
At 12:15 PM 9/21/2004, you wrote:
>I think you're right, it seems to be a problem with trailing underscore in function
>naming.
>For example :
>
>in /usr/lib/w32api/libkernel32.a we found :
>
> T [EMAIL PROTECTED]
>U __head_libkernel32_a
> I [EMAIL PROTECT
I think you're right, it seems to be a problem with trailing underscore
in function naming.
For example :
in /usr/lib/w32api/libkernel32.a we found :
T [EMAIL PROTECTED]
U __head_libkernel32_a
I [EMAIL PROTECTED]
which is required by win32-winbase.o, re
At 05:38 AM 9/21/2004, you wrote:
> Using latest release of CygWin ( 1.5.11-1 ) I install the devel kit,
>
>including gcc and gnat compilers. Then I build from src GCC and GNAT release 3.4.1 (
>which include necessary patchs for my application ).
>All my Ada application compile well with gnatmake
13 matches
Mail list logo
