From owner-freebsd-emulation Tue May 22 0:22: 1 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id 8C78837B50B for ; Tue, 22 May 2001 00:21:52 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.Physik.Uni-Mainz.DE (Sturm@klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.11.3/8.11.3) with ESMTP id f4M7LnT03985; Tue, 22 May 2001 09:21:49 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Tue, 22 May 2001 09:21:49 +0200 (CEST) From: "Hartmann, O." To: Vladimir Silyaev Cc: Subject: Re: Fortran problems/Linux emu problems In-Reply-To: <20010521182029.A427@delta.rc.ny.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 21 May 2001, Vladimir Silyaev wrote: :> :>As far as I understood you, you have a problem with binaries builded :>under FreeBSD by Linux fortran compiler. The same source code builded :>in the native linux environment looks ok, right? That is correct. :> :>If so I see only one possible problem (besides wrong installation :>of fortran) - that during compilation fortran used some part :>of FreeBSD system (i.e. libraries, or even linker, C-compiler). That was my first idea and it seems that way, but the same installation (which hasn't been changed) worked before. :> :>If you think that it was working before you may use ktrace/linux_kdump :>or strace to see what differences before and after upgrade. :> :>Regards, :>Vladimir :> :>P.S. You may want see how binaries builded on FreeBSD works under native :>Linux and what's ldd saying there. :>P.S.S. Did you aware about brandelf utility? I'm surely aware of brandelf, but that doesn't matter. A couriosity is, that on one machine, the NFS server, after restarting mountd, the problem disappeared on the NFS server. I can now compile my software normaly. But not on the other systems, the clients of the NFS server. It looks weird ...' :> :>> Well, I did the 'doublecheck' so far, without success. :>> I tried to 'chroot' myself into /compat/linux and encapsulate :>> all actions by starting a Linux shell by exec-ing a :>> /compat/linux/bin/sh, without success. :>> :>> But why should I do that when I know that all systems run all :>> right before? :>> :>> Using ldd within this encapsulated environment gives me an error :>> like this: :>> :>> root: /bin: ldd dd :>> /usr/bin/ldd: /lib/ld-linux.so.2: cannot execute binary file :>> ldd: /lib/ld-linux.so.2 exited with unknown exit code (126) :>> :>> This is the Linux dd. :>> :>> All programs are compiled against Linux ones, I presume. :>> It is curois to me that some systems are not working properly since :>> we did the last update. :>> :>You should doublecheck that your linux executabled are linked against :>> :>Linux libraries, not FreeBSD ones. You may check that by using ldd from the :>> :>linux devtools. :>> :> :>> :>Another thing what you may try to do, it's to compile from environment :>> :>'chrooted' into the /compat/linux. :>> :> :>> :>-- :>> :>Regards, :>> :>Vladimir :>> :> :>> :> :> :>-- :>Vladimir :> :> -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institut fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message