On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote:
Can anyone tell me where PORTS_MODULES is documented? I don't find it in
the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I
thing) wrote it. This is a very beneficial tool. It really needs to be well
On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote:
On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote:
Hi,
The nvidia-driver package needs to be recompiled with the latest
FreeBSD-current sources, because of changes in the callout subsystem.
If
On Sat, Jan 17, 2015 at 7:43 AM, Andreas Tobler andreast-l...@fgznet.ch
wrote:
On 17.01.15 16:18, Bob Willcox wrote:
Yesterday when I upgraded my current box I encountered this failure when
attempting to load the nvidia-driver (nvidia.so):
link_elf_obj: symbol _callout_stop_safe undefined
On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote:
...
Can anyone tell me where PORTS_MODULES is documented? I don't find it in
the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I
thing) wrote it. This is a very beneficial tool. It really needs to be well
Any hope to get a bit of text on this into the Handbook? Maybe with the
example in Doug B.'s e-mail announcing it. (It's in the ports archive and
DuckDuckGo can find it easily.) The example in build(7) is for a single
module while Doug's message show that they should be space delimited.
--
R.
On Sat, Jan 17, 2015 at 8:34 PM, Bob Willcox b...@immure.com wrote:
On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote:
On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote:
Hi,
The nvidia-driver package needs to be recompiled with the latest
Yesterday when I upgraded my current box I encountered this failure when
attempting to load the nvidia-driver (nvidia.so):
link_elf_obj: symbol _callout_stop_safe undefined
linker_load_file: Unsupported file type
So, today I updtated my system again today hoping it might be fixed but the
problem
On 01/17/15 16:18, Bob Willcox wrote:
Yesterday when I upgraded my current box I encountered this failure when
attempting to load the nvidia-driver (nvidia.so):
link_elf_obj: symbol _callout_stop_safe undefined
linker_load_file: Unsupported file type
So, today I updtated my system again today
On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote:
On 01/17/15 16:18, Bob Willcox wrote:
Yesterday when I upgraded my current box I encountered this failure when
attempting to load the nvidia-driver (nvidia.so):
link_elf_obj: symbol _callout_stop_safe undefined
On 17.01.15 16:18, Bob Willcox wrote:
Yesterday when I upgraded my current box I encountered this failure when
attempting to load the nvidia-driver (nvidia.so):
link_elf_obj: symbol _callout_stop_safe undefined
linker_load_file: Unsupported file type
So, today I updtated my system again today
2014-11-07 23:26 GMT+03:00 O. Hartmann ohart...@web.de:
Out of the blue the build of port x11/nvidia-driver fails - portmaster is
that sloppy
that it can not check BEFORE it kills the existent driver and fails to
install after the
deletion!
The src tree is at Revision: 274250 and with
Out of the blue the build of port x11/nvidia-driver fails - portmaster is that
sloppy
that it can not check BEFORE it kills the existent driver and fails to install
after the
deletion!
The src tree is at Revision: 274250 and with Revision r274177 the build works.
The
failure is:
===
Tonight's current breaks compiling IPFILTER. It complains that it
can't find the 'PFIL_OUT' symbol.
Dave.
--
|David Gilbert, Independent Contractor. | Two things can only be |
|Mail: [EMAIL PROTECTED
On Fri, Sep 26, 2003 at 09:56:08PM -0400, David Gilbert wrote:
Tonight's current breaks compiling IPFILTER. It complains that it
can't find the 'PFIL_OUT' symbol.
Did you read UPDATING?
Kris
pgp0.pgp
Description: PGP signature
Tonight's current breaks compiling IPFILTER. It complains that it
can't find the 'PFIL_OUT' symbol.
Read UPDATING; you need PFIL_HOOKS in your kernel config file.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
On 2003-09-26 21:56:08 (-0400), David Gilbert [EMAIL PROTECTED] wrote:
Tonight's current breaks compiling IPFILTER. It complains that it can't
find the 'PFIL_OUT' symbol.
The top entry in UPDATING insists that you stick PFIL_HOOKS in your
configuration. I've just rebuilt a kernel
Hi there, i was just wondering if anyone out there used Courier Imap on
current using authpam? ... In the last couple days i upgraded both my
current installation (from about 1 week old, to CURRENT current) and the
courier-imap port. After this, i noticed that my courier imap stopped
working... i
Hi there, i was just wondering if anyone out there used Courier Imap on
current using authpam? ... In the last couple days i upgraded both my
current installation (from about 1 week old, to CURRENT current) and the
courier-imap port. After this, i noticed that my courier imap stopped
working... i
On 2003-01-10 19:06:18 (-0500), Jeff Utter [EMAIL PROTECTED] wrote:
Hi there, i was just wondering if anyone out there used Courier Imap on
current using authpam? ...
Yeps...
In the last couple days i upgraded both my current installation (from about
1 week old, to CURRENT current) and the
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter
On 21-Sep-01 Aloha Guy wrote:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -g -nostdinc -I- -I. -I/usr/src/sys
-I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica
John Baldwin [EMAIL PROTECTED] wrote:
On 21-Sep-01 Aloha Guy wrote: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev
On 18-Sep-01 Vincent Poy wrote:
With the latest -current sources today, the kernel fails to build
after a buildworld.
Doh. Something is including sys/mutex.h or sys/sx.h w/o including sys/lock.h.
I'll fix in a bit.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
On Tue, 18 Sep 2001, John Baldwin wrote:
On 18-Sep-01 Vincent Poy wrote:
With the latest -current sources today, the kernel fails to build
after a buildworld.
Doh. Something is including sys/mutex.h or sys/sx.h w/o including sys/lock.h.
I'll fix in a bit.
Just wanted to
With the latest -current sources today, the kernel fails to build
after a buildworld.
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I.
-I/usr/src/sys
On Mon, 3 Sep 2001, Kazutaka YOKOTA wrote:
Until yesterday, I was running -CURRENT from around July 4th on my
notebook, given that I was travelling and unwilling to break my means of
giving presentations on my trip :-). Yesterday, I decided to upgrade, and
built kernel/world. The userland
Until yesterday, I was running -CURRENT from around July 4th on my
notebook, given that I was travelling and unwilling to break my means of
giving presentations on my trip :-). Yesterday, I decided to upgrade, and
built kernel/world. The userland stuff appears to work fine, but
interestingly,
Until yesterday, I was running -CURRENT from around July 4th on my
notebook, given that I was travelling and unwilling to break my means of
giving presentations on my trip :-). Yesterday, I decided to upgrade, and
built kernel/world. The userland stuff appears to work fine, but
interestingly,
I just tried to compile and got this one:
=== ld
ln -sf
/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/emultempl/astring.sed
stringify.sed
sh /usr/src/gnu/usr.bin/binutils/ld/genscripts.sh
/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld \/usr/lib\
On Sat, Jan 06, 2001 at 12:12:24AM -0500, Raymond Hicks wrote:
I have had a problem with running infobot after my recent cvsup to
current. I have heard that there is a problem with the newer perl
version.. is this a result of that? Here is error:
deepwoods# Missing braces on \N{} at
Raymond Hicks wrote:
I have had a problem with running infobot after my recent cvsup to
current. I have heard that there is a problem with the newer perl
version.. is this a result of that? Here is error:
deepwoods# Missing braces on \N{} at ./src/Irc.pl line 131, near " $b"
Missing
On Sat, Jan 06, 2001 at 12:36:12PM -0500, Thomas Stromberg wrote:
Welp, hard to help you here since there isn't any version info for the
infobot, but.. I am succesfully running a blootbot 1.0.0pre4 (infobot
derivative) in -CURRENT, and haven't seen any such problem. If there is
indeed a
I have had a problem with running infobot after my recent cvsup to
current. I have heard that there is a problem with the newer perl
version.. is this a result of that? Here is error:
deepwoods# Missing braces on \N{} at ./src/Irc.pl line 131, near " $b"
Missing braces on \N{} at ./src/Irc.pl
Vallo Kallaste wrote:
Strange, I always thought the -current list is for general issues
related to -current branch and for true kernel hackers exist -hackers.
Ok, now you know differently. No problem. :)
--
"Welcome to the desert of the real."
- Laurence Fishburne as
Hello
Just did switchover to 5.0-current and noticed that building jpeg shared
library doesn't work. Lots of X apps depend on jpeg shared library. The
fix is very small, just edit patch-ac to include freebsd5* as well.
Just FYI.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail
On Tue, Mar 14, 2000 at 01:30:32PM +0200, Vallo Kallaste wrote:
Just did switchover to 5.0-current and noticed that building jpeg shared
This belongs in [EMAIL PROTECTED] *NOT* the freebsd-current list!!!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
On Tue, Mar 14, 2000 at 08:19:24AM -0800, David O'Brien [EMAIL PROTECTED] wrote:
On Tue, Mar 14, 2000 at 01:30:32PM +0200, Vallo Kallaste wrote:
Just did switchover to 5.0-current and noticed that building jpeg shared
This belongs in [EMAIL PROTECTED] *NOT* the freebsd-current list!!!
On Tue, Mar 14, 2000 at 06:26:37PM +0200, Vallo Kallaste wrote:
This belongs in [EMAIL PROTECTED] *NOT* the freebsd-current list!!!
Yes, I did bounce the mail to freebsd-ports as well.
It's current thing also, no?
Not in the least. Specialized mailing lists exist to take the
specialized
On Tue, Mar 14, 2000 at 01:31:39PM -0800, David O'Brien [EMAIL PROTECTED] wrote:
It's current thing also, no?
Not in the least. Specialized mailing lists exist to take the
specialized traffic off the more general lists.
Plus, the fix to your problem is to fix the port. The Ports team
On Tue, 14 Mar 2000, Vallo Kallaste wrote:
Strange, I always thought the -current list is for general issues
related to -current branch ...
We really should have a new mailing list since we have an additional branch.
I'll again voice the opinion that the naming of the lists is sub-optimal.
This may or may not affect you.
Today's installworld broke passwords for me. By that, I mean that login,
xdm, su and friends gave authentication failures on all passwords for
all users that I tried. I suspect this has to do with a hashing
algorithm that isn't backward compatible.
I used
Maybe your have switched between hashing modes (DES-MD5 or MD5-DES)?
Because hashing algorithms doesn't changing without a wide notification has
been made. Please check handbook on this subj.
Maxim
Sheldon Hearn wrote:
This may or may not affect you.
Today's installworld broke passwords for
hi, there!
On Fri, 22 Jan 1999, Sheldon Hearn wrote:
This may or may not affect you.
Today's installworld broke passwords for me. By that, I mean that login,
xdm, su and friends gave authentication failures on all passwords for
all users that I tried. I suspect this has to do with a
On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote:
Maybe your have switched between hashing modes (DES-MD5 or MD5-DES)?
Possibly that's what's happened, but it certainly isn't something I did
deliberately.
Because hashing algorithms doesn't changing without a wide
notification has
-Original Message-
From: Sheldon Hearn [mailto:a...@iafrica.com]
Sent: Friday, January 22, 1999 3:17 PM
To: Maxim Sobolev
Cc: curr...@freebsd.org
Subject: Re: WARNING: Today's current breaks passwords
On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote:
Maybe your
45 matches
Mail list logo
