Honestly, unless you want the Debian layout, it looks like the CLFS guys have some movement again. Martin just posted a huge update and William is working through them now.
On January 23, 2017 11:26:10 AM CST, DJ Lucas <[email protected]> wrote: >That should do it, however, the environment isn't setup at that point. >Need to set path for the temp tools, and set +h. > >On January 21, 2017 9:15:46 AM CST, Roger Koehler ><[email protected]> wrote: >>On Wed, Jan 18, 2017 at 6:31 AM, Pierre Labastie >><[email protected]> wrote: >>> On 18/01/2017 02:05, Roger Koehler wrote: >>>> >>>> On Tue, Jan 17, 2017 at 5:39 PM, DJ Lucas <[email protected]> >>wrote: >>>>> >>>>> On 01/16/2017 08:05 PM, Roger Koehler wrote: >>>>>> >>>>>> On Sat, Jan 14, 2017 at 11:43 PM, Roger Koehler >>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> On Sat, Jan 14, 2017 at 11:31 PM, Roger Koehler >>>>>>> <[email protected]> wrote: >>>>>>>> >>>>>>>> On Sat, Jan 14, 2017 at 11:07 PM, Roger Koehler >>>>>>>> <[email protected]> wrote: >>>>>>>>> >>>>>>>>> On Sat, Jan 14, 2017 at 10:50 PM, Roger Koehler >>>>>>>>> <[email protected]> wrote: >>>>>>>>>> >>>>>>>>>> On Sat, Jan 14, 2017 at 9:44 PM, DJ Lucas >><[email protected]> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> So far, I have not been successful building ANY version of >>CLFS >>>>>>>>>>>> >>>>>>>>>>>> What is a known good way to build CLFS x86_64 (multilib) >>from an >>>>>>>>>>>> amd64 host? >>>>>>>>>>>> >>>>>>>>>>> You can do it after regular LFS, but that doesn't fix the >>CLFS book >>>>>>>>>>> or its interaction with jhalfs. >>>>>>>>>>> >>>>>>>>>>> I just updated from local sources (without testing): >>>>>>>>>>> >>>>>>>>>>> >>http://www.linuxfromscratch.org/~dj/lfs-multilib-20170115.diff >>>>>>>>>>> >>>>>>>>>>> As long as you are not opposed to /lib and /usr/lib with >>/usr/lib32 >>>>>>>>>>> for >>>>>>>>>>> 32bit libs (Debian style). Also, with ISL and gold but >ld.bfd >>>>>>>>>>> default, this >>>>>>>>>>> should work (though I haven't tested it in a while). >>>>>>>>>>> >>>>>>>>>>> --DJ >>>>>>>>>> >>>>>>>> So, I figured out the patch command: >>>>>>>> >>>>>>>> cd to my LFS SVN directory and then: >>>>>>>> >>>>>>>> patch -s -p0 < ../lfs-multilib-20170115.diff >>>>>>>> >>>>>> For some reason, the commands starting with 139-binutils-temp are >>>>>> missing the unpack functions. >>>>>> >>>>> Yes, I'm not sure I tested it with jhalfs yet, completely spaced >on >>that. >>>>> Do the unpack functions work with packages after 139 and 140? >>>> >>>> Yes. Missing for 139, 140, and 141, and again for all of the lib32 >>>> lfs-commands. >> >>So, I manually updated the Makefile to include the unpack functions on >>these steps, and it ran up to 141-glibctemp. I then tried following >>the book manually at 6.74. Glibc-2.24 32-bit (temp), but I get the >>same error during the configuration step: >> >>checking build system type... x86_64-unknown-linux-gnu >>checking host system type... i686-pc-linux-gnu >>checking for i686-pc-linux-gnu-gcc... x86_64-unknown-linux-gnu-gcc >-m32 >>checking for suffix of object files... configure: error: in >>`/mnt/lfs/sources/glibc-2.24/build': >>configure: error: cannot compute suffix of object files: cannot >compile >>See `config.log' for more details >> >>From config.log: >> >>configure:2189: checking build system type >>configure:2203: result: x86_64-unknown-linux-gnu >>configure:2223: checking host system type >>configure:2236: result: i686-pc-linux-gnu >>configure:2265: checking for i686-pc-linux-gnu-gcc >>configure:2292: result: x86_64-unknown-linux-gnu-gcc -m32 >>configure:2561: checking for C compiler version >>configure:2570: x86_64-unknown-linux-gnu-gcc -m32 --version >&5 >>../configure: line 2572: x86_64-unknown-linux-gnu-gcc: command not >>found >> >>../configure: (lines 2560 - 2583) >> >># Provide some information about the compiler. >>$as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler >version" >>>&5 >>set X $ac_compile >>ac_compiler=$2 >>for ac_option in --version -v -V -qversion; do >> { { ac_try="$ac_compiler $ac_option >&5" >>case "(($ac_try" in >> *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; >> *) ac_try_echo=$ac_try;; >>esac >>eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" >>$as_echo "$ac_try_echo"; } >&5 >>############## The following line is line 2572 ############### >> (eval "$ac_compiler $ac_option >&5") 2>conftest.err >>############################################### >> ac_status=$? >> if test -s conftest.err; then >> sed '10a\ >>... rest of stderr output deleted ... >> 10q' conftest.err >conftest.er1 >> cat conftest.er1 >&5 >> fi >> rm -f conftest.er1 conftest.err >> $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 >> test $ac_status = 0; } >>done >> >>Any ideas? >>-- >>http://lists.linuxfromscratch.org/listinfo/alfs-discuss >>FAQ: http://www.linuxfromscratch.org/faq/ >>Unsubscribe: See the above information page > >-- >Sent from my Android device with K-9 Mail. Please excuse my brevity. > >-- >http://lists.linuxfromscratch.org/listinfo/alfs-discuss >FAQ: http://www.linuxfromscratch.org/faq/ >Unsubscribe: See the above information page -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
