Nate Lawson wrote:
> /home/src/sys/gnu/ext2fs/ext2_vfsops.c: In function `ext2_unmount':
> @/sys/buf.h:281: warning: inlining failed in call to `BUF_LOCK'
"Warning: compiler failed to do what the hell it was told to do".
8-).
-- Terry
I get this:
===> i386/cdboot
===> i386/kgzldr
===> i386/libi386
===> i386/loader
"/usr/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target "loader"
ignored
cc -nostdlib -static -Ttext 0x0 -o loader.sym
/home/obj/home/src/sys/boot/i386/loader
I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
when I first launch /stand/sysinstall after the system has start, the
following message appears :
... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
block devices
I searched the list archives and find
"Andrew Tulloch" <[EMAIL PROTECTED]> writes:
> Device char-major=116 minor=196608 opened in block mode, convert to char
> mode with /dev/MAKEDEV before 2000-07-01
It has been fixed in sys/kern/vfs_subr.c:1.255. cvsup or grab the
patch and apply.
/assar
To Unsubscribe: send mail to [EMAIL PROT
In message <[EMAIL PROTECTED]>, walt writes:
>Starting today I noticed this warning at bootup:
>WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
>
>Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
--
Poul-Henning Kamp
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, walt writes:
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
Yes, fixed n
This patch should fix the sparc64 tinderbox warning/error.
--- aicasm_gram.y.orig Mon Jul 22 10:53:58 2002
+++ aicasm_gram.y Mon Jul 22 10:54:43 2002
@@ -1586,9 +1586,9 @@
}
src_mode = dst_value & 0xF;
dst_mode = (dst_value >>
Hi,
About two weeks ago(maybe after -current awk updates), awk warns when
I try to install any ports:
/usr/ports/deskutils/dailystrips# make install clean
>> dailystrips-1.0.20.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
awk: cmd. line:1: warning: escape sequence `
there may be greakage in gdb due th the commit today..
I'm waiting for my buildworld to get sround to it so I can test my fix..
julian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
there may be greakage in gdb due th the commit today..
I'm waiting for my buildworld to get sround to it so I can test my fix..
julian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
w
A couple months ago an improvement was added to the color support of ls
to use a wider variety of colors, indicated by alphabet characters
instead of numbers. While I think this is a good change, it included a
warning when users have the old style numeric flags in their LSCOLORS
variable
--- Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> I get this one on every single boot. We're not shipping the snapshot
> with that in place, right ?
>
> real memory = 268423168 (262132K bytes)
> avail memory = 257003520 (250980K bytes)
> acquiring duplicate lock of same type: "thrd_sleep"
> 1
In message <[EMAIL PROTECTED]>, Hiten Pandya w
rites:
>I haven't seen this. I built a kernel today, and I have a dual processor
>machine. Are you using any special kernel options, such as VFS_BIO_DEBUG
>or something, or am I talking nuts? :)
Well, I have. On a single CPU net-booting -current.
--- Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> >I haven't seen this. I built a kernel today, and I have a dual processor
> >machine. Are you using any special kernel options, such as VFS_BIO_DEBUG
> >or something, or am I talking nuts? :)
>
> Well, I have. On a single CPU net-booting -curr
On Sat, 16 Mar 2002 10:22:22 +0100,
Poul-Henning Kamp <[EMAIL PROTECTED]> said:
Poul-Henning> acquiring duplicate lock of same type: "thrd_sleep"
Poul-Henning> 1st @ ../../../vm/vm_map.c:2288
Poul-Henning> 2nd @ ../../../vm/vm_kern.c:172
(snip)
Poul-Henning> _vm_map_lock(c038afb4,c02f8440,ac,
On Sat, 16 Mar 2002, Poul-Henning Kamp wrote:
> I get this one on every single boot. We're not shipping the snapshot
> with that in place, right ?
I assume this is from Brian's recent VM locking commit. Currently, it's
on the list of commits to back out of the DP1 branch, assuming the issues
> The patch attached below renames the lock of the kernel_map to
> "kernel_map" once witness gets ready to run. This eliminated all of
> the lock order reversals on my PC.
I will check it out. I will check this out on my dual-processor machine.
Thanks for the patch. :-)
On Sat, 16 Mar 2002 22:56:58 +0900,
Seigo Tanimura <[EMAIL PROTECTED]> said:
Seigo> On Sat, 16 Mar 2002 10:22:22 +0100,
Seigo> Poul-Henning Kamp <[EMAIL PROTECTED]> said:
Seigo> Poul-Henning> acquiring duplicate lock of same type: "thrd_sleep"
Seigo> Poul-Henning> 1st @ ../../../vm/vm_map.c
I've seen this as well, -current from about 5 days ago, dual proc 1.4GHz
K7 A7M266D with a 13GB IBM UDMA66 drive, GENERIC kernel + hints.
On Sat, 16 Mar 2002, Hiten Pandya wrote:
> --- Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> > >I haven't seen this. I built a kernel today, and I have a du
> Although I am still getting the following lock problems when I shut
> the system down:
>
> lock order reversal
> 1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452
> 2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457
I've been seeing this since Feb 4.
Bill
To Uns
PC.
Hello Seigo,
Thanks for the patch.
That eliminated the 'duplicate lock' warning and worked fine on my UP system
with 'make -j2 buildworld'.
Thank you,
Haro
PS. I got another message that happend when I ^C'ed a buildworld earlier,
with same kernel. May be
* Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote:
>
> PS. I got another message that happend when I ^C'ed a buildworld earlier,
> with same kernel. May be it should go to Alfred Perlstein?
>
> lock order reversal
> 1st 0xc198eec0 pipe mutex @ ../../../kern/sys_pipe.c:779
> 2nd 0xc0
On Sun, 17 Mar 2002, Alfred Perlstein wrote:
> * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote:
> >
> > PS. I got another message that happend when I ^C'ed a buildworld earlier,
> > with same kernel. May be it should go to Alfred Perlstein?
> >
> > lock order reversal
> > 1st 0xc
* Robert Watson <[EMAIL PROTECTED]> [020317 09:08] wrote:
>
> On Sun, 17 Mar 2002, Alfred Perlstein wrote:
>
> > * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote:
> > >
> > > PS. I got another message that happend when I ^C'ed a buildworld earlier,
> > > with same kernel. May be it
Apparently, On Sun, Mar 17, 2002 at 09:17:22AM -0800,
Alfred Perlstein said words to the effect of;
> * Robert Watson <[EMAIL PROTECTED]> [020317 09:08] wrote:
> >
> > On Sun, 17 Mar 2002, Alfred Perlstein wrote:
> >
> > > * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote:
> >
On 17-Mar-2002 Robert Watson wrote:
>
> On Sun, 17 Mar 2002, Alfred Perlstein wrote:
>
>> * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote:
>> >
>> > PS. I got another message that happend when I ^C'ed a buildworld earlier,
>> > with same kernel. May be it should go to Alfred Perls
* John Baldwin <[EMAIL PROTECTED]> [020318 10:24] wrote:
>
> On 17-Mar-2002 Robert Watson wrote:
> >
> > On Sun, 17 Mar 2002, Alfred Perlstein wrote:
> >
> >> * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote:
> >> >
> >> > PS. I got another message that happend when I ^C'ed a buildw
On 18-Mar-2002 Alfred Perlstein wrote:
> * John Baldwin <[EMAIL PROTECTED]> [020318 10:24] wrote:
>>
>> On 17-Mar-2002 Robert Watson wrote:
>> >
>> > On Sun, 17 Mar 2002, Alfred Perlstein wrote:
>> >
>> >> * Munehiro Matsuda <[EMAIL PROTECTED]> [020317 06:36] wrote:
>> >> >
>> >> > PS. I got
There's an unchecked syslog call inside of libssp/ssp.c
/usr/src/gnu/lib/libssp/../../../contrib/gcclibs/libssp/ssp.c:137:23:
warning: format string is not a string literal (potentially insecure)
[-Wformat-security]
syslog (LOG_CRIT, msg1);
^~~~
1 wa
--- On Thu, 7/8/10, Alex Keda wrote:
From: Alex Keda
Subject: WARNING: Non-uniform processors.
To: freebsd-current@freebsd.org
Date: Thursday, July 8, 2010, 4:42 PM
When booting, I have strange message.
All work OK (processor with hyperthreading, but system seems it as 1 CPU ).
lissyara-gp
08.07.2010 22:13, Super Biscuit ?:
--- On *Thu, 7/8/10, Alex Keda //* wrote:
From: Alex Keda
Subject: WARNING: Non-uniform processors.
To: freebsd-current@freebsd.org
Date: Thursday, July 8, 2010, 4:42 PM
When booting, I have strange message.
All work OK
992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.0-CURRENT #0 r209745: Wed Jul 7 06:08:36 MSD 2010
> r...@lissyara-gp.grand-prix:/usr/obj/usr/src/sys/GENERIC i38
, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-CURRENT #0 r209745: Wed Jul 7 06:08:36 MSD 2010
r...@lissyara-gp.grand-prix:/usr/obj/usr/src/sys/GENERIC i386
WARNING
Hi all!
I got this build warning with ~recent 11-CURRENT:
--- xen-locore.o ---
/usr/data/source/git/opBSD/opBSD.git/sys/amd64/amd64/xen-locore.S:45:1:
warning: DWARF2 only supports one section per compilation unit
.section __xen_guest
^
/usr/data/source/git/opBSD/opBSD.git/sys/amd64/amd64/xen
Hi all,
when I compile bhyve, I have the following errors from clang:
pci_emul.c:750:2: error: unused typedef '__assert750'
[-Werror,-Wunused-local-typedef]
CTASSERT(sizeof(struct msicap) == 14);
pci_emul.c:776:2: error: unused typedef '__assert776'
[-Werror,-Wunused-local-typedef]
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 Kerberos
#dmesg|tail -n 2
Warning: pid 474 used static ldt allocation.
See the i386_set_ldt man page for more info
What does it means?
It was apearring for aprox. 15days.
What I have to do?
Maybe it was asked before... Could anybody refetch that message or answer? :(
--
freebsd the power to serve
Nate Lawson wrote:
I get this:
===> i386/cdboot
===> i386/kgzldr
===> i386/libi386
===> i386/loader
"/usr/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target "loader"
ignored
cc -nostdlib -static -Ttext 0x0 -o loader.sym
/home/obj/home/src/sys/bo
On Thu, Aug 07, 2003 at 02:46:23PM -0300, Daniel C. Sobral wrote:
> Nate Lawson wrote:
> >I get this:
> >===> i386/cdboot
> >===> i386/kgzldr
> >===> i386/libi386
> >===> i386/loader
> >"/usr/share/mk/bsd.prog.mk", line 38: warning: dup
Nate Lawson wrote:
I get this:
===> i386/cdboot
===> i386/kgzldr
===> i386/libi386
===> i386/loader
"/usr/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target "loader"
ignored
cc -nostdlib -static -Ttext 0x0 -o loader.sym
/home/obj/home/src/sys/bo
On Fri, Aug 08, 2003 at 11:25:49AM +1200, Andrew Turner wrote:
[...]
> I found this patch worked by removing the secound ${PROG} target if
> there was already one there.
>
> --- /usr/src/share/mk/bsd.prog.mk Mon Jun 30 06:16:26 2003
> +++ /usr/share/mk/bsd.prog.mk Mon Aug 4 17:54:22 2003
> @
On Mon, May 08, 2000 at 03:41:55PM -0500, Erik de Zeeuw wrote:
>
> I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
> when I first launch /stand/sysinstall after the system has start, the
> following message appears :
>
> ... /kernel: WARNING: run /dev/M
In message <[EMAIL PROTECTED]>, Erik de Zeeuw writes:
>
>I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
>when I first launch /stand/sysinstall after the system has start, the
>following message appears :
>
>... /kernel: WARNING: run /dev/MAKEDEV
gt; >following message appears :
> >
> >... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
> >block devices
> >
> >I searched the list archives and find some informations about this, but
> >nothing that helps me understand why I get this m
;when I first launch /stand/sysinstall after the system has start, the
>> >following message appears :
>> >
>> >... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
>> >block devices
>> >
>> >I searched the list archives
On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
> I ran MAKEDEV all, but the message still appear. The messages I found
> about this on the archives says to do a 'ls -l /dev | grep ^b', and
> to remake all devices listed, but there's no device listed when I'm
> doing the 'ls -l /dev | gr
On Tue, 9 May 2000, Sheldon Hearn wrote:
>
>
> On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
>
> > I ran MAKEDEV all, but the message still appear. The messages I found
> > about this on the archives says to do a 'ls -l /dev | grep ^b', and
> > to remake all devices listed, but there'
> >> No, I havn't tracked down the last couple of causes of this, but I
> >> will try to reproduce it as you describe it with some debugging added.
> >
> >How hard would it be to print the filename (or the device/inode) that
> >triggers the warning?
&
On Thu, 7 Feb 2002, Julian Elischer wrote:
>
> there may be greakage in gdb due th the commit today..
> I'm waiting for my buildworld to get sround to it so I can test my fix..
>
> julian
the fix I am looking at testing is:
Index: i386/kvm-fbsd.c
On Thu, 7 Feb 2002, Julian Elischer wrote:
>
> there may be greakage in gdb due th the commit today..
> I'm waiting for my buildworld to get sround to it so I can test my fix..
>
> julian
the fix I am looking at testing is:
Index: i386/kvm-fbsd.c
Doug Barton <[EMAIL PROTECTED]> writes:
> A couple months ago an improvement was added to the color support of ls
> to use a wider variety of colors, indicated by alphabet characters
> instead of numbers. While I think this is a good change, it included a
> warning when
s a good change, it included a
> > warning when users have the old style numeric flags in their LSCOLORS
> > variable. I think this is a mistake, and needlessly places another
> > barrier for users coming into -current. Since the support for the old
> > style color flags is prac
Doug Barton <[EMAIL PROTECTED]> writes:
> Mike Barcroft wrote:
> > Deprecated features should generate warnings.
>
> Ok, then let's call it "Undocumented legacy support." I agree that
> features we don't want to support anymore should generate warnings that
> encourage users to change. Howe
Mike Barcroft wrote:
> I don't have any objections to making this a supported legacy mode,
> but I think deprecated features (things we *want* to go away) should
> produce warnings.
Right-o no argument there. I'll wait for Joe to comment on the
patch then...
--
"We have known fr
On Mon, Feb 25, 2002 at 02:38:45AM -0500, Mike Barcroft wrote:
> Doug Barton <[EMAIL PROTECTED]> writes:
> > Mike Barcroft wrote:
> > > Deprecated features should generate warnings.
> >
> > Ok, then let's call it "Undocumented legacy support." I agree that
> > features we don't want to suppor
ersion include warnings.
I could understand your argument if there were A) many different
ways, or B) support for the one legacy method was complicated. But neither
of these are true. Including a warning for something that is easy to
support and costs us nothing is pointlessly pedantic. Do
s.
Just make the damn thing not work with the deprecated setup,
remove the warnings, and handle the complaints. You're going
to be handling the complaint either way.
Or get rid of the warning, and avoid the complaints, and remove
the deprecated support code later, after most of the user base
Unless there are objections in the next day or two, I'm going to
deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD. Where TUNSLMODE
prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a
4-byte network-byte-order address family.
Jordan, I believe this change should go into 4.
probably due to an issue in the latest openpam; sudo is not affected
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebs
I am getting the following while executing make toolchain TARGET=pc98:
building static roken library
ranlib libroken.a
ranlib: warning: elf_strptr failed: Invalid argument
ranlib: warning: elf_strptr failed: Invalid argument
ranlib: warning: elf_strptr failed: Invalid argument
ranlib: warning
On Oct 21, 2013, at 05:47, Sean Bruno wrote:
> There's an unchecked syslog call inside of libssp/ssp.c
>
>
> /usr/src/gnu/lib/libssp/../../../contrib/gcclibs/libssp/ssp.c:137:23:
> warning: format string is not a string literal (potentially insecure)
> [-Wforma
On Mon, 2013-10-21 at 08:44 +0200, Dimitry Andric wrote:
> On Oct 21, 2013, at 05:47, Sean Bruno wrote:
> > There's an unchecked syslog call inside of libssp/ssp.c
> >
> >
> > /usr/src/gnu/lib/libssp/../../../contrib/gcclibs/libssp/ssp.c:137:23:
> >
Hi
/usr/src/sys/netinet/ip_output.c: In function 'ip_output':
/usr/src/sys/netinet/ip_output.c:625: warning: cast discards qualifiers from
pointer target type
/usr/src/sys/netinet/ip_output.c:659: warning: cast discards qualifiers from
pointer target type
*** [ip_output.o] Error cod
On 22 Jun 2015, at 22:53, Oliver Pinter wrote:
>
> I got this build warning with ~recent 11-CURRENT:
>
> --- xen-locore.o ---
> /usr/data/source/git/opBSD/opBSD.git/sys/amd64/amd64/xen-locore.S:45:1:
> warning: DWARF2 only supports one section per compilation unit
>
Better to just replace CTASSERT() with _Static_assert() while you're here.
Best,
Conrad
On Thu, Aug 13, 2015 at 5:05 AM, Stefano Garzarella
wrote:
> Hi all,
> when I compile bhyve, I have the following errors from clang:
> pci_emul.c:750:2: error: unused typedef '__assert750'
> [-Werror,-Wunused
Conrad Meyer wrote this message on Thu, Aug 13, 2015 at 08:12 -0700:
> Better to just replace CTASSERT() with _Static_assert() while you're here.
And make sure that sys/cdefs.h is included for compatibility w/ pre-C11
compilers...
> On Thu, Aug 13, 2015 at 5:05 AM, Stefano Garzarella
> wrote:
>
Hi!
I'm about to start merging in changes from Andriy that change how the
transmit path in net80211 works. Right now it's a holdover from the
old if_start style mechanism - a call to if_start() always consumed
the mbuf, even upon an error. He's changing it so upon error the
caller returns without
I got the error when compiling GENERIC kernel with address sanitizer
/bin/sh:
--- vers.c ---
MAKE=make sh /usr/home/howardsu/freebsd/sys/conf/newvers.sh
GENERIC=
==4132==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7
I did a buildworld with llvm39. Unsurprisingly I had to pass NO_WERROR= as the
llvm has added additional warnings since 3.8.
https://gist.github.com/mattmacy/5f0c994b7587a10e3f58e7fd9fc1dd01
The most prevalent seems to be:
jemalloc_nstime.c:120:7: warning: macro expansion producing 'de
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
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 ha
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 ha
> -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 19
Current from approximately 0500 BST on 16th September is giving me
errors like this from boot:
ad0: WARNING - WRITE_MUL write data underrun 8192>2048
ad0: WARNING - WRITE_MUL write data underrun 8192>6144
ad0: WARNING - WRITE_MUL write data underrun 8192>4096
ad0: WARNING - WRITE_MUL w
Pau Rodriguez wrote:
> #dmesg|tail -n 2
> Warning: pid 474 used static ldt allocation.
> See the i386_set_ldt man page for more info
>
> What does it means?
>
> It was apearring for aprox. 15days.
>
> What I have to do?
>
> Maybe it was asked before... Coul
I get several of these messages with a recent -current:
Oct 16 17:38:35 cicely6 kernel: dummynet: warning, refcnt now 0, decreasing
Oct 16 17:38:36 cicely6 last message repeated 2 times
Oct 16 17:38:36 cicely6 kernel: dummynet: warning, refcnt now -1, decreasing
Oct 16 17:38:36 cicely6 kernel
Andrew Turner wrote:
>
> Name: find_dependcy
>find_dependcyType: application/x-java-applet
> Encoding: base64
This posting is a Java applet with inline disposition. Do n
Hi
Just did the following:
dd if=/dev/zero of=/dev/da1 bs=1k count=512 #remove old stuff
fdisk -I da1#cover the entire disk with one da1s1 slice
fdisk da1 #check what's put there
disklabel -rw da1s1 auto#install virgin disklabel
disklabel -e da1s1 #add partition e:, copi
If you reinstalled libc with the previous version of ttyname.c your
sshd will likely get confused and refuse access.
Apologies...
Poul-Henning
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp
writes:
>phk 2003/06/21 01:16:12 PDT
>
> FreeBSD src repository
>
> Modified files:
>l
num and libh will
need this RSN.
Remove a pointless warning in the root device locating code.
Remove the "wd" compatibility name from the "ad" driver.
WARNING: If you have not updated to use /dev/wd* in your /etc/fstab
and modern bootblocks, it would be a very
Hi,
I'm seeing lots of:
ed0: warning - receiver ring buffer overrun
This box is building the world with sources via NFS. What gives?
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]fax (0118) 989 4254
To Unsubscribe: send mail to [
How are you supposed to disable -Werror in kernel builds? Setting
NO_WERROR in the env or passing it to 'make buildkernel' via -D
doesn't work; neither does putting -Wno-error in COPTFLAGS. I get the
following fatal warning when compiling a recent alpha 5.0 kernel under
4.x:
>>> "tl" == "Terry Lambert" wrote:
tl> FWIW: tail-call optimization is when I have a function
tl> that, as it's last thing (perhaps after reordering by
tl> the compiler, as well) calls another function, such
tl> that the return value of the other function is its
tl> return value.
See also:
D
I have uncovered some odd behavior on my machine here using netgraph
since the last changes..
I'm trying to find the problem but I need sleep...
If you have used he latest netgraph code, let me know what modules
you are using and how so I can try narrow my search..
thanks..
Julian
--
__
> Jordan, I believe this change should go into 4.0-RELEASE rather than
> happening afterwards so that we have a minimal number of people
> (hopefully none) using TUNSLMODE. TUNSLMODE was never MFC'd.
Do it. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd
Brian Somers <[EMAIL PROTECTED]> writes:
> Unless there are objections in the next day or two, I'm going to
> deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD. Where TUNSLMODE
> prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a
> 4-byte network-byte-order address family.
> Brian Somers <[EMAIL PROTECTED]> writes:
> > Unless there are objections in the next day or two, I'm going to
> > deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD. Where TUNSLMODE
> > prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a
> > 4-byte network-byte-order addre
Dag-Erling Smørgrav writes:
> probably due to an issue in the latest openpam; sudo is not affected
should be fixed now.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
On 05/26/2012 16:36, Dag-Erling Smørgrav wrote:
> Dag-Erling Smørgrav writes:
>> probably due to an issue in the latest openpam; sudo is not affected
>
> should be fixed now.
Confirmed, thanks. :)
--
This .signature sanitized for your protection
__
On Sat, Oct 20, 2012 at 3:26 AM, Andriy Gapon wrote:
>
> I am getting the following while executing make toolchain TARGET=pc98:
> building static roken library
> ranlib libroken.a
> ranlib: warning: elf_strptr failed: Invalid argument
> ranlib: warning: elf_strptr failed
on 20/10/2012 20:39 Garrett Cooper said the following:
> On Sat, Oct 20, 2012 at 3:26 AM, Andriy Gapon wrote:
[snip]
>> main.o: In function `usage':
>> main.c:(.text+0x17): undefined reference to `arg_printusage'
>> main.o: In function `main':
>> main.c:(.text+0x77): undefined reference to `getarg
Today I saw a spurious witness warning for "acquiring duplicate lock of
same type". The root cause is that when running mtx_destroy on a spinlock
that is held by the current thread, mtx_destroy calls spinlock_exit()
before calling WITNESS_UNLOCK, which opens up a window in which the
I'm getting an strange warning whem compiling with clang (from base) on RC1.
This warning doesn't appear with 8.X and clang from ports.
The warning is strange because ntohs is not int:
uint16_t
ntohs(uint16_t netshort);
Any insight would be appreciated, thanks in a
I'm using 14.0-current on old DELL xps12 notebook.
Xconsole on it is fillfulled the 'ACPI Warning: Firmware issue:
Excessive sleep time (0x0014 ms > 10 ms) in ACPI
Control Method (20220331/exsystem-347)' messages and I'm failling
to see other important messages.
Beware, a recent change has moved zfs tools internal libraries to the wrong
location and this can cause machines to be unbootable. /sbin/zfs uses the
libraries from /lib, which are now going stale and may have undefined symbols.
installworld is incorrectly installing them in /usr/lib. This ha
I have /etc/src.conf:
WITH_DEBUG_FILES=1
WITH_CTF=1
/etc/make.conf:
CFLAGS=-fno-omit-frame-pointer
WITH_CTF=1
WITH_DEBUG=yes
Not sure which of those is relevant (or even correct), but I seem to
get debuginfo in /usr/lib/debug/.debug.
Best,
Conrad
On Thu, Feb 25, 2016 at 7:21 PM, Howard Su wrot
On 26 Feb 2016, at 04:21, Howard Su wrote:
>
> I got the error when compiling GENERIC kernel with address sanitizer
> /bin/sh:
> --- vers.c ---
> MAKE=make sh /usr/home/howardsu/freebsd/sys/conf/newvers.sh
> GENERIC=
> ==4132==ERROR:
On Fri, Feb 26, 2016 at 06:21:20PM +0100, Dimitry Andric wrote:
> On 26 Feb 2016, at 04:21, Howard Su wrote:
> > I got the error when compiling GENERIC kernel with address sanitizer
> > /bin/sh:
> > --- vers.c ---
> > MAKE=make sh /usr/home/howardsu/freebsd/sys/conf/newvers.sh
> > GENERIC
On 28 Feb 2016, at 23:16, Jilles Tjoelker wrote:
>
> On Fri, Feb 26, 2016 at 06:21:20PM +0100, Dimitry Andric wrote:
...
>> This frame has 3 object(s):
>>[16, 20) 'bqlist'
>>[32, 128) 'state_static' <== Memory access at offset 32 is inside this
>> variable
>>[160, 170) 'buf'
...
>>
On recent CURRENT, the source tree /usr/src seems to have issues on some of my
boxes and whenever I issue "make build", the message:
make warning: �: No such file or directory.
pops up. "svn st" doesn't reveal anything wrong.
My locale settings are:
LANG=
L
101 - 200 of 531 matches
Mail list logo
