Frank Mehnert wrote:
> On Tuesday 29 May 2007, Larry Finger wrote:
>> Frank Mehnert wrote:
>>> Hi Larry,
>>>
>>> On Tuesday 29 May 2007, Larry Finger wrote:
>>>> While building the latest svn version on an x86_64 host, I am getting
>>>> the error shown below. My recollection is that I had this once before,
>>>> but that was during the time when 64-bit hosts were not supported. Now,
>>>> it has returned.
>>>>
>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin
>>>> /ld
>>>>
>>>> : skipping incompatible
>>>>
>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../libXt.so when searching
>>>> for -lXt
>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin
>>>> /ld
>>>>
>>>> : skipping incompatible
>>>>
>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../libXt.a when searching
>>>> for -lXt
>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin
>>>> /ld
>>>>
>>>> : skipping incompatible /usr/lib64/libXt.so when searching for -lXt
>>>>
>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin
>>>> /ld
>>>>
>>>> : skipping incompatible /usr/lib64/libXt.a when searching for -lXt
>>>>
>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin
>>>> /ld
>>>>
>>>> : cannot find -lXt
>>>>
>>>> The 32-bit version of libXt.so.6.0.0 is present in /usr/lib, but there
>>>> is no libXt.a nor libXt.la in /usr/lib.
>>> Do you have the packages
>>>
>>>   xorg-x11-libXt-32bit and
>>>   xorg-x11-libXt-devel-32bit
>>>
>>> installed?
>> The devel-32bit was not installed as it is not on my DVD. I downloaded the
>> rpm and installed it, but still get the same error.
> 
> Hmm, and does /usr/lib/libXt.so exist? It should be a symlink to
> libXt.so.6.0.0.

Yes it is there as you say. From the 'locate' command, it was created when the 
devel-32bit rpm was 
installed, but it doesn't help.

Larry


_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to