olvwm on amd64

Luciano Rottava da Silva rottava at gmail.com
Sat Nov 22 00:07:24 UTC 2014


I think I am getting close.

1. I've downloaded i386 binary packages for xview* and olvwm.
2. Copy olvwm binary to a temporary directory to evaluate:

root at desktop:/tmp/XVIEW/bin # ldd olvwm
olvwm:
        libXpm.so.4 => not found (0)
        libolgx.so.3 => /usr/lib32/libolgx.so.3 (0x280ad000)
        libXext.so.6 => not found (0)
        libX11.so.6 => not found (0)
        libm.so.5 => /usr/lib32/libm.so.5 (0x280bb000)
        libc.so.7 => /usr/lib32/libc.so.7 (0x280e4000)

Then started copying shared libs from the packages I've downloaded to
/usr/lib32. However, I copied all the above and some were identified while
others not.

3. readelf gives me the following:

root at desktop:/tmp/XVIEW/bin # readelf -d olvwm

Dynamic section at offset 0x44014 contains 26 entries:
  Tag        Type                         Name/Value
 0x00000001 (NEEDED)                     Shared library: [libXpm.so.4]
 0x00000001 (NEEDED)                     Shared library: [libolgx.so.3]
 0x00000001 (NEEDED)                     Shared library: [libXext.so.6]
 0x00000001 (NEEDED)                     Shared library: [libX11.so.6]
 0x00000001 (NEEDED)                     Shared library: [libm.so.5]
 0x00000001 (NEEDED)                     Shared library: [libc.so.7]
 0x0000000f (RPATH)                      Library rpath: [/usr/local/lib]

4. Now, to be honest, don't know what's next.

Think it's the shared library path is not correct, but can't figure out how
to fix it.

Any ideas?

Cheers,
Luciano.









On 21 November 2014 10:38, Alnis Morics <alnis.morics at gmail.com> wrote:

>
> On 11/21/2014 13:52, Arthur Chance wrote:
>
>> On 21/11/2014 11:29, Luciano Rottava da Silva wrote:
>>
>>> That´s the point. Binary packages are available for i386, but I guess
>>> it´s
>>> not possible to run them in FreeBSD. Maybe similar to OpenBSD where amd64
>>> platform does not run i386 packages, as far as I know.
>>>
>>
>> I thought that was the entire point of the lib32 subsystem under amd64 -
>> to allow 32 bit code to run on a 64 bit machine? After all, Wine (mentioned
>> below) is 32 bit and runs on amd64.
>>
> Plus FreeBSD i386 build environment described in the link I shared below,
> installed in /compat, if there's no binary package. The packages of Wine
> for amd64 and i386 are different (named "i386-wine" and "wine"); the hard
> work is already done for us, as it is in the Linux distros mentioned. lib32
> doesn't supply libraries for every application we might wish to install;
> they need to be built.
>
>
>>  Because of that, I thought about running binary packages (i386 also) from
>>> Linux using FreeBSD compat layer. Hope it will work.
>>>
>>> However, I wonder how Linux distributions do that! I have a Ubuntu
>>> desktop,
>>> amd64, running olvwm.
>>>
>>> We know xview is not availabe for 64-bit platforms, but applications
>>> based
>>> on it run perfectly in Linux.
>>>
>>> How come?!
>>>
>>> Best Regards.
>>>
>>> On 21 November 2014 04:53, Alnis Morics <alnis.morics at gmail.com> wrote:
>>>
>>>
>>>> On 11/21/2014 00:09, Luciano Rottava da Silva wrote:
>>>>
>>>>  Thanks Alnis but, isn't xview only available for i386?
>>>>>
>>>>> I am stuck because of it. Or am I doing something wrong?
>>>>>
>>>>> root at desktop:/usr/ports/x11-wm/olvwm # make install clean
>>>>> ===>   olvwm-4.2_1 depends on file: /usr/local/sbin/pkg - found
>>>>> ===> Fetching all distfiles required by olvwm-4.2_1 for building
>>>>> ===>  Extracting for olvwm-4.2_1
>>>>> => SHA256 Checksum OK for olvwm4.tar.Z.
>>>>> => SHA256 Checksum OK for olvwm4.Patch01.Z.
>>>>> => SHA256 Checksum OK for olvwm4.Patch02.Z.
>>>>> ===>  Patching for olvwm-4.2_1
>>>>> ===>  Applying distribution patches for olvwm-4.2_1
>>>>> ===>  Applying FreeBSD patches for olvwm-4.2_1
>>>>> ===>   olvwm-4.2_1 depends on executable: imake - found
>>>>> ===>   olvwm-4.2_1 depends on executable: tradcpp - found
>>>>> ===>   olvwm-4.2_1 depends on file: /usr/local/libdata/pkgconfig/xpm.pc
>>>>> -
>>>>> found
>>>>> ===>   olvwm-4.2_1 depends on shared library: libxview.so - not found
>>>>> ===>    Verifying for libxview.so in /usr/ports/x11-toolkits/xview
>>>>> ===>  xview-3.2.1.4.19c_1 is only for i386, while you are running
>>>>> amd64.
>>>>> *** Error code 1
>>>>>
>>>>> Stop.
>>>>> make[1]: stopped in /usr/ports/x11-toolkits/xview
>>>>> *** Error code 1
>>>>>
>>>>> Stop.
>>>>> make: stopped in /usr/ports/x11-wm/olvwm
>>>>>
>>>>>
>>>>> On 20 November 2014 19:29, Alnis Morics <alnis.morics at gmail.com>
>>>>> wrote:
>>>>>
>>>>>   On 11/20/2014 23:01, Luciano Rottava da Silva wrote:
>>>>>
>>>>>>
>>>>>>   Hello,
>>>>>>
>>>>>>>
>>>>>>> I am trying to setup up a new FreeBSD desktop at home based on the
>>>>>>> new
>>>>>>> 10.1
>>>>>>> release.
>>>>>>>
>>>>>>> As usual, my wm of choice is olvwm. Well, didn't know ports/packages
>>>>>>> are
>>>>>>> not available for amd64, only for i386.
>>>>>>>
>>>>>>> Searching on the Internet I've read in many places the problem is
>>>>>>> with
>>>>>>> xview and there's no hope for 64-bit platform.
>>>>>>>
>>>>>>> But then I've found the following website:
>>>>>>>
>>>>>>> http://physionet.caregroup.harvard.edu/physiotools/xview/
>>>>>>>
>>>>>>> So, question is, is it possible to run a i386 Linux package in my
>>>>>>> amd64
>>>>>>> Free machine? Would it be possible run the i386 FreeBSD packages
>>>>>>> xview
>>>>>>> and
>>>>>>> olvwm?
>>>>>>>
>>>>>>> How can I run my beloved olvwm? There must be a way!
>>>>>>>
>>>>>>> Thanks & Regards,
>>>>>>> Luciano.
>>>>>>> _______________________________________________
>>>>>>> freebsd-questions at freebsd.org mailing list
>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>>>>>> To unsubscribe, send any mail to "freebsd-questions-
>>>>>>> unsubscribe at freebsd.org"
>>>>>>>
>>>>>>>   Of course ports are available for amd64. Just run
>>>>>>>
>>>>>>
>>>>>> portsnap fetch extract
>>>>>>
>>>>>> to download and extract the ports tree.
>>>>>>
>>>>>> And olvwm is in ports. To install it, run:
>>>>>>
>>>>>> cd /usr/ports/x11-wm/olvwm
>>>>>> make install clean
>>>>>>
>>>>>> The manual chapter on how to work with ports:
>>>>>>
>>>>>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/
>>>>>> handbook/ports-using.html
>>>>>>
>>>>>> -Alnis
>>>>>>
>>>>>>  [list bumf snipped]
>>
>>>
>>>>>  Ah, I see. Then it's way more complicated. You need a 32-bit build
>>>> environment. There are examples of how to build Wine (which is a 32-bit
>>>> application, too) on a amd64 system (no longer needed because now
>>>> there's a
>>>> i386-wine port) which involves preparing a 32-bit build environment. You
>>>> can take one such example (say, http://daemon-notes.com/
>>>> articles/other/wine/prepare) and build xview instead. But I guess it's
>>>> an
>>>> overkill unless you can't do without xview.
>>>>
>>>
>>
>>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-
> unsubscribe at freebsd.org"
>


More information about the freebsd-questions mailing list