From owner-freebsd-mips@freebsd.org Fri Feb 5 15:34:58 2016 Return-Path: Delivered-To: freebsd-mips@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B29E0A77640 for ; Fri, 5 Feb 2016 15:34:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E3A31FB1 for ; Fri, 5 Feb 2016 15:34:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk0-x229.google.com with SMTP id o6so35319732qkc.2 for ; Fri, 05 Feb 2016 07:34:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Qi9dXRFSDragMpUSHG5TC166aXNeFjUAamYeHOYIVRY=; b=cvAXEGkB5sOe1Pf+XaQ2GCbFn99CCbaBfMi8B6n7ADCMTZh4DNyuVfS/oiZTmeAWSq fvGxH2ShWw5CMeVQQGVK6iKyfGSOIYKUPKRsyj9ry9330lzI1xLbpGfG+EPSW82qHwTt ojMDnHZugp2LGMs516k4n+ksQxuas0LLPchlPPYcKdXaWj60LMAaVg8IssrUN+p7QVTq CQQ86oEHEJ8YLm1VYUCMQZ/i4RDKf42Jw0p9f+b7e84fFjWNe3lLmm6xfEq81ECcNeiu 9xtTarz4zPCYEqWnxHEWKqU5IX7HqD1feKGB9HYXD5KiG8enEoVzLreaS/peFvC1jIAK Yu5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Qi9dXRFSDragMpUSHG5TC166aXNeFjUAamYeHOYIVRY=; b=e0bVFxIR37eGnj/nHtV0phsq1D2JksPTsX6oHsRspdxObu1HOdKdM0vl7RsNrmgKdE ItIRxY2CkaOzwbsTl2XYUGbqAsQGAVlG12Vi4qI9lF2GpyWr1dTfw7YDebYrFpIwvtEp qwTirQSGEN0tDxVbJJhUIO15JibA/eaQUrAqrqfTC2pkHF8RxzfCck8YSw/DrH1gA7gp IcI8EarPbd3kFboYJrSwaqLLiLOdo//oIj8MMrCslFIYbTyHm47jm1PjK7/DR/eutUAL gxZZ8QxoiiLhzHmNS6U+mqMe4xYg5FZ4mU/mHolGQY8KPGkq/1iaSYlgspScNM05joFi afdw== X-Gm-Message-State: AG10YOSJ29SpRQWhE/gC9e/yhP1iUeAUC5aQRFiXGpWvYRrZ1jL2yKf3hVpfA8K9dmxduq79rE8aSHwP99mCDw== MIME-Version: 1.0 X-Received: by 10.55.192.7 with SMTP id o7mr17026221qki.93.1454686497451; Fri, 05 Feb 2016 07:34:57 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.30.166 with HTTP; Fri, 5 Feb 2016 07:34:57 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <20160205143335.GC93874@anubis.morrow.me.uk> References: <20160205143335.GC93874@anubis.morrow.me.uk> Date: Fri, 5 Feb 2016 08:34:57 -0700 X-Google-Sender-Auth: 8CIllLyVpfYBTkvs1FmkrvqoQM4 Message-ID: Subject: Re: Re: mips/qemu jails with native-xtools From: Warner Losh To: Ben Morrow Cc: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 15:34:58 -0000 On Fri, Feb 5, 2016 at 7:33 AM, Ben Morrow wrote: > [Sorry, I sent this to Warner privately by mistake.] > > Warner Losh wrote: > > On Thu, Feb 4, 2016 at 5:26 PM, Ben Morrow wrote: > > > > > I've finally got a mips/qemu poudriere jail working properly with a > > > native toolchain, but it took a bit of fiddling to make it work, so I > > > thought I'd report on what I did. > [...] > > > Having put the proper libraries back, the next problem was that ld was > > > failing to find shared libraries that were implicitly linked > (DT_NEEDED) > > > by other shared libraries. The specific port I was building was > > > net/tshark, which links glib, which implicitly pulls in libpcre and > > > libiconv. The configure step was failing because ld couldn't find > > > libpcre.so.3. > > > > > > It turns out that ld finds the path to search for DT_NEEDED libraries > by > > > reading ld-elf.so.hints. That file (in the jail) is BE, because this is > > > a mips world with a mips ldconfig, but the ld binary is LE, so it can't > > > read the file. With the patch below, it can; since endianness is the > > > only difference between architectures, I think it should be safe for > > > general use, but I don't really know > > > > I'd think it would be better to generate the ld.so in the proper binary > > format. How hard is that? > > ld.so has to be a mips binary, otherwise we can't run any other > (non-static) mips binaries. So ld.so.hints has to be in BE format, > otherwise ld.so can't read it. The problem is that ld and ld.so have > different endiannesses, and ld is assuming it can read ld.so's files to > find the search path. > > Of course, it would always be possible to simply use a mips binary for > ld, as well, and just let it be emulated. > I guess I'm misunderstanding something. When / how is ld have a different endianness? Is it the amd64 ld that produces binaries for big-endian mips that introduces the cross-threading? Warner