I've been trying to get all the mssge toolflow stuff running on a new SL
5.8 machine. Everything works except that compilation fails at xst
synthesis for even the simplest designs with a lot of complaints from glibc.
A while back there was a thread describing some very similar issues. I
believe it
I suggest using ISE 13 if that's an option for you.
On Thu, Aug 9, 2012 at 4:47 PM, Alex Zahn wrote:
> I've been trying to get all the mssge toolflow stuff running on a new SL 5.8
> machine. Everything works except that compilation fails at xst synthesis for
> even the simplest designs with a lot
> I've been trying to get all the mssge toolflow stuff running on a new SL
> 5.8 machine. Everything works except that compilation fails at xst
> synthesis for even the simplest designs with a lot of complaints from
> glibc.
>
> A while back there was a thread describing some very similar issues. I
I'm not sure how to force a dynamically linked program to use compat-glibc
instead of the default glibc...maybe some convoluted chroot trickery?
In the meantime, I found an old source rpm for glibc 2.5-65. As soon as a I
finish building and installing it I'll let everyone know how it goes. If it
w
> I'm not sure how to force a dynamically linked program to use compat-glibc
> instead of the default glibc...maybe some convoluted chroot trickery?
I think that's the purpose of the compat-glibc package. I think you tell
it with some environment variable.
The wonders of dynamic linking...
>
>
It looks like rolling back to the rebuilt glibc 2.5-65 rpms worked. It's
too early to tell if I broke anything on our system, but everything, ISE 11
included, appears to be in good working order. What system damage lurks
unseen, only time will tell...
The rpms for RHEL5 (compiled on a Scientific L
6 matches
Mail list logo
