lkml.org 
[lkml]   [2018]   [May]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: crosstool requirements?
From
Date
On 05/05/2018 07:35 PM, Arnd Bergmann wrote:
> On Sat, May 5, 2018 at 2:20 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> Hi Arnd,
>>
>> I was trying to use the x86_64 hosted openrisc/or1k gcc compiler (7.3.0-nolibc)
>> but I mostly what I get are errors like the following:
>>
>> crosstool/gcc-7.3.0-nolibc/or1k-linux/bin/../libexec/gcc/or1k-linux/7.3.0/cc1: error while loading shared libraries: libisl.so.15: cannot open shared object file: No such file or directory
>>
>>
>> I do have /usr/lib64/libisl.so.10 (not .15) installed on my system.
>> Am I just outofluck for doing this?
>
> This has been pointed out by some others before, sorry for not having addressed
> it yet. I'll be back from travelling on May 22 and should be able to build a set
> of gcc-8.1 binaries without this problem, and also rebuild some of the older
> compilers to fix it (gcc-4.8 is already fixed, but IIRC doesn't
> support openrisc)
>
> What happened here is that I built against the libraries that came
> with Ubuntu 16.04,
> intentionally picking a somewhat older distro in the hope that this
> would produce
> binaries that work on a wider range of systems, but I had it use the
> system libisl,
> libgmp, libmpfc, and libmpc rather than using the one provided by the
> gcc project
> for static linking.
>
> You should be able to just install the binaries from
> https://launchpad.net/ubuntu/xenial/amd64/libisl15/0.16.1-1
> as well as any others you might need along with the toolchain (either
> using dpkg on Debian or Ubuntu, or extracting the .so file into an
> appropriate directory for others) until then.

Thanks. That is working for me now.

--
~Randy

\
 
 \ /
  Last update: 2018-05-08 23:07    [W:0.045 / U:0.752 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site