Now i got it!
Thanks for the clarification.
i did extract the i386 and x86_64 files to the same directory and run
rpm -Uvh --oldpackage *.rpm
but i got a bunch of conflicts messages like these
conflicts with file from package glibc-headers-2.5-65.x86_64
file /usr/include/sys/io.h from install of
glibc-headers-2.5-65.i386 conflicts with file from package
glibc-headers-2.5-65.x86_64
file /usr/include/sys/perm.h from install of
glibc-headers-2.5-65.i386 conflicts with file from package
glibc-headers-2.5-65.x86_64
file /usr/include/sys/procfs.h from install of
glibc-headers-2.5-65.i386 conflicts with file from package
glibc-headers-2.5-65.x86_64
file /usr/include/sys/reg.h from install of
glibc-headers-2.5-65.i386 conflicts with file from package
glibc-headers-2.5-65.x86_64
file /usr/include/sys/ucontext.h from install of glibc-headers-2.5-65.i3
is it bad?
On Wed, Oct 10, 2012 at 5:28 PM, Alex Zahn <[email protected]> wrote:
> It looks like you tried to install the x86_64 and src rpm's. What I meant to
> say is that you should install both the x86_64 and i386 rpm's (given of
> course that you have a 64 bit system). The src tarball only contains rpm's
> that contain source code and instructions for creating the installable rpm's
> in the glibc-2.5-65.el5.i386.tar.gz and glibc-2.5-65.el5.x86_64.tar.gz
> tarballs.
>
> If I recall correctly, the x86_64 rpms actually depend on the i386 rpms. 64
> bit systems definitely need both 32 and 64 bit versions of glibc. It's
> probably a good idea not to have a version mismatch between the two. In case
> something goes wrong (there's no guarantee that something will, however),
> you should unpack the i386 tarball and install everything in it as before.
>
> Also, rpm -Uvh threw an error on encountering src rpm's, but again, those
> don't do anything.
>
> -Alex
>
> On Wed, Oct 10, 2012 at 9:44 AM, Ricardo Finger <[email protected]> wrote:
>>
>> Hello Alex and Ivan.
>> Thanks for your help.
>> Now the system is compiling!
>>
>> I finally installed glibc 2.6-65 from Alex's link, but I had to use the
>> --nodeps option to go through i.e:
>>
>> rpm -Uvh --oldpackage --nodeps *.rpm
>>
>> it might not be totally advisable to deactivate the dependencies
>> checking.... but it worked!
>>
>> Cheers,
>>
>> Ricardo.
>>
>>
>>
>> On 10-10-2012 9:37, Ricardo Finger wrote:
>>
>> Hello Alex,
>>
>> I downloaded and extracted glibc-2.5-65.el5.x86_64.tar.gz and
>> glibc-2.5-65.src.rpm.tar.gz to the same directory and run rpm, but it seems
>> it doesn't work: please see the log.
>> I tried to compile after that, but the same error appears.
>>
>> [root@suseradio glibc-2.5-65.el5.x86_64.tar.gz_FILES]# ls
>> glibc-2.5-65.x86_64.rpm glibc-headers-2.5-65.x86_64.rpm
>> glibc-common-2.5-65.x86_64.rpm glibc-utils-2.5-65.x86_64.rpm
>> glibc-debuginfo-2.5-65.x86_64.rpm nscd-2.5-65.x86_64.rpm
>> glibc-devel-2.5-65.x86_64.rpm
>> [root@suseradio glibc-2.5-65.el5.x86_64.tar.gz_FILES]#
>> [root@suseradio glibc-2.5-65.el5.x86_64.tar.gz_FILES]# rpm -Uvh
>> --oldpackage *.rpm
>> warning: glibc-2.5-65.src.rpm: Header V3 DSA signature: NOKEY, key ID
>> 192a7d7d
>> error: Failed dependencies:
>> glibc-common = 2.5-81.el5_8.7 is needed by (installed)
>> glibc-2.5-81.el5_8.7.i686
>> [root@suseradio glibc-2.5-65.el5.x86_64.tar.gz_FILES]#
>>
>>
>>
>>
>> On 08-10-2012 18:56, Alex Zahn wrote:
>>
>> The latest version is too new, and the oldest version in the repositories
>> now is too new as well.
>>
>> I built the newest compatible glibc rpms and put them at
>> betacage.caltech.edu
>>
>> If you download and unpack the two non-source tarballs to the same
>> directory, you can install the rpms just with
>>
>> rpm -Uvh --oldpackage *.rpm
>>
>> -Alex
>>
>> On Mon, Oct 8, 2012 at 3:24 PM, Ricardo Finger <[email protected]> wrote:
>>>
>>> Hello Alex,
>>>
>>> Running yum install glibc I am getting this:
>>>
>>> Package glibc-2.5-81.el5_8.7.x86_64 already installed and latest version
>>> Package glibc-2.5-81.el5_8.7.i686 already installed and latest version
>>>
>>> so it seem i am working with 2.5, which it seems to be the latest
>>> version in the repository I have.
>>> is it too new?
>>>
>>> I tried:
>>> yum downgrade glibc
>>> but it failed with a missing dependency error.
>>>
>>> Ricardo.
>>>
>>>
>>> On Mon, Oct 8, 2012 at 6:58 PM, Alex Zahn <[email protected]> wrote:
>>> > Do you know what version of glibc you have? The default on RHEL 5.8 is
>>> > too
>>> > new for use with ISE 11.
>>> >
>>> > -Alex
>>> >
>>> > On Mon, Oct 8, 2012 at 2:24 PM, Ricardo Finger <[email protected]>
>>> > wrote:
>>> >>
>>> >> Dear Casperites,
>>> >>
>>> >> I am trying to make a Centos 5.8 64bit / Matlab2009b / ISE 11.4 /
>>> >> glibc-2.5 to work. I followed the steps of the "Xilin ISE 11.4 Setup"
>>> >> wiki page, but when I try to compile any design (even the most simples
>>> >> one) I got the following error:
>>> >>
>>> >> ======= Memory map: ========
>>> >>
>>> >> //// many lines ////
>>> >>
>>> >> 2ad363fd8000-2ad363fed000 r-xp 00000000 fd:00 43811577
>>> >> /usr/local/hdl/Xilinx/11.1/ISE/lib/lin64/libUtilC_QualityData.so
>>> >> 2ad363fed000-2ad3640ec000 ---p 00015000 fd:00 43811577
>>> >> /usr/local/hdl/Xilinx/11.1/ISE/lib/lin64/libUtilC_QualityData.so
>>> >> 2ad3640ec000-2ad3640ee000 rw-p 00014000 fd:00 43811577
>>> >> /usr/local/hdl/Xilinx/11.1/ISE/lib/lin64/libUtilC_QualityData.so
>>> >> 7fff7f0a1000-7fff7f0f0000 rw-p 7ffffffaf000 00:00 0
>>> >> [stack]
>>> >> 7fff7f187000-7fff7f18a000 r-xp 7fff7f187000 00:00 0
>>> >> [vdso]
>>> >> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
>>> >> [vsyscall]
>>> >> ERROR:EDK - xst: application received signal 6.
>>> >> ERROR:EDK:546 - Aborting XST flow execution!
>>> >>
>>> >> Running NGCBUILD ...
>>> >>
>>> >> Rebuilding cache ...
>>> >> ERROR:EDK:440 - platgen failed with errors!
>>> >> gmake: *** [implementation/system.bmm] Error 2
>>> >> ERROR:EDK - Error while running "gmake -f system.make bits".
>>> >> Return code = 2
>>> >> No changes to be saved in MSS file
>>> >> Saved project XMP file
>>> >> cp: cannot stat `implementation/system.bit': No such file or directory
>>> >> bit file open failed
>>> >> chmod: cannot access `implementation/system.bof': No such file or
>>> >> directory
>>> >> cp: cannot stat `implementation/system.bof': No such file or directory
>>> >>
>>> >> Error using ==> gen_xps_files at 689
>>> >> Programation files generation failed, EDK compilation probably also
>>> >> failed.
>>> >> >>
>>> >>
>>> >> The error is the same no matter what Casper library I am using, and I
>>> >> haven't found anything similar on the mail list.
>>> >> I would highly appreciate any hint.
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Ricardo.
>>> >>
>>> >> --
>>> >> Ricardo Finger Camus
>>> >> Electrical Engineer
>>> >> Astronomy Department
>>> >> University of Chile
>>> >> Of: 56(2)9771122
>>> >> Casilla 36-D, Santiago.
>>> >> http://www.das.uchile.cl/lab_mwl/
>>> >>
>>> >
>>>
>>>
>>>
>>> --
>>> Ricardo Finger Camus
>>> Electrical Engineer
>>> Astronomy Department
>>> University of Chile
>>> Of: 56(2)9771122
>>> Casilla 36-D, Santiago.
>>> http://www.das.uchile.cl/lab_mwl/
>>
>>
>>
>> --
>> Ricardo Finger Camus
>> Electrical Engineer
>> Astronomy Department
>> University of Chile
>> Of: 56(2)9771150
>> Casilla 36-D, Santiago.
>> http://www.das.uchile.cl/lab_mwl/
>>
>>
>> --
>> Ricardo Finger Camus
>> Ingeniero Eléctrico
>> Departamento de Astronomía
>> Universidad de Chile
>> Of: 56(2)9771150
>> Casilla 36-D, Santiago.
>> www.das.uchile.cl/lab_mwl/
>
>
--
Ricardo Finger Camus
Electrical Engineer
Astronomy Department
University of Chile
Of: 56(2)9771122
Casilla 36-D, Santiago.
http://www.das.uchile.cl/lab_mwl/
