[HECnet] building simh

[Gregg Levine]

On Sun, Apr 8, 2012 at 7:05 PM, Dave McGuire <mcguire at neurotica.com> wrote:

  I was thinking this was pretty odd, so I looked at the source
distribution for simh v3.8-1.   It seems the makefile is hard-coded to
look for libpcap.a in /usr/local/lib.

  Bad idea.

  Edit the makefile and fix the path to libpcap.a.   That's on line 18 in
the standard v3.8-1 sources.

               -Dave

On 04/08/2012 03:48 PM, hvlems at zonnet.nl wrote:
Dave,
The system has libpcap-devel-1.0.0.5 installed
Fedora is RH's free linux distribution.
It uses Yum as install manager.
-----Original Message-----
From: Dave McGuire <mcguire at neurotica.com>
Sender: owner-hecnet at Update.UU.SE
Date: Sun, 08 Apr 2012 15:40:32
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] building simh

On 04/08/2012 05:26 AM, hvlems at zonnet.nl wrote:
Well, this isn't a linux forum but perhaps one of you solved this problem.
I have an Asus Eee PC 900, and it Tnow) has Fedora 14 installed.
It runs the bridge program and I want to run simh on this box since it is cheap on mains power. Its battery is shot which is why my ex gave it to me.
I have libpcap installed and used 'make USE_NETWORK'=1' to build simh.
Which fails because it cannot locate
/usr/local/llib/libpcap.a
There is a libpcap.so, in /usr/lib
Am I running an old version of linux, or made an error installing libcap?

   Hi!   It sounds to me like you've got the runtime support for libpcap
installed, but not the "development" support.

   For libraries, .so files (so == Shared Object) are used at runtime,
while .a (Archive) files are used at compile time. (well, more
specifically at link time).   The former are dynamically-linked shared
libraries, whereas the latter are non-shared libraries for static linking.

   These days, compilation support is rarely included by default on Linux
OS or package distributions to save space.   One must explicitly install
the "dev" version of the library, which typically gets you .a files for
static linking, as well as the header (.h) files.

   I've never seen Fedora 14, so I don't know exactly how its package
repository system works, but you'll need to find and install whatever
package corresponds to "libpcap-dev" or something very similarly named.
  This should get you going.

                    -Dave



--
Dave McGuire, AK4HZ
New Kensington, PA

Hello!
First of all, there's been discussion on the SIMH list regarding
updates to the code, and one individual other then Bob himself has
undertaken the task of the herculean efforts to create what will
become the next big release. I'm not sure how old the Fedora release
is that you are using Hans, but for me I do know that Slackware-13.37
who always includes everything even kernel source code, is about two
years old and is approaching three. Search the list for SIMH for the
methods of obtaining a code drop from the authors Git repository. It
includes code in the make file to use the normal locations of where
libcap.a lives.

And here's the amusing part, what release of the GNU tools is your
Fedora release using? I know that mine is too new for the release of
SIMH we are discussing because the linker complains.

Ideally before going that route, I suggest looking through SIMH
postings for a newer release then the one that's on the site.

And Dave, welcome to the region.

-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."