Date: Fri, 21 Nov 2014 22:07:21 -0200 From: Luciano Rottava da Silva <rottava@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: olvwm on amd64 Message-ID: <CAGROAxWycOTSnZwW85aCsWPEesDbneYAG_cUkerRKDNatryV1g@mail.gmail.com> In-Reply-To: <546F3259.6000205@gmail.com> References: <CAGROAxU0OK7ZZYpuaqFQ3u6UjiUSeBE18adcpudoxcjtFodATQ@mail.gmail.com> <546E5D2D.6010603@gmail.com> <CAGROAxUzdfZEzfaix_NFbNXHsHJJ7yR9U2bxgOA3_KtNWh8aKQ@mail.gmail.com> <546EE14E.7050507@gmail.com> <CAGROAxX8WpBZo5zPT4nBLVDJAX3N%2Bk%2Bhw1ncRSqQkFQH77UkRA@mail.gmail.com> <546F277B.8030204@qeng-ho.org> <546F3259.6000205@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@desktop:/tmp/XVIEW/bin # ldd olvwm
olvwm:
libXpm.so.4 =3D> not found (0)
libolgx.so.3 =3D> /usr/lib32/libolgx.so.3 (0x280ad000)
libXext.so.6 =3D> not found (0)
libX11.so.6 =3D> not found (0)
libm.so.5 =3D> /usr/lib32/libm.so.5 (0x280bb000)
libc.so.7 =3D> /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@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@gmail.com> wrote:
>
> On 11/21/2014 13:52, Arthur Chance wrote:
>
>> On 21/11/2014 11:29, Luciano Rottava da Silva wrote:
>>
>>> That=C2=B4s the point. Binary packages are available for i386, but I gu=
ess
>>> it=C2=B4s
>>> not possible to run them in FreeBSD. Maybe similar to OpenBSD where amd=
64
>>> 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 (mentio=
ned
>> 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. lib=
32
> 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) fr=
om
>>> 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@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@desktop:/usr/ports/x11-wm/olvwm # make install clean
>>>>> =3D=3D=3D> olvwm-4.2_1 depends on file: /usr/local/sbin/pkg - found
>>>>> =3D=3D=3D> Fetching all distfiles required by olvwm-4.2_1 for buildin=
g
>>>>> =3D=3D=3D> Extracting for olvwm-4.2_1
>>>>> =3D> SHA256 Checksum OK for olvwm4.tar.Z.
>>>>> =3D> SHA256 Checksum OK for olvwm4.Patch01.Z.
>>>>> =3D> SHA256 Checksum OK for olvwm4.Patch02.Z.
>>>>> =3D=3D=3D> Patching for olvwm-4.2_1
>>>>> =3D=3D=3D> Applying distribution patches for olvwm-4.2_1
>>>>> =3D=3D=3D> Applying FreeBSD patches for olvwm-4.2_1
>>>>> =3D=3D=3D> olvwm-4.2_1 depends on executable: imake - found
>>>>> =3D=3D=3D> olvwm-4.2_1 depends on executable: tradcpp - found
>>>>> =3D=3D=3D> olvwm-4.2_1 depends on file: /usr/local/libdata/pkgconfi=
g/xpm.pc
>>>>> -
>>>>> found
>>>>> =3D=3D=3D> olvwm-4.2_1 depends on shared library: libxview.so - not=
found
>>>>> =3D=3D=3D> Verifying for libxview.so in /usr/ports/x11-toolkits/xv=
iew
>>>>> =3D=3D=3D> xview-3.2.1.4.19c_1 is only for i386, while you are runni=
ng
>>>>> 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@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/package=
s
>>>>>>> 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@freebsd.org mailing list
>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>>>>>> To unsubscribe, send any mail to "freebsd-questions-
>>>>>>> unsubscribe@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-bi=
t
>>>> 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. Y=
ou
>>>> 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@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-
> unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGROAxWycOTSnZwW85aCsWPEesDbneYAG_cUkerRKDNatryV1g>