> Umm, installed in /root instead of /usr/bin ?
No, I was logged in as root and was using tab completion to find out the
various rust programs.
> I think that so far everyone has had 1.22.1 installed when trying to
> build 1.25.0. In theory, using the previous versions of rust and
> cargo
On Sun, Apr 15, 2018 at 05:18:10PM -0500, Bruce Dubbs wrote:
> On 04/15/2018 05:15 PM, Ken Moffat wrote:
> > On Sat, Apr 14, 2018 at 01:24:46PM -0400, Alain Toussaint wrote:
> > >
> > > root [ ~ ]# rust
> > > rustc rustdocrust-gdb rust-lldb
> >
> > Umm, installed in /root instead of
On Sun, Apr 15, 2018 at 12:49:38PM -0400, Alain Toussaint wrote:
>
> > -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG
> > -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Failed
>
>
> I do get these failures but the configure & build steps went fine on the
> stock build
On 04/15/2018 05:15 PM, Ken Moffat wrote:
On Sat, Apr 14, 2018 at 01:24:46PM -0400, Alain Toussaint wrote:
I have a nearly ready made system done with llvm 6 and rust 1.22.1:
I came to answer this because I couldn't remember if your question
at the end had been answered. But ...
root [ ~
On Sat, Apr 14, 2018 at 01:24:46PM -0400, Alain Toussaint wrote:
>
> I have a nearly ready made system done with llvm 6 and rust 1.22.1:
>
I came to answer this because I couldn't remember if your question
at the end had been answered. But ...
> root [ ~ ]# llvm-config --version
> 6.0.0
> root
On Sun, Apr 15, 2018 at 09:07:15PM +0100, Ken Moffat wrote:
>
> And yesterday I tried building llvm in /tmp for speed (tmpfs, should
> be fast) - only to discover that for some reason the fstab I had
> started from (system was a binary copy from an older machine, fstab
> modified to point to the
On 04/15/2018 02:57 PM, Ken Moffat wrote:
On my system,:
llvm-config --libs all gives -lLLVM-6.0
llvm-config --libs gives -lLLVM-6.0
llvm-config --system-libs returns an empty line
Yes, I get the same.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ:
On 15/04/2018 21:57, Ken Moffat wrote:
> On Sun, Apr 15, 2018 at 01:01:54PM -0500, Bruce Dubbs wrote:
>> On 04/15/2018 11:14 AM, baldu...@units.it wrote:
>>>
>>> I saw the "undefined symbol: ffi_type_float" error quite a long ago with
>>> 1.17.0 and it was fixed by:
>>>
>>> export
On Sun, Apr 15, 2018 at 01:43:52PM -0500, Bruce Dubbs wrote:
> On 04/15/2018 01:16 PM, Ken Moffat wrote:
> > On Sun, Apr 15, 2018 at 11:27:22AM +0200, Pierre Labastie wrote:
> > >
> > > Done, and it built. Ken, don't you think the instructions should wipe out
> > > /sources/RUST after installing?
On Sun, Apr 15, 2018 at 01:01:54PM -0500, Bruce Dubbs wrote:
> On 04/15/2018 11:14 AM, baldu...@units.it wrote:
> >
> > I saw the "undefined symbol: ffi_type_float" error quite a long ago with
> > 1.17.0 and it was fixed by:
> >
> > export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi"
>
> Well
On 04/15/2018 01:16 PM, Ken Moffat wrote:
On Sun, Apr 15, 2018 at 11:27:22AM +0200, Pierre Labastie wrote:
Done, and it built. Ken, don't you think the instructions should wipe out
/sources/RUST after installing?
Pierre
We don't explicitly remove the build directories, AFAICS.
This is a
On Sun, Apr 15, 2018 at 11:27:22AM +0200, Pierre Labastie wrote:
>
> Done, and it built. Ken, don't you think the instructions should wipe out
> /sources/RUST after installing?
>
> Pierre
>
We don't explicitly remove the build directories, AFAICS.
This is a first (hopefully the only) DESTDIR
On 04/15/2018 11:14 AM, baldu...@units.it wrote:
hi,
There remains to understand why Bruce has an error with libffi. There is no
mention of libffi in my rust build log.
I routinely build rustc vs system llvm
I had no problems building rustc-1.25.0 vs llvm-6.0
I saw the "undefined symbol:
On Sun, Apr 15, 2018 at 07:01:10PM +0200, baldu...@units.it wrote:
>
> Tools will only be linked to the libLLVM shared library if
> LLVM_LINK_LLVM_DYLIB
> is also ON.
Thanks for that explanation.
ĸen
--
In my seventh decade astride this planet, and as my own cells degrade,
there are
On Sun, Apr 15, 2018 at 11:42:56AM -0500, Bruce Dubbs wrote:
>
> Well this is interesting. I tried to build llvm with:
>
> CC=gcc \
> CXX=g++ \
> cmake -DCMAKE_INSTALL_PREFIX=/usr \
>
On 04/15/2018 12:01 PM, baldu...@units.it wrote:
Well this is interesting. I tried to build llvm with:
[snip]
Here are my notes about the above problem, which I wrote for 4.0.0
(2017-04-29), but I guess still apply.
The essence is: do NOT switch *BOTH* LLVM_BUILD_LLVM_DYLIB and
> Well this is interesting. I tried to build llvm with:
>
> CC=gcc \
> CXX=g++ \
> cmake -DCMAKE_INSTALL_PREFIX=/usr \
>-DLLVM_ENABLE_FFI=ON \
>
> -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG
> -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Failed
I do get these failures but the configure & build steps went fine on the stock
build instruction:
CC=gcc CXX=g++ \
cmake
On 04/15/2018 02:25 AM, Pierre Labastie wrote:
On 14/04/2018 23:50, Ken Moffat wrote:
On Sat, Apr 14, 2018 at 10:26:22PM +0200, Pierre Labastie wrote:
I think there is a switch for building shared libraries in llvm. The book was
using it at a time, but there were problems with mesa IIRC.
hi,
> There remains to understand why Bruce has an error with libffi. There is no
> mention of libffi in my rust build log.
I routinely build rustc vs system llvm
I had no problems building rustc-1.25.0 vs llvm-6.0
I saw the "undefined symbol: ffi_type_float" error quite a long ago with
1.17.0
Le samedi 14 avril 2018 à 22:26 +0200, Pierre Labastie a écrit :
> On 14/04/2018 19:18, Pierre Labastie wrote:
> > On 14/04/2018 18:18, Bruce Dubbs wrote:
> > > On 04/13/2018 11:38 PM, Bruce Dubbs wrote:
> > > > Using the new instructions in the book O could not get rustc to build.
> > > > I was
On 15/04/2018 09:25, Pierre Labastie wrote:
> On 14/04/2018 23:50, Ken Moffat wrote:
>> On Sat, Apr 14, 2018 at 10:26:22PM +0200, Pierre Labastie wrote:
>>>
>
> Do we need to adjust the book's instructions?
>
I'd say not before understanding what is going on... Let me try
On 14/04/2018 23:50, Ken Moffat wrote:
> On Sat, Apr 14, 2018 at 10:26:22PM +0200, Pierre Labastie wrote:
>>
Do we need to adjust the book's instructions?
>>>
>>> I'd say not before understanding what is going on... Let me try building
>>> rust
>>> with the new instructions, after
On 04/14/2018 11:05 PM, Bruce Dubbs wrote:
On 04/14/2018 08:22 PM, Ken Moffat wrote:
On Sat, Apr 14, 2018 at 10:50:11PM +0100, Ken Moffat wrote:
On Sat, Apr 14, 2018 at 10:26:22PM +0200, Pierre Labastie wrote:
Given that one of the old issues I found suggested that the problem
only happened
On 04/14/2018 08:22 PM, Ken Moffat wrote:
On Sat, Apr 14, 2018 at 10:50:11PM +0100, Ken Moffat wrote:
On Sat, Apr 14, 2018 at 10:26:22PM +0200, Pierre Labastie wrote:
Given that one of the old issues I found suggested that the problem
only happened with static libs, and that libffi is being
On Sun, Apr 15, 2018 at 02:22:13AM +0100, Ken Moffat wrote:
>
> for the binaries, a lot of differences, mostly in size.
> Attached as bindiff
>
I knew I'd forget. Attached now.
--
In my seventh decade astride this planet, and as my own cells degrade,
there are some things I cannot do now:
On Sat, Apr 14, 2018 at 10:50:11PM +0100, Ken Moffat wrote:
> On Sat, Apr 14, 2018 at 10:26:22PM +0200, Pierre Labastie wrote:
> >
> > thread 'main' panicked at 'command did not execute successfully:
> > "/usr/bin/llvm-config" "--link-shared" "--libs" "--system-libs" "asmparser"
> > "bitreader"
On Sat, Apr 14, 2018 at 11:35:56AM -0500, Bruce Dubbs wrote:
> On 04/14/2018 11:20 AM, Ken Moffat wrote:
> > On Fri, Apr 13, 2018 at 11:38:26PM -0500, Bruce Dubbs wrote:
> >
> > There was a suggestion from several years ago that this used to
> > happen if _static_ llvm libs were used. Latest
On Sat, Apr 14, 2018 at 10:26:22PM +0200, Pierre Labastie wrote:
>
> >>
> >> Do we need to adjust the book's instructions?
> >>
> >
> > I'd say not before understanding what is going on... Let me try building
> > rust
> > with the new instructions, after installing llvm 6, and removing
> So: three persons; three different outcomes...
Most likely 4 differents outcome by tomorrow, I'll be getting a 2010 model Mac
Pro, with, I think, a
6 core nehalem as a minimum which will heat the place compiling software under
travis-ci (https://gi
thub.com/travis-ci/travis-ci ) or something
On 14/04/2018 19:18, Pierre Labastie wrote:
> On 14/04/2018 18:18, Bruce Dubbs wrote:
>> On 04/13/2018 11:38 PM, Bruce Dubbs wrote:
>>> Using the new instructions in the book O could not get rustc to build. I was
>>> getting:
>>>
>>> --- stderr
>>> error: couldn't load codegen backend
>>>
On 04/14/2018 12:24 PM, Alain Toussaint wrote:
Le samedi 14 avril 2018 à 19:18 +0200, Pierre Labastie a écrit :
On 14/04/2018 18:18, Bruce Dubbs wrote:
On 04/13/2018 11:38 PM, Bruce Dubbs wrote:
When I removed the line
llvm-config = "/usr/bin/llvm-config"
from config.toml, it seem to work
Le samedi 14 avril 2018 à 19:18 +0200, Pierre Labastie a écrit :
> On 14/04/2018 18:18, Bruce Dubbs wrote:
> > On 04/13/2018 11:38 PM, Bruce Dubbs wrote:
> > > Using the new instructions in the book O could not get rustc to build. I
> > > was
> > > getting:
> > >
> > > --- stderr
> > > error:
On 14/04/2018 18:18, Bruce Dubbs wrote:
> On 04/13/2018 11:38 PM, Bruce Dubbs wrote:
>> Using the new instructions in the book O could not get rustc to build. I was
>> getting:
>>
>> --- stderr
>> error: couldn't load codegen backend
>>
On Sat, Apr 14, 2018 at 11:18:06AM -0500, Bruce Dubbs wrote:
>
> The build completed and everything seems OK. I do not know why rustc does
> not like my version of clang.
>
> $ clang --version
> clang version 6.0.0 (tags/RELEASE_600/final)
> Target: x86_64-unknown-linux-gnu
> Thread model:
On 04/14/2018 11:20 AM, Ken Moffat wrote:
On Fri, Apr 13, 2018 at 11:38:26PM -0500, Bruce Dubbs wrote:
Using the new instructions in the book O could not get rustc to build. I was
getting:
--- stderr
error: couldn't load codegen backend
On Fri, Apr 13, 2018 at 11:38:26PM -0500, Bruce Dubbs wrote:
> Using the new instructions in the book O could not get rustc to build. I was
> getting:
>
> --- stderr
> error: couldn't load codegen backend
>
On 04/13/2018 11:38 PM, Bruce Dubbs wrote:
Using the new instructions in the book O could not get rustc to build. I
was getting:
--- stderr
error: couldn't load codegen backend
38 matches
Mail list logo
