My Gnat is rusty - link error

My Gnat is rusty - link error

[Thomas Kerstan]

I have GNAT 3.12 on a windows 95 machine. (the machine also
has GNAT 3.01a but I believe that should be irrelevant)

I am able to generate executables for the samples that are
included in the win32ada/samples directory but when I try
to compile/bind/link (using gnatmake) some code that uses
the win32.winsock binding for sockets the compile and bind
complete without errors, but the gnatlink gives
undefined reference to 'WSAStartup@8'
undefined reference to ... 
messages for all of the winsock routines.

any help would be appreciated,
thanks,

Tom
kerstan@home.com

Re: My Gnat is rusty - link error

[Marin David Condic]

I believe you have to specify either a linker option or put the following
pragma into your code somewhere:

    pragma Linker_Options ("-lwsock32") ;

Putting it in the code will make it harder to forget. :-)

Hope this helps.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Thomas Kerstan" <kerstan@home.com> wrote in message
news:3B8571D0.64268D43@home.com...
> I have GNAT 3.12 on a windows 95 machine. (the machine also
> has GNAT 3.01a but I believe that should be irrelevant)
>
> I am able to generate executables for the samples that are
> included in the win32ada/samples directory but when I try
> to compile/bind/link (using gnatmake) some code that uses
> the win32.winsock binding for sockets the compile and bind
> complete without errors, but the gnatlink gives
> undefined reference to 'WSAStartup@8'
> undefined reference to ...
> messages for all of the winsock routines.
>
> any help would be appreciated,
> thanks,
>
> Tom
> kerstan@home.com

Re: My Gnat is rusty - link error

[Thomas Kerstan]

Marin David Condic wrote:
> 
> I believe you have to specify either a linker option or put the following
> pragma into your code somewhere:
> 
>     pragma Linker_Options ("-lwsock32") ;
> 
> Putting it in the code will make it harder to forget. :-)
> 
> Hope this helps.
> 
> MDC
> --

That did the trick,
thanks,

Tom
kerstan@home.com

Re: My Gnat is rusty - link error

[Simon Wright]

"Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org> writes:

> I believe you have to specify either a linker option or put the following
> pragma into your code somewhere:
> 
>     pragma Linker_Options ("-lwsock32") ;
> 
> Putting it in the code will make it harder to forget. :-)

Of course, it also binds your code to Windows .. umm, perhaps that
won't matter until 3.14p comes out? (with GNAT.Sockets)

Re: My Gnat is rusty - link error

[Marin David Condic]

I don't think so - not any worse than using WinSock is going to bind you to
Windows anyway. Remember that a pragma that isn't recognized by another
implementation is just going to get ignored anyway - so hopefully it would
just get dropped on the floor.

My advice would be to code up a package to do all of the usual sockets jobs,
only at an Ada level of abstraction - hiding in the implementation beneath
any of the WinSock specifics. The pragma should be isolated in this part of
the code as well. From there, if you have to switch to a different flavor of
sockets, at least its all in one isolated place with a minimal level of
fuss.

Using GNAT.Sockets might be a wonderful thing - except that now your code is
GNAT dependent. This may not be bad depending on your project. Many projects
are committed to a specific compiler. However, I think a *cleaner* idea
would be for there to be some sort of Sockets support in a generalized Ada
package (descending from Ada-dot-something?) that was reasonably standard
across all implementations. Its technically doable - just a political
question. Do the vendors want to standardize this and if so at what level?
But this raises the whole "Standard Ada Library" question again.....

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Simon Wright" <simon@pushface.org> wrote in message
news:x7vheuwk4d1.fsf@smaug.pushface.org...
> "Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org> writes:
>
> > I believe you have to specify either a linker option or put the
following
> > pragma into your code somewhere:
> >
> >     pragma Linker_Options ("-lwsock32") ;
> >
> > Putting it in the code will make it harder to forget. :-)
>
> Of course, it also binds your code to Windows .. umm, perhaps that
> won't matter until 3.14p comes out? (with GNAT.Sockets)

Re: My Gnat is rusty - link error

[David C. Hoos]

----- Original Message -----
From: "Marin David Condic ]" <dont.bother.mcondic.auntie.spam@[acm.org>
Newsgroups: comp.lang.ada
To: <comp.lang.ada@ada.eu.org>
Sent: Monday, August 27, 2001 9:04 AM
Subject: Re: My Gnat is rusty - link error


> I don't think so - not any worse than using WinSock is going to bind you
to
> Windows anyway. Remember that a pragma that isn't recognized by another
> implementation is just going to get ignored anyway - so hopefully it would
> just get dropped on the floor.
>
The pragma Linker_Options will be recognized by all compilers,
and the liker will complain when it cant find the library file.

Re: My Gnat is rusty - link error

[tmoran]

>Using GNAT.Sockets might be a wonderful thing - except that now your code is
>GNAT dependent. This may not be bad depending on your project. Many projects
>are committed to a specific compiler. However, I think a *cleaner* idea
>would be for there to be some sort of Sockets support in a generalized Ada
>package (descending from Ada-dot-something?) that was reasonably standard
>across all implementations. Its technically doable - just a political
>question. Do the vendors want to standardize this and if so at what level?
>But this raises the whole "Standard Ada Library" question again.....
  I'd modestly offer the Claw.Sockets interface (see www.rrsoftware.com).
It works on multiple compilers targetted to Windows, and the actual
Windows dependencies are inside the implementation, mostly concerning
asynchronous stuff that uses the Windows message loop.  An example very
simple web server (ca 400 lines) using it is on www.adapower.com