Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 1 Jun 2008 10:30:16 +1000
From:      Peter Jeremy <peterjeremy@optushome.com.au>
To:        Chuck Robey <chuckr@chuckr.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Trying for a duplex printer
Message-ID:  <20080601003016.GA11556@server.vk2pj.dyndns.org>
In-Reply-To: <20080506192504.GD7293@server.vk2pj.dyndns.org>
References:  <48208A9C.8070305@chuckr.org> <20080506192504.GD7293@server.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--EVF5PPMfhYS0aIcm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2008-May-07 05:25:04 +1000, Peter Jeremy <peter@server.vk2pj.dyndns.org>=
 wrote:
>On Tue, May 06, 2008 at 12:43:08PM -0400, Chuck Robey wrote:
>>1) I can't determine which (if any) of the PIPS ports support the RX680, =
and
=2E..
>>2) right now, none of them build because of an error you get about a
>>   linuxwrapper not handling symbol versioning.
>
>This is a bigger issue.  The linuxpluginwrapper maintainer is not
>responding to emails about it so I doubt it will get fixed anytime
>soon.  I've had a quick look at it and decided that I don't understand
>enough about how the symbol aliasing used to work or how the symbol
>versioning broke it.

I finally bit the bullet and used the sledge-hammer approach to get my
pips-scx3500_3600s driver going again.  Basically, I manually built
the driver via its configure script, using a mixture of the
ports/pip800/files patches, contents of ports/pips800/Makefile.pips,
how linuxpluginwrapper worked and bits liberated from glibc.

To get the supplied .so to work, I needed to strip out the
'.gnu.version' and '.gnu.version_r' sections with objcopy and null out
the 'VERNEED', 'VERNEEDNUM' and 'VERSYM' tags in the dynamic segment
using a hex editor.  I checked that I'd found everything by directly
linking pips-scx3500_3600s against the .so (though I installed the
version that dlopen's the .so).

The result works for me but I doubt I can turn it into a port.  I suspect
a similar approach will work for you.

--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.

--EVF5PPMfhYS0aIcm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkhB7ZgACgkQ/opHv/APuIfQogCaAhPZeq/64tYt0HOkOqxldixg
IUkAn1bgIdz8I9T0S6ZbV37DLZSTgF9p
=1HY/
-----END PGP SIGNATURE-----

--EVF5PPMfhYS0aIcm--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080601003016.GA11556>