#10240: rustc-1.23.0-src
-------------------------+-----------------------
Reporter: ken@… | Owner: ken@…
Type: enhancement | Status: assigned
Priority: normal | Milestone: 8.2
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+-----------------------
Comment (by ken@…):
Replying to [comment:4 bdubbs@…]:
> Rust builds it's own version of llvm. Interestingly, it is current:
5.0.1.
>
> That is one of the reasons rust takes so long to build. llvm in the
book is 22 SBU and rust is 33 SBU. If they used system llvm, it would be
a LOT faster.
>
The two problems in the past were:
1. Using system llvm, ISTR that tests failed excessively (but that was in
the days before it reliably ran its full set of tests).
2. A version of rust which uses the current version of LLVM will always
lag the introduction of the new LLVM to BLFS.
> I'll note that I do have:
>
> /tmp/rustc/rustc-1.23.0-src/build/x86_64-unknown-linux-gnu/llvm/bin
/llvm-config
>
> but I generally do not do a DESTDIR install other than to look at files.
In the case of rust, it seems to ignore the exported DESTDIR variable.
>
I often use DESTDIR installs when looking at a new build. But I always do
them manually, and specify the DESTDIR in the install command. But I now
think that although rustc-1.23.0 had ended its build normally, something
was missed. i.e. the reported completion at the end is inaccurate. I say
that because I've just managed a successful user build and DESTDIR, but
the build took a LOT longer than the previous abortive attempt.
Will run tests to check how much .cargo increases (if at all), then will
give another try to getting root to do a DESTDIR.
My current feeling is that the build system is very flakey.
> I note that I have:
>
> $ du -sh .cargo
> 547M .cargo
>
Thanks, but I'd like to accurately blame rust / firefox / librsvg for
cargo files!
> Tell me again why upstream has gone to rustc/cargo?
o Because they like to make things harder for people who build from
source
o Because they think everybody on supported platforms ought to use
their binary builds
o Because they think rust will prevent a class of errors
o Because they want to ensure everybody uses the exact same versions of
the cargo files, so that build-failures in the future cannot be worked
around with current versions of the package
[ pick as many answers as you wish ]
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/10240#comment:5>
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
