Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Jan 2007 00:42:49 +0300
From:      Boris Samorodov <bsam@ipt.ru>
To:        Divacky Roman <xdivac02@stud.fit.vutbr.cz>
Cc:        Alexander Leidinger <Alexander@Leidinger.net>, freebsd-current@freebsd.org
Subject:   Re: broken linuxulator in -current as of Jan 8 17:51:45 CET
Message-ID:  <89559334@srv.sem.ipt.ru>
In-Reply-To: <20070109210153.GA35342@stud.fit.vutbr.cz> (Divacky Roman's message of "Tue, 9 Jan 2007 22:01:53 %2B0100")
References:  <20070108165157.GA94941@stud.fit.vutbr.cz> <57417212@srv.sem.ipt.ru> <20070108180014.GA4540@stud.fit.vutbr.cz> <20070108210813.368389dc@Magellan.Leidinger.net> <20070109204604.62915dc7@Magellan.Leidinger.net> <89565167@srv.sem.ipt.ru> <20070109213151.2bf5a8f3@Magellan.Leidinger.net> <46677978@srv.sem.ipt.ru> <80597611@srv.sem.ipt.ru> <20070109210153.GA35342@stud.fit.vutbr.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Jan 2007 22:01:53 +0100 Divacky Roman wrote:
> On Tue, Jan 09, 2007 at 11:57:08PM +0300, Boris Samorodov wrote:
> > On Tue, 09 Jan 2007 23:51:01 +0300 Boris Samorodov wrote:
> > 
> > > for i in (linux,freebsd) do
> > >   for y in (/usr,/usr/local,etc) do
> > 
> > I ment if linux, use '/compat/linux + y' prefix.
> > 
> > >     find_a_library
> > >   done
> > > done
> > 
> > Hm, even if we can implement it, the (potential) problem with linux
> > ports installed to /usr/local remains...

> how does this solve the problem? I might misunderstand whats going on

All possible linux paths are searched fistly.

> but as I see it the program opens the libraries in the right order.

> but it "refuses" the correct library and keeps searching. I think
> the problem is in the "refusing".

It refuses the library 'cause it's too new one (maybe that's why you
succeeded with 2.6.16 linux.osrelease -- linuxulator didn't throw this
lib away) and keeps searching for an old one but eats a new FreeBSD
one.

> One thing is very strange - I was able to use acroread on 2 days
> old current and now I am running 2 months old current and I am
> not able to run it. can anyone think of what can cause this?

It should be an another case. What is the diagnostic?


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve



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