Date: Mon, 17 Nov 2014 03:52:33 -0700 From: Warner Losh <imp@bsdimp.com> To: sbruno@freebsd.org Cc: freebsd-arch@freebsd.org Subject: Re: mips misbehaving, not respecting make.conf Message-ID: <C4633A81-3E37-4B58-91FB-59786992BA3B@bsdimp.com> In-Reply-To: <1416193104.1098.1207.camel@bruno> References: <1416179733.1098.1200.camel@bruno> <2A2AD781-06B3-4450-9631-D83822016D0B@bsdimp.com> <1416183055.1098.1205.camel@bruno> <7C1D8D61-0486-4783-A3E2-73189AE83023@bsdimp.com> <1416193104.1098.1207.camel@bruno>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Nov 16, 2014, at 7:58 PM, Sean Bruno <sbruno@ignoranthack.me> wrote: > On Sun, 2014-11-16 at 17:15 -0700, Warner Losh wrote: >> On Nov 16, 2014, at 5:10 PM, Sean Bruno <sbruno@ignoranthack.me> wrote: >> >>> On Sun, 2014-11-16 at 16:55 -0700, Warner Losh wrote: >>>> On Nov 16, 2014, at 4:15 PM, Sean Bruno <sbruno@ignoranthack.me> wrote: >>>> >>>>> I have set make.conf to use AS=/nxb-bin/usr/bin/as and >>>>> CC=/nxb-bin/usr/bin/cc >>>>> >>>>> Yet, while monitoring, I still see the ports build process >>>>> using /usr/bin/as and /usr/bin/ld and /usr/libexec/cc1 >>>>> >>>>> I don't see this on armv6 when building in a jail + qemu. >>>>> >>>>> I'm trying to understand what is missing from our gcc toolchain here >>>>> that is causing the builds to ignore my directives. >>>> >>>> Let’s start with the first question: How are you seeing this? >>>> >>>> Warner >>>> >>> >>> >>> Setup a qemu-user enabled jail for mips based on head. Start poudriere >>> building audio/speex (nice, short depend chain). >>> >>> While all this is running, I have a "ps auwxxx|grep qemu" running that >>> catches some of the invocations of qemu that are happening. When >>> running a mips jail I see the tool chain being invoked, partially, >>> from /usr/bin instead of /nxb-bin/usr/bin. >>> >>> http://dpaste.com/12SD5TE >>> >>> This is just a primitive profile attempt on my part. This shows that >>> qemu is being invoked *a lot* to get cc1 and as running via emulation. >> >> If you are building ports, chances are those settings won’t do what you think they will. Do you have build logs I could look at? >> >> Warner > > > More verbose output, not super useful. Except that the configure output > shows that /nxb-bin/usr/bin/cc wants to use /usr/bin/ld ... I think this > means we're not setting up the build flags for gcc correctly? > > http://crack.ysv.freebsd.org/data/11-mips-test-default/2014-11-17_02h37m39s/logs/speex-1.2.r1_7,1.log Perhaps. But when I wrote those targets, I assumed they’d replace the target-native binaries with host-native binaries, now that I think about it, rather than live in a side directory. You’d need to make CC be something more like CC=$PATH/usr/bin/cc -B$PATH/lib/exec or some such. Is there a good reason to not replace the binaries? I noticed you keeping them separate, but wasn’t sure if that was just a “well, that’s what the target does” thing or a “I had to do it because X” thing. Warner [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUadNxAAoJEGwc0Sh9sBEA9a4P/iEdibt8dPpNkEW/YTxsiApj g8dx25DC7PEy7hZsFN3TCYHsi6cXrS/su8G4DW3/wCB1o4TBPiNYCwbem2R+610J mazJVGZ4vG6P9R21GhmlaJyH0ih95HLOnZuLErDWQ1MYXRQzzfalWejSm2duswFN 7HB2aJGrQ5mNSRhyveyxkC75Y4387o63HQHHDjIriFISxJFDpektL/wzMcOd01Ds anUakexFQfdzyUDKRN4mOhFqFYjK1eQ/+TvGnSRVLgAFJf9jBxED6SZcQo8TA1OV O7wtdtDe3KnPa06McMo7iCZ8AYLXDMmT2d+7e2CtLxDTR4qck7+iYQuLflwqNXhK YwamsBwlmq7uKfLk7FPeviYuba01+AmRzgoDVTeWE0WvAlyDc3fmKYh3aCKHs6sC l6SDMYbD8FXTSQnURvWkXGSxheFu1W9YT2dNqMWKtxYky87/OT0OrS6koYTwuqE1 ChSNf9Qo6owvXI5u5kWrZ2E0icQfsAxdFoxNAmyEgJcX+5W2rgBGe9940Z0Q/18f 3LEMl8xKicMXJn4wSlA3KUh7hTkTJKUI7TyK0nlhpuwPIPmRkrVy1onno29T7P4B 3AiTdnG0B8wjXczvvdfruN2Jqhc65Lylz4bLjFjqRB9ih+DgvkDLbq6IANdwXLF+ bdZ94/VPc11YnNd2jW/N =iNcH -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C4633A81-3E37-4B58-91FB-59786992BA3B>