#8951: rustc will apparently be needed for firefox-53.
-------------------------+-----------------------
 Reporter:  ken@…        |       Owner:  ken@…
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  8.1
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------

Comment (by ken@…):

 The debian patches are, at least partially, applied in 1.16. Long story
 short - if I install rustc and one lib (librustc_driver-*.so : initially
 ldd said that was not found), and run ldconfig, ldd shows that lib is now
 found and all the others are missing (I renamed the DESTDIR to be
 absolutely certain).

 I ran the tests after that - the jemalloc test appears to not be run, but
 I now get 104 failures from all of the gdb tests (because gdb is not
 present).
 I suppose that means gdb is needed for the testsuite.

 This was using rustbuild, but with configure and using *static* llvm
 (because rust loves static libs, and things might break in future versions
 of either rust or LLVM).  For that, I needed a sed from fedora to ensure
 -lffi is picked up when system LLVM (built against libffi) is used: there
 have been alternative fixes, apparently they no longer work (the shipped
 LLVM is not built against libffi). :
 {{{
 sed -i -e '$a #[link(name = "ffi")] extern {}' src/librustc_llvm/lib.rs
 }}}

 and then
 {{{
 ./configure --prefix=/usr --llvm-root=/usr
 ./x.py build
 DESTDIR=/some/path ./x.py dist --install
 ./x.py test
 }}}

 The tests can be run after the build, but I was more concerned about the
 DESTDIR.

 Without the tests, build tree was 1.6G, install 264M. The tests added 0.3G
 to the build tree.

 This was cleaner than previously: I ran each command | tee somelog : the
 output on the term showed which file was being built, no need to force
 verbosity. It takes all the cores, of course.  When I did get an error
 (one was local, second  eventually led me to the sed) the output did
 eventually show the error - 'eventually' because the first time it took
 about 3 minutes waiting for other jobs to stop, with 1 core at 100%, and
 then it stopped and reported the detail.

 No idea how much of it used cmake - I suspect that only really gets used
 if building the shipped LLVM. That will be my next step, along with trying
 to stop it installing for other architectures, and using a versioned
 docdir.




 The docs are in /usr/share/doc/rust (unversioned).

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/8951#comment:7>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to