From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,434e685e89e79374,start
X-Google-Attributes: gid103376,public
From: bklungle@ix.netcom.com(Robert Klungle )
Subject: gnat3.01/elf/linux problem
Date: 1996/05/14
Message-ID: <4na697$cci@dfw-ixnews10.ix.netcom.com>#1/1
X-Deja-AN: 154775382
organization: Netcom
x-netcom-date: Tue May 14  9:44:55 AM CDT 1996
newsgroups: comp.lang.ada
Date: 1996-05-14T09:44:55-05:00
List-Id: <comp.lang.ada>


A couple of weeks ago, I and two others posted a note documenting an
execution failure with gnat3.01. The symptom is a message saying "can't
resolve symbol '__libc_opendir'". The program compiles and links
perfectly. It appears that for some reason, either libgnat.so.3.01 (the
dynamic link library) is not being linked into the executable
correctly, or the referenced component is missing. Someone else said
they had the problem, but reloaded libc.a and reran ldconfig to get rid
of the problem. I have reloaded gnat3.01 and gcc2.7.2 and rerun
ldconfig in every order I can think of and nothing fixes the problem.
Tried deleting gnat and gcc from the system and rebuilding in case an
old link was not being rebuilt, to no avail.
Sent a message to the gnat group but no answer or suggestion yet.

Anybody got any idea what to try next (maybe reformat the drive and
rebuild the system from scratch)??

Incidentally, the gcc2.7.2 works perfectly and detects the 2.7.2-specs.

tks...bob klungle