Compiling against bsdsocket in C

[copse]

I'm writing a socket server in C using vbcc (in WinUAE) and it doesn't link against the static libraries from AmiTCP. If I add the -vv option, I see the following:

vlink -bamigahunk -t -x -Bstatic -Cvbcc -nostdlib -mrel vlibos3:startup.o "T:t_3_0.o" -Lnetlib -lnet -s -Rshort -Lvlibos3: -lvc -o a.out

Loading files:

vlibos3:startup.o (amigahunk object)
T:t_3_0.o (amigahunk object)
netlib/net.lib (amigahunk library)
Fatal error 13: netlib/net.lib: File format corrupted.
Aborting.

I have checked that the CRC of the file in the lha locally in 7zip is the same as the one on Aminet by browsing the archive contents online there.

There are two possible outcomes I suspect I am looking for:

1. Someone points out the obvious thing I am doing wrong.
2. I saw inline assembly in some of the C headers for bsdsocket calls. Perhaps someone knows how to use these and bypass the library calls?

Files used:

1. https://aminet.net/package/dev/c/vbcc_bin_amigaos68k
2. https://aminet.net/package/comm/tcp/AmiTCP-SDK-4.3

[thomas]

I cannot help you with AmiTCP. But it is ancient. Try Roadshow SDK instead.

And what do you need static libs for? I never even bothered. But I am not a power user, I only ever wrote simple http clients.

[copse]

I've not programmed in non-assembly on the Amiga before. What is the alternative to static libs? Inline header asm stubs?

[thomas]

You are using vbcc. Just #include <proto/bsdsocket.h> and you are done. No need to link against any net lib.

[copse]

Originally Posted by thomas

You are using vbcc. Just #include <proto/bsdsocket.h> and you are done. No need to link against any net lib.

Thanks. This fails due to a missing file 'clib/bsdsocket_protos.h' which is clearly another problem with the AmiTCP SDK. I'll get rid of it and replace it with Roadshow which you've kindly pointed me in the direction of.

[Hedeon]

I think the posixlib for vbcc also has bsdsocket stuff?

[copse]

That's a good tip Hedeon but it's unclear how useful this is. It refers to only opening bsdsocket.library when needed, but the perhaps unstated goal here is that the whole point is that bsdsocket.library is used. This is because WinUAE provides it and it allows a form of external communication.

[phx]

The network stuff is confusing with AmigaOS. Main problem here is: although AmiTCP and Roadshow both name their shared library

bsdsocket.library

the header files in their SDK are named differently. It is either

<proto/socket.h>

(from vbcc) and

<clib/socket_protos.h

(from AmiTCP SDK) or

<proto/bsdsocket.h>

(from vbcc) and

<clib/bsdsocket_protos.h>

(from Roadshow SDK).

So in this case (AmiTCP) including

<proto/socket.h>

might have helped.

As Thomas indicated, linking with any static libraries from the AmiTCP SDK is rarely required, if you include the proto header, because that automatically includes the inline-calls from

<inline/socket_protos.h>

.

The reason for the "corrupted file format" error is unclear. I couldn't reproduce it. But maybe the vlink used is just too old. The libraries in the AmiTCP-SDK are in SAS/C

HUNK_LIB

format, which vlink only supports since V15.

Also note that you have to be careful with the Include path from the AmiTCP-SDK. It overwrites compiler-specific standard headers like

stdio.h

and

errno.h

, which you must avoid. Solution for vbcc is to force reading from the standard include path before the AmiTCP-SDK include path. For example:

-Ivincludeos3: -IAmiTCP/netinclude

As far as I remember this situation improved with Roadshow.

[copse]

Thanks, it sounds like upgrading to the non-aminet version of vbcc/vlink is the way to go. I do have the amitcp headers last though, so that problem was avoided from the get go fortunately.

[bebbo]

Originally Posted by phx

The network stuff is confusing with AmigaOS. Main problem here is: although AmiTCP and Roadshow both name their shared library

bsdsocket.library

the header files in their SDK are named differently. It is either

<proto/socket.h>

(from vbcc) and

<clib/socket_protos.h

(from AmiTCP SDK) or

<proto/bsdsocket.h>

(from vbcc) and

<clib/bsdsocket_protos.h>

(from Roadshow SDK). So in this case (AmiTCP) including

<proto/socket.h>

might have helped.
...

proto/socket.h is also present in RoadShow and is the way to go.

[patrik]

Originally Posted by phx

As far as I remember this situation improved with Roadshow.

Yes and the Roadshow SDK works great even if you end up using AmiTCP or Miami as it is the same bsdsocket.library API. I only use the Roadshow SDK since a long time. I only use the proto files and do not link against any library.