On 04/15/2018 03:19 PM, Ken Moffat wrote:
This is what I now propose to do, to fix the build and to ensure
that the DESTDIR gets blown away when the user deletes the source:




This causes tools to be linked to the libLLVM shared library
and also ensures that llvm-config will correctly use libLLVM-6.0.so

(and add an entity for 6.0 because llvm-config reports that rather
than 6.0.0 and we don't want to refer to 6.0 when 7.0.0 arrives in
the book)

I'm OK with this, but I note that it didn't fix things for me.


before the build add

export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi"

Command explanation:

On some systems, linking fails to include libffi unless this is used.
The reasons are not clear.

Agreed.  This does fix things for me.

Change the DESTDIR install to create and use 'install' in the source
directory.  This removes the need to know what the absolute PATH is.

DESTDIR=${PWD}/install ./x.py install

The real install then becomes:

chown -R root:root install
cp -a install/* /

The reference to DESTDIR in the Estimated disk space can be removed.

This makes it a little less of a conventional DESTDIR so perhaps the
Note at the top should be reworded slightly to:

Unusually, a DESTDIR-style method ...
and change
Using a DESTDIR method saves 30 SBU
This saves 30 SBU

Agreed.  This does make the page cleaner.

  -- Bruce

FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to