I vaguely recall seeing something about this, but don't recall if
there was a resolution.
Doug
--
This .signature sanitized for your protection
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
In article <4a7dd122.10...@freebsd.org> you write:
>I vaguely recall seeing something about this, but don't recall if
>there was a resolution.
Well head defaults to f10 linux base now so I'd say you'll need
at least the proper libflashsupport for that (the one installed by
the www/linux-f10-flashp
Hi Doug,
for me it helps to set the following link
ln -s /compat/linux/lib/libssl.so.0.9.8g /compat/linux/lib/libssl.so.5
Hope this helps,
Rainer Hurling
On 08.08.2009 21:25 (UTC+2), Doug Barton wrote:
I vaguely recall seeing something about this, but don't recall if
there was a resolution.
Juergen Lock wrote:
> In article <4a7dd122.10...@freebsd.org> you write:
>> I vaguely recall seeing something about this, but don't recall if
>> there was a resolution.
>
> Well head defaults to f10 linux base now
I've been using that for a while even before it became the default.
> Btw, any pa
On Sat, 08 Aug 2009 22:27:23 +0200
Rainer Hurling wrote:
> Hi Doug,
>
> for me it helps to set the following link
>
> ln -s /compat/linux/lib/libssl.so.0.9.8g /compat/linux/lib/libssl.so.5
>
> Hope this helps,
> Rainer Hurling
>
>
> On 08.08.2009 21:25 (UTC+2), Doug Barton wrote:
> > I vague
Jason J. Hellenthal wrote:
> Is this something that could be handled through libmap.conf rather
> than adding an extraneous symlink to that may stick around after
> package deletion ?
Erroneous libmap.conf entries are just as likely to stick around. :)
You must have missed the part of the thread
