From owner-freebsd-current Mon Mar 27 21:01:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA24577 for current-outgoing; Mon, 27 Mar 1995 21:01:56 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA24568 for ; Mon, 27 Mar 1995 21:01:50 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id WAA04596; Mon, 27 Mar 1995 22:05:59 -0700 Date: Mon, 27 Mar 1995 22:05:59 -0700 Message-Id: <199503280505.WAA04596@trout.sri.MT.net> To: brian@mediacity.com (Brian Litzinger) Cc: freebsd-current@FreeBSD.org Subject: Re: hylafax doesn't with work with shared libraries In-Reply-To: References: Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@FreeBSD.org Precedence: bulk Brian Litzinger writes: > I compiled hylafax beta 111 (flexfax) with -current (032695) and the faxstat > command reports something like invalid response 'ld.so ....' from > server. That generally happens when one of the programs is compiled with the wrong load flags. This happened in the early days of the shared libs when we changed our default a.out format, but it shouldn't do anything now. Are you sure there isn't some special ld flags that were added? Try doing a file on the resulting executables to see if they show up as FreeBSD executables. Nate