On 2020-Feb-22, at 09:29, Stefan Eßer wrote:
> Am 22.02.20 um 03:50 schrieb Mark Millard via freebsd-ports:
>>
>>
>> . . .
>>
>> In the style of my prior examples (including the change that
>> found libedit and such), analogous would be:
>>
>> # find /usr/local/*bin* /usr/local/lib* -type
Am 22.02.20 um 03:50 schrieb Mark Millard via freebsd-ports:
>
>
> On 2020-Feb-21, at 15:59, Kevin Oberman wrote:
>
>> On Fri, Feb 21, 2020 at 8:38 AM Mark Millard via freebsd-ports
>> wrote:
>> Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd
>> there are commands such as
On 2020-Feb-21, at 15:59, Kevin Oberman wrote:
> On Fri, Feb 21, 2020 at 8:38 AM Mark Millard via freebsd-ports
> wrote:
> Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd
> there are commands such as the following that might help:
>
> . . .
>
> This can be a lot of files
Revision 358165 of base repository did a __FreeBSD_version bump.
I think it's better to rebuild all ports.
Because binaries contain versions.
The following is an example.
> file /bin/\[
/bin/[: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD),
dynamically linked, interpreter
On Fri, Feb 21, 2020 at 8:38 AM Mark Millard via freebsd-ports <
freebsd-ports@freebsd.org> wrote:
> Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd
> there are commands such as the following that might help:
>
> # find /usr/local/bin* /usr/local/lib* -type f | xargs -n1 file -F
On 2020-Feb-21, at 08:38, Mark Millard wrote:
> Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd
> there are commands such as the following that might help:
>
> . . .
>
> This can be a lot of files to go through (e.g., lib*) and so
> can take a fair amount of time.
The
Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd
there are commands such as the following that might help:
# find /usr/local/bin* /usr/local/lib* -type f | xargs -n1 file -F ' ' | grep
'ELF.*dynamically' | cut -f1 -d' ' | xargs ldd -f '%A %o\n' | grep
ncurses\.so\.8 | more
On Fri, Feb 21, 2020 at 11:41:15AM +, Lorenzo Salvadore via freebsd-ports
wrote:
> > > Are there any way to know which of installed ports are linked to base
> > > ncurses?
> > > Best Regards.
> >
> > All the one with USES=ncurses in ports, otherwise I am sorry but no we have
> > no
> > way
On 2/21/20 3:25 AM, Baptiste Daroussin wrote:
> On Fri, Feb 21, 2020 at 05:22:15PM +0900, Yasuhiro KIMURA wrote:
>> (Switch to freebsd-ports ML)
>>
>> From: Baptiste Daroussin
>> Subject: svn commit: r358166 - head
>> Date: Thu, 20 Feb 2020 09:33:14 + (UT
> > Are there any way to know which of installed ports are linked to base
> > ncurses?
> > Best Regards.
>
> All the one with USES=ncurses in ports, otherwise I am sorry but no we have no
> way to track that down.
What about "pkg query -a '%n: %B' | grep ncurses"? Maybe it can not distinguish
From: Baptiste Daroussin
Subject: Re: svn commit: r358166 - head
Date: Fri, 21 Feb 2020 09:25:22 +0100
>> Are there any way to know which of installed ports are linked to base
>> ncurses?
>>
> All the one with USES=ncurses in ports, otherwise I am sorry but no we h
On Fri, Feb 21, 2020 at 05:22:15PM +0900, Yasuhiro KIMURA wrote:
> (Switch to freebsd-ports ML)
>
> From: Baptiste Daroussin
> Subject: svn commit: r358166 - head
> Date: Thu, 20 Feb 2020 09:33:14 + (UTC)
>
> > Author: bapt
> > Date: Thu Feb 20 09:33:14 2020
&g
(Switch to freebsd-ports ML)
From: Baptiste Daroussin
Subject: svn commit: r358166 - head
Date: Thu, 20 Feb 2020 09:33:14 + (UTC)
> Author: bapt
> Date: Thu Feb 20 09:33:14 2020
> New Revision: 358166
> URL: https://svnweb.freebsd.org/changeset/base/358166
>
> Log:
>
13 matches
Mail list logo