: yes (cached)
>- WinDbg builds: no (cached)
>- WinDbgCached builds : no (cached)
>- BOOST_COMP_GNUC >= 4.3.0 : no (cached)
> =>> Killing runaway build after 7200 seconds with no output
>- zlib : ye
=>> Killing runaway build after 7200 seconds with no output
- zlib : yes (cached)
- bzip2: yes (cached)
- lzma : yes (cached)
- zstd : no (cached)
=>> Cleaning up wrkdir
===> Cleaning fo
I get a lot of garbled debug output in rtorrent completely blocking
anything useful to see, probably after restarting rtorrent and after
having upgraded to latest ports version of xmlrpc-c. Is there anything
I can do to fix this?
$ pkg info | grep -e torrent -e xmlrpc
libtorrent-0.13.7_3
Hi,
context: freebsd-12-prerelease / ports r485429
in /usr/ports, make index gives the following odd output:
[snip]
--- describe.x11-wm ---
make_index: ldapscripts-2.0.8: no entry for /usr/ports/ldapwhoami-client
make_index: ldapscripts-2.0.8: no entry for /usr/ports/libssl.so.9
make_index
On 01/28/18 19:31, Baptiste Daroussin wrote:
> On Mon, Jan 29, 2018 at 03:27:22AM +0900, Yasuhiro KIMURA wrote:
>> From: Larry Rosenman
>> Subject: Re: daily security run output and joomla3
>> Date: Sun, 28 Jan 2018 12:04:56 -0600
>>
>>> But as the OP note
On 28/01/2018 18:04, Larry Rosenman wrote:
> On Mon, Jan 29, 2018 at 02:56:51AM +0900, Yasuhiro KIMURA wrote:
>> From: Carmel NY
>> Subject: Re: daily security run output and joomla3
>> Date: Sun, 28 Jan 2018 17:38:10 +
>>
>>>> You ca
29.01.2018 1:04, Larry Rosenman wrote:
>> Accoding to the messages of security periodic sript, the problrem is
>> not checksum mismatch but lost of package files. And "pkg check -r"
>> cannot recover it. So you should reinstall www/joomla3.
>>
> But as the OP notes, the joomla3 instructions *REQUI
On Sun, Jan 28, 2018 at 07:31:00PM +0100, Baptiste Daroussin wrote:
> On Mon, Jan 29, 2018 at 03:27:22AM +0900, Yasuhiro KIMURA wrote:
> > From: Larry Rosenman
> > Subject: Re: daily security run output and joomla3
> > Date: Sun, 28 Jan 2018 12:04:56 -0600
> >
>
On Mon, Jan 29, 2018 at 03:27:22AM +0900, Yasuhiro KIMURA wrote:
> From: Larry Rosenman
> Subject: Re: daily security run output and joomla3
> Date: Sun, 28 Jan 2018 12:04:56 -0600
>
> > But as the OP notes, the joomla3 instructions *REQUIRE*
> > removal of the instal
From: Larry Rosenman
Subject: Re: daily security run output and joomla3
Date: Sun, 28 Jan 2018 12:04:56 -0600
> But as the OP notes, the joomla3 instructions *REQUIRE*
> removal of the install directory for security reasons, so
> I understand where he is coming from.
Do you mean
On Sun, Jan 28, 2018 at 12:04:56PM -0600, Larry Rosenman wrote:
> On Mon, Jan 29, 2018 at 02:56:51AM +0900, Yasuhiro KIMURA wrote:
> > From: Carmel NY
> > Subject: Re: daily security run output and joomla3
> > Date: Sun, 28 Jan 2018 17:38:10 +
> >
> > >
On Mon, 29 Jan 2018 02:56:51 +0900, Yasuhiro KIMURA stated:
>From: Carmel NY
>Subject: Re: daily security run output and joomla3
>Date: Sun, 28 Jan 2018 17:38:10 +
>
>>>You can try "pkg check -r", see man pkg-check
>>
>> Unfortunately, that has
On Mon, Jan 29, 2018 at 02:56:51AM +0900, Yasuhiro KIMURA wrote:
> From: Carmel NY
> Subject: Re: daily security run output and joomla3
> Date: Sun, 28 Jan 2018 17:38:10 +
>
> >>You can try "pkg check -r", see man pkg-check
> >
> > Unfortunatel
From: Carmel NY
Subject: Re: daily security run output and joomla3
Date: Sun, 28 Jan 2018 17:38:10 +
>>You can try "pkg check -r", see man pkg-check
>
> Unfortunately, that has no affect.
Accoding to the messages of security periodic sript, the problrem is
not checksu
On Sun, 28 Jan 2018 17:51:16 +0100, Miroslav Lachman stated:
>Carmel NY wrote on 2018/01/28 11:59:
>> FreeBSD-11.1-RELEASE-p6
>>
>> I have "www/joomla3" installed and working fine. Part of the configuration
>> routine is the removal of the "installation" directory in joomla3 when it is
>> configu
Carmel NY wrote on 2018/01/28 11:59:
FreeBSD-11.1-RELEASE-p6
I have "www/joomla3" installed and working fine. Part of the configuration
routine is the removal of the "installation" directory in joomla3 when it is
configured. This is done as a security feature and joomla3 advertises that it
will
FreeBSD-11.1-RELEASE-p6
I have "www/joomla3" installed and working fine. Part of the configuration
routine is the removal of the "installation" directory in joomla3 when it is
configured. This is done as a security feature and joomla3 advertises that it
will not run if that directory is present.
es itself repeatedly, that was the best way
to get trace output from child processes, it did not suffice to execute the
script with "sh -x portmaster".
Sorry for the breakage, it is fixed in the patch I committed 15v Minutes ago.
Regards, STefan
__
Thank you, it is fixed.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Found it:
It is the shebang
-#!/bin/sh
+#!/bin/sh -x
Stefan please remove "-x"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org
Found it:
-#!/bin/sh
+#!/bin/sh -x
Stefan please remove the "-x"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On 15.12.2017 20:45, Walter Schwarzenfeld wrote:
After recent patch, I had a strange output in my terminal with portmaster
+ trap trap_exit INT
+ umask 022
+ progcmd=/usr/local/sbin/portmaster
+ progname=portmaster
+ realpath /usr/local/sbin/portmaster
+ program=/usr/local/sbin/portmaster
After recent patch, I had a strange output in my terminal with portmaster
+ trap trap_exit INT
+ umask 022
+ progcmd=/usr/local/sbin/portmaster
+ progname=portmaster
+ realpath /usr/local/sbin/portmaster
+ program=/usr/local/sbin/portmaster
+ [ -z '' ]
+ PM_PARENT_PID=40170
+ : /tmp
+
Hi!
> I hope this helps, and if there's anything I can try, please let me know...
Use poudriere to build firefox, then 'pkg add' that locally-build firefox
package.
--
p...@opsec.eu+49 171 3101372 3 years to go !
__
After a couple months' hiatus at playing with ports, I started again with
a fresh checkout. It seems more than a little has changed.
First off, it looks as if -DBATCH no longer works; dialogs still come
up. Is there a replacement?
Second, I tried to use make search. The transcript looks like thi
Le 19/02/2017 à 09:52, Mike Clarke a écrit :
> On Sat, 18 Feb 2017 15:45:12 -0800
> Kevin Oberman wrote:
>
>> This belongs here because the message is a muddled mess. It might belong to
>> gnome@ because I am only aware that gnome is the remaining ports user of
>> this port. (I'm quite possibly wr
On Sat, 18 Feb 2017 15:45:12 -0800
Kevin Oberman wrote:
> This belongs here because the message is a muddled mess. It might belong to
> gnome@ because I am only aware that gnome is the remaining ports user of
> this port. (I'm quite possibly wrong about this.)
>
> It's telling you (very poorly)
On Sat, Feb 18, 2017 at 2:51 PM, Andy Farkas wrote:
>
> I get this in my daily security run output:
>
> Checking for packages with security vulnerabilities:
> Database fetched: Fri Feb 17 03:47:22 AEST 2017
> gstreamer-ffmpeg-0.10.13_4
> avidemux-2.6.11_5
> perl5-5.20.3_
I get this in my daily security run output:
Checking for packages with security vulnerabilities:
Database fetched: Fri Feb 17 03:47:22 AEST 2017
gstreamer-ffmpeg-0.10.13_4
avidemux-2.6.11_5
perl5-5.20.3_15: Tag: expiration_date Value: 2017-06-30
samba36-libsmbclient-3.6.25_2: Tag
hout a trailing colon after the date.
> I normalized all the entries for consistency and am seeing `pkg updating
> -d 20160626` return the expected output for me. Please see if that
> resolved the issue for you as well.
>
> Jason
Aye; it did -- thank you for figuring out what was cata
ed.
>
> This morning, for the first time in ... months, I think, the "pkg
> updating -d ..." command I run to start the process actually generated
> some output -- quite a bit of it.
>
> But I'm at a loss to understand why it did: only one of the ports it
> mentio
dating -d ..." command I run to start the process actually generated
some output -- quite a bit of it.
But I'm at a loss to understand why it did: only one of the ports it
mentioned is installed, and that one didn't get updated by "portmaster
-ad"; the others aren't inst
ssage
Subject: Cron cronic /usr/sbin/pkg audit -F
Date: Sun, 8 Feb 2015 06:56:00 +0100 (CET)
From: Cron Daemon
To: r...@smtp.digiware.nl
Cronic detected failure or error output for the command:
/usr/sbin/pkg audit -F
RESULT CODE: 0
ERROR OUTPUT:
pkg: vulnxml file up-to-date
STANDARD OUTP
t; >
> > and no idea now which package needs reinstall.
>
> Agreed. One need to use verbose output to identifiy the problem.
>
> Xav
>
Thanks, 'pkg check -s -a -v' gives a clue here:
[23/91] Checking gettext-tools-0.19.3: checksums...pkg:
pkg_create_from_dir(
On 07/12/14 09:38, Milan Obuch wrote:
> # pkg check -s -a
> Checking all packages: 24%
> pkg: pkg_create_from_dir(lstat failed): No such file or directory
> Checking all packages: 100%
> #
>
> and no idea now which package needs reinstall.
Agreed. One need to use verbos
new I needed to rebuild/reinstall asterisk (some modules were not
able to load, which manifests itself clearly so is easily
identifiable), after that, the same command's output somewhat changed:
# pkg check -s -a
Checking all packages: 24%
pkg: pkg_create_from_dir(lstat failed): No such file o
On 8/24/2014 7:55 AM, Michael Gmelin wrote:
> On Sun, 24 Aug 2014 18:13:10 +1000
> andrew clarke wrote:
>
>> Installing a package built on another system I noticed pkg 1.3.6 shows
>> incorrect output when installing with a dependency:
>>
>> # ls -l
>>
On Sun, 24 Aug 2014 18:13:10 +1000
andrew clarke wrote:
> Installing a package built on another system I noticed pkg 1.3.6 shows
> incorrect output when installing with a dependency:
>
> # ls -l
> total 41123
> -rw-r--r-- 1 ozzmosis ozzmosis 2428 24 Aug 18:07
> cl
Installing a package built on another system I noticed pkg 1.3.6 shows
incorrect output when installing with a dependency:
# ls -l
total 41123
-rw-r--r-- 1 ozzmosis ozzmosis 2428 24 Aug 18:07
clang-devel-3.6.r216160.txz
-rw-r--r-- 1 ozzmosis ozzmosis 19728928 24 Aug 18:08
llvm-devel
From: Yasuhiro KIMURA
Subject: Re: Output change of 'pkg info' after 1.2.
Date: Mon, 09 Dec 2013 00:11:14 +0900 (JST)
> BTW, I noticed there is no explanation about 'alias' option in
> pkg.conf(5) but two examples in EXAMPLES section. It is far from fatal
> but any
From: Baptiste Daroussin
Subject: Re: Output change of 'pkg info' after 1.2.
Date: Fri, 6 Dec 2013 09:29:30 +0100
>> Then I have one question. Is there any way to get same output as
>> 'pkg info pkg-name' of 1.1.x? I tried some combination of options but
>>
On Fri, Dec 06, 2013 at 01:54:22AM +0900, Yasuhiro KIMURA wrote:
> From: Baptiste Daroussin
> Subject: Re: Output change of 'pkg info' after 1.2.
> Date: Thu, 5 Dec 2013 17:24:09 +0100
>
> > On Thu, Dec 05, 2013 at 04:36:00PM +0100, Michael Gmelin wrote:
> >&g
Am 2013-12-05 17:54, schrieb Yasuhiro KIMURA:
From: Baptiste Daroussin
Subject: Re: Output change of 'pkg info' after 1.2.
Date: Thu, 5 Dec 2013 17:24:09 +0100
On Thu, Dec 05, 2013 at 04:36:00PM +0100, Michael Gmelin wrote:
On Fri, 06 Dec 2013 00:13:38 +0900 (JST)
Yasuhiro KIM
From: Baptiste Daroussin
Subject: Re: Output change of 'pkg info' after 1.2.
Date: Thu, 5 Dec 2013 17:24:09 +0100
> On Thu, Dec 05, 2013 at 04:36:00PM +0100, Michael Gmelin wrote:
>> On Fri, 06 Dec 2013 00:13:38 +0900 (JST)
>> Yasuhiro KIMURA wrote:
>>
>>
On Thu, Dec 05, 2013 at 04:36:00PM +0100, Michael Gmelin wrote:
> On Fri, 06 Dec 2013 00:13:38 +0900 (JST)
> Yasuhiro KIMURA wrote:
>
> > I noticed that output of 'pkg info' changed after version 1.2.
> >
> > If I remember correctly, 1.1.x behaved as follow
On Fri, 06 Dec 2013 00:13:38 +0900 (JST)
Yasuhiro KIMURA wrote:
> I noticed that output of 'pkg info' changed after version 1.2.
>
> If I remember correctly, 1.1.x behaved as following:
>
> - 'pkg info -q pkg-name' outputs package name with version.
> - &#
I noticed that output of 'pkg info' changed after version 1.2.
If I remember correctly, 1.1.x behaved as following:
- 'pkg info -q pkg-name' outputs package name with version.
- 'pkg info pkg-name' outputs package name with version, and comment.
- 'pkg info -f
So, I've noticed this now, but also on make install of a port... At
the end when it dumps all the info about the various port/packages it
installed, it can produce a lot of output... In my case I don't know
how many ports I installed, but it was a couple screen fulls...
The problem i
; Am Dienstag, 23. Juli 2013, 08:48:38 schrieb Bryan Drewery:
> >> On 7/23/2013 8:36 AM, Wolfgang Riegler wrote:
> >>> Hi,
> >>>
> >>> I having trouble using poudriere since updating it to 3.0.4 on FreeBSD
> >>> 9.1-p4. Trying poudriere-devel thro
i 2013, 08:48:38 schrieb Bryan Drewery:
>> On 7/23/2013 8:36 AM, Wolfgang Riegler wrote:
>>> Hi,
>>>
>>> I having trouble using poudriere since updating it to 3.0.4 on FreeBSD
>>> 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete
&g
using poudriere since updating it to 3.0.4 on FreeBSD
> > 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete
> > output of trying to compile shells/bash:
> >
> >
> > # poudriere bulk -p hostportstree -f
> > /usr/local/e
On 7/23/2013 8:36 AM, Wolfgang Riegler wrote:
> Hi,
>
> I having trouble using poudriere since updating it to 3.0.4 on FreeBSD
> 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete
> output of trying to compile shells/bash:
>
>
> # poudriere
Hi,
I having trouble using poudriere since updating it to 3.0.4 on FreeBSD 9.1-p4.
Trying poudriere-devel throws the same error. Here is the complete output of
trying to compile shells/bash:
# poudriere bulk -p hostportstree -f
/usr/local/etc/poudriere.d/91amd64-buildlist.conf -j 91amd64 -J
On 6/28/2013 7:31 AM, Anton Shterenlikht wrote:
> This is on amd64 r252033 with ports at 321955:
>
> Running portmaster -a I see this:
>
> ===>>> Returning to update check of installed ports
>
> make: "/usr/ports/graphics/ImageMagick/Makefile" line 83:
This is on amd64 r252033 with ports at 321955:
Running portmaster -a I see this:
===>>> Returning to update check of installed ports
make: "/usr/ports/graphics/ImageMagick/Makefile" line 83: warning: Couldn't
read shell's output for "/bin/sh -c 'case `per
/bsd.port.subdir.mk" line 101: warning: Couldn't read
> > shell's output for "if /sbin/sysctl -n compat.ia32.maxvmem >/dev/null
> > 2>&1; then echo YES; fi" make: "/usr/ports/Mk/bsd.port.mk" line 1638:
> > warning: Couldn't read shell
On 6/21/2013 16:42, Anton Shterenlikht wrote:
On ia64 r252055 with ports at r321471 make issues lots of warnings
like:
# make -C /usr/ports/ fetchindex make:
"/usr/ports/Mk/bsd.port.subdir.mk" line 101: warning: Couldn't read
shell's output for "if /sbin/sysctl -n compa
On ia64 r252055 with ports at r321471
make issues lots of warnings like:
# make -C /usr/ports/ fetchindex
make: "/usr/ports/Mk/bsd.port.subdir.mk" line 101: warning: Couldn't read
shell's output for "if /sbin/sysctl -n compat.ia32.maxvmem >/dev/null 2>&1;
then
. done.
Applying patches... done.
Yet looking in svn latest commit was 13 hours ago, not fifteen minutes...
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Strange-portsnap-output-change-in-metadate-without-changes-tp5802779.html
Sent from the freebsd-ports mailing list
the problem to having a look at the output of e.g.
'${PREFIX}/bin/dialog4ports --version'. Something like 'Version: 0.1.2'
would do, which is easily parseable.
From there, you'd be able to check this in the wrapper, and act
differently on different versions (no, please d
On 3/25/2013 6:35 AM, Bryan Drewery wrote:
> On 3/25/2013 5:11 AM, Ilya A. Arkhipov wrote:
>> Hi All,
>>
>> Fixed in
>> https://bitbucket.org/m1cro/d4p/commits/42e03ab186b30120fa79e2d0a6093a3c673385ef
>>
>> Thanks Marco.
>>
>> After checking it will committed, but you already can test it:
>> - chan
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the
host
via ssh.
I've also tried on 8.4-BETA1 (r248617), but got the same
behaviour.
Anyone else experiencing this ?
Yes, I have also experienced this.
8.3-STABLE r244863
>> Hi,
> >>>
> >>> after installing dialog4ports, I'm getting the following behaviour
> >>> on each 8.3-STABLE I tried:
> >>>
> >>> # jexec /bin/tcsh
> >>> # cd
> >>> # make config
> >>>
> >&
:
On Sun, 24 Mar 2013 23:40:47 +0400
"Eugene V. Boontseff" wrote:
*Marco Steinbach wrote:
*
Hi,
after installing dialog4ports, I'm getting the following behaviour
on each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-output
===> Options unchanged
On 3/25/2013 5:11 AM, Ilya A. Arkhipov wrote:
> Hi All,
>
> Fixed in
> https://bitbucket.org/m1cro/d4p/commits/42e03ab186b30120fa79e2d0a6093a3c673385ef
>
> Thanks Marco.
>
> After checking it will committed, but you already can test it:
> - change dialog4ports version to 0.1.2
> - make makesum
>
ene V. Boontseff" wrote:
*Marco Steinbach wrote:
*
Hi,
after installing dialog4ports, I'm getting the following behaviour
on each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the co
bach wrote:
*
Hi,
after installing dialog4ports, I'm getting the following behaviour
on each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the host
via ssh.
I
ports, I'm getting the following behaviour
on each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the host
via ssh.
I've also tried on 8.4-BETA1 (r248617)
our
on each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the host
via ssh.
I've also tried on 8.4-BETA1 (r248617), but got the same behaviour.
Anyone else expe
sh
# cd
# make config
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the host
via ssh.
I've also tried on 8.4-BETA1 (r248617), but got the same behaviour.
Anyone else experiencing this ?
Yes, I have also experienced this.
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the host
via ssh.
I've also tried on 8.4-BETA1 (r248617), but got the same behaviour.
Anyone else experiencing this ?
Yes, I have also experienced this.
8.3-STABLE r244863
Only
Michael Gmelin schrieb:
On Sun, 24 Mar 2013 23:40:47 +0400
"Eugene V. Boontseff" wrote:
*Marco Steinbach wrote:
*
Hi,
after installing dialog4ports, I'm getting the following behaviour
on each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-outp
On Sun, 24 Mar 2013 23:40:47 +0400
"Eugene V. Boontseff" wrote:
> *Marco Steinbach wrote:
> *
> > Hi,
> >
> > after installing dialog4ports, I'm getting the following behaviour
> > on each 8.3-STABLE I tried:
> >
> > # jexec /bin/tcsh
&
*Marco Steinbach wrote:
*
Hi,
after installing dialog4ports, I'm getting the following behaviour on
each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the
Hi,
after installing dialog4ports, I'm getting the following behaviour on
each 8.3-STABLE I tried:
# jexec /bin/tcsh
# cd
# make config
cannot open tty-output
===> Options unchanged
#
Regardless, if I'm logged in on the console or connect to the host via ssh.
I've
b-1.0.21_1 - this is the output:
>
> ===>>> linux-f10-alsa-lib-1.0.21_1
> ===>>> No ORIGIN in /var/db/pkg/linux-f10-alsa-lib-1.0.21_1/+CONTENTS
>
> I don't understand what it means exactly and wondered if someone could
> explain? and perhap
Hi
This morning I updated my ports tree using svn. Then used `portmaster -L` to
check outdated ports, etc. and there is a message/warning/whatever, from
portmaster about linux-f10-alsa-lib-1.0.21_1 - this is the output:
===>>> linux-f10-alsa-lib-1.0.21_1
===>>
On 6/8/12 4:02 PM, Jakub Lach wrote:
Or is it new options framework? I thought that old knobs
would still work.
that is usually the goal, but, definition of an upgrade:
'take old bugs out, put new bugs in'
so, they are supposed to work, but are causing problems in some cases.
--
Michael Sch
Or is it new options framework? I thought that old knobs
would still work.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/strange-output-from-make-tp5716636p5716640.html
Sent from the freebsd-ports mailing list archive at Nabble.com
/usr/ports/Mk/bsd.port.mk looks broken
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/strange-output-from-make-tp5716636p5716639.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #21 r236721: Thu Jun 7
15:52:12 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64
After a recent portsnap fetch update I'm seeing this output:
# make search name=ssldump
"/usr/ports/Mk/bsd.port.mk", line 6097: Malfor
Hi, folks.
I'm running:
FreeBSD orion 8.0-CURRENT FreeBSD 8.0-CURRENT #6 r195343: Sat Jul 4
12:23:04 EDT 2009 r...@orion:/usr/obj/usr/src/sys/ORION i386
Once security/rkhunter reaches the 'Performing malware checks', there
appears to be no I/O -- this check used to take less than 2 minutes
7 20:52:52 sub kernel:
oss_sbxfi: Interrupts don't seem to be working. May 27 20:52:52 sub
kernel: oss_sbxfi0: port 0xdf00-0xdf1f mem
0xdfff8000-0xdfffbfff,0xdfc0-0xdfdf,0xd800-0xdbff irq
16 at device 1.0 on pci2
Additionally I had no Sound output and xmms/mplayer seemed pre
Usage: radiusniff [-vVrqa] [-i interface] [-f expression]
[-d dictionary ] [-c clients] [-s passwd]
for me on the localhost interface, the sniff give me :
# radiusniff -v -ilo0
ERROR: 7.20.0.64:56 > 7.20.0.64:49364 - non RADIUS packet (bad length in
packet: 60328)
--
Script started on Sat Mar 1 18:10:02 2008
[EMAIL PROTECTED] /tmp]# exitmore bsd.port.mk ls[Kcd
/usr/ports/Mkvsup -g -L2 -hcvsup4.freebsd.org
/root/ports-supfile && p
portupgrade -aDD
Parsing supfile "/root/ports-supfile"
Connecting to cvsup4.freebsd.org
On Sun, Nov 11, 2007 at 05:03:59AM -0500, Aryeh M. Friedman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> If I do "make search key=XXX display=[br]deps" it displays the deps in
> question twice... is there a difference between the two and if so if
> want to know what needs to be bui
Aryeh M. Friedman wrote:
> If I do "make search key=XXX display=[br]deps" it displays the deps in
> question twice... is there a difference between the two and if so if
> want to know what needs to be build before the port can be built or
> run which list do I use?
>
Did you ever RTFM at all?
"b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I do "make search key=XXX display=[br]deps" it displays the deps in
question twice... is there a difference between the two and if so if
want to know what needs to be build before the port can be built or
run which list do I use?
- --
Aryeh M. Frie
On Tuesday 15 May 2007 23:59:23 Pav Lucistnik wrote:
> You expect dependencies in LOCALBASE and install into PREFIX.
Shouldn't you install into ${DESTDIR}${PREFIX} or ${TARGETDIR} ?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mail
Tijl Coosemans píše v st 16. 05. 2007 v 15:44 +0200:
> On Tuesday 15 May 2007 23:59:23 Pav Lucistnik wrote:
> > You expect dependencies in LOCALBASE and install into PREFIX.
>
> Shouldn't you install into ${DESTDIR}${PREFIX} or ${TARGETDIR} ?
Hell no :)
That plan got scraped.
--
Pav Lucistnik
Li-Lun Wang (Leland Wang) píše v st 16. 05. 2007 v 04:02 +0800:
> A port installs modules into $SCIM_MODULEDIR, which is determined by
> using
>
> SCIM_MODULEDIR=`pkg-config --variable=moduledir scim`
>
> during configure. I wonder if I should just let the port to install to
> $SCIM_MODUL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
A port installs modules into $SCIM_MODULEDIR, which is determined by
using
SCIM_MODULEDIR=`pkg-config --variable=moduledir scim`
during configure. I wonder if I should just let the port to install to
$SCIM_MODULEDIR determined this way
More data. I was trying to use the PPD for the 5550, and the output
from the testpage was not raw PS, but a mangled cups test page with all
kinds of FF in it. Just on a whim, I tried the generic printer and the
"Generic PCL 6/PCL XL Printer Foomatic/hpijs" PPD, and that worked fine
(
Background: FBSD 6.1 (recently upgraded from 5.5). Did fairly massive
upgrade of apps.
foomatic-db-20060922= up-to-date with port
foomatic-db-engine-20060922,1 = up-to-date with port
foomatic-db-hpijs-1.4 = up-to-date with port
foomatic-filters-3.0.2_4= up-to-date with p
Below is a short program to make the single line output of
pretty-print-*-depends-list actually readable. This prints the case
insensitively sorted & merged output of both run & build dependencies.
Feel free to modify. Each dependency is listed on its own line.
#!perl
use str
95 matches
Mail list logo
