Re: gcc 8.1 + libc.a

2018-10-04 Thread Jonathan Wakely
Please don't cross-post to both gcc@gcc.gnu.org and gcc-h...@gcc.gnu.org, it is almost never appropriate to send the same email to both lists, because they are for discussing different topics. You're looking for help, so use gcc-help not gcc. Please remove gcc@gcc.gnulorg from further replies in t

Re: gcc 8.1 + libc.a

2018-10-03 Thread Jost, Gabriele (ARC-TNC)[Supersmith] via gcc
: Dmitry Mikushin Date: Wednesday, October 3, 2018 at 5:00 PM To: "Jost, Gabriele (ARC-TNC)[Supersmith]" Cc: "gcc-h...@gcc.gnu.org" , GCC Subject: Re: gcc 8.1 + libc.a First of, "error opening libc.a" message looks highly unusual. It's not the way ld typically c

Re: gcc 8.1 + libc.a

2018-10-03 Thread Dmitry Mikushin
First of, "error opening libc.a" message looks highly unusual. It's not the way ld typically complains about a missing library or wrong architecture. More likely, here it is rather some gcc-internal lib.a to be deployed in some special way, but was missing. I would try two things: 1) Re-iterate th

gcc 8.1 + libc.a

2018-10-03 Thread Jost, Gabriele (ARC-TNC)[Supersmith] via gcc
Hello, I have successfully installed gcc 8.1 on one system. I had to build the accelerator on the front end, because the compute nodes did not have libc.a. The build process seems to require a libc.a. I am now struggling with trying to install it on a different system: Same concept, front end has