From owner-freebsd-emulation Mon May 21 15:20:40 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25]) by hub.freebsd.org (Postfix) with ESMTP id DB19637B422 for ; Mon, 21 May 2001 15:20:36 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from delta.rc.ny.us (nyf-ny3-45.ix.netcom.com [198.211.16.173]) by barry.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA03155; Mon, 21 May 2001 18:20:34 -0400 (EDT) Received: (from vsilyaev@localhost) by delta.rc.ny.us (8.11.1/8.9.3) id f4LMKTJ00493; Mon, 21 May 2001 18:20:29 -0400 (EDT) (envelope-from vsilyaev) Date: Mon, 21 May 2001 18:20:29 -0400 From: Vladimir Silyaev To: "Hartmann, O." Cc: freebsd-emulation@freebsd.org Subject: Re: Fortran problems/Linux emu problems Message-ID: <20010521182029.A427@delta.rc.ny.us> References: <20010518213535.A306@delta.rc.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ohartman@klima.physik.uni-mainz.de on Sat, May 19, 2001 at 04:12:32PM +0200 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 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? 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). 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? > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message