[HECnet] building simh

Dave McGuire mcguire at neurotica.com
Tue Apr 10 19:17:36 PDT 2012


On 04/10/2012 02:12 PM, H Vlems wrote:
Is it possible to explain what the magic does?
More precisely: what is the difference between an .a and an .so library?

  I detailed this a few posts ago.   .a is a static library, .so is a
shared library.

How on earth does -lpcap point to /usr/lib?

  -lpcap tells the linker to look in every directory in the library
search path to find either libpcap.a or libpcap.so.

  This library lives in /usr/lib on most systems, but the simh makefile
hard-coding that path (and hard-coding it to only find the static
library) is a big mistake.

                    -Dave


If the answers are too lengthy or are too complex for an old Algol
programmer then say so ;-)

Hans 

-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Oleg Safiullin
Verzonden: maandag, april 2012 8:04
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] building simh

On 04/09/2012 12:33 PM, hvlems at zonnet.nl wrote:
Dave,
I figured that out too. My system doesn't have a libpcap.a file! If I know
how to build one then all would be fine.

To build SimH manually wothout libpcap.a (but with libpcap.so.*) you should
edit `makefile' and replace line

NETWORK_OPT = -DUSE_NETWORK -isystem /usr/local/include
/usr/local/lib/libpcap.a

with

NETWORK_OPT = -DUSE_NETWORK -isystem /usr/local/include -lpcap

and then do

mkdir BIN
make USE_NETWORK=yes



-- 
Dave McGuire, AK4HZ
New Kensington, PA



More information about the Hecnet-list mailing list