I have an error for a week and cannot make buildworld.
Where can I find panic other than real panic?
=== sbin/gbde
: : : :
cc -O -pipe -mcpu=pentiumpro -I/usr/src/sbin/gbde/../../sys -Werror -Wall
-Wno-format-y2k -Wno-uninitialized -c template.c
cc1: warnings being treated as errors
On Sat, 26 Oct 2002, John De Boskey wrote:
I've (re)scanned my -current folder for issues related
to the following but didn't see a good match. Pointing
out my blindness is allowed if this was discussed...
It's just another intentional incompatibility in GEOM.
I have a system onto
Bakul Shah wrote:
Thank you for explicating the security argument! I'll also
point out that hardwiring module names makes it harder to
experiment with replacement modules (i.e. I may want to
develop if_super_duper_ppp).
Actually, this isn't an issue (I'm assuming that you want it to
be named
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
Terry Lambert wrote:
Brooks Davis wrote:
This isn't going to have an effect on the ability to use kernel ppp for
other things. The tty orientation of pppd and the outdated, unmodular
design on ppp(4) have taken care of that. This patch gives people
the functionality they want (pppd just
According to Ollivier Robert:
During its reading of all fonts available, it get a segv...
Any idea ?
Found that at least one of the Type1 fonts I had (installed by XFree86) does
bad things to freetype and it was getting a segv.
The interesting point is that it happens even if you have disabled
Yamada Ken Takeshi wrote:
I have an error for a week and cannot make buildworld.
Where can I find panic other than real panic?
=== sbin/gbde
: : : :
cc -O -pipe -mcpu=pentiumpro -I/usr/src/sbin/gbde/../../sys -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c template.c
cc1: warnings
Thank you for your prompt reply.
From: walt [EMAIL PROTECTED]
: ::
I can't see how line 222 includes an implicit declaration of 'panic'.
Is your file different?
I do not know why compiler says line 222, but it is
below 222 and my latest source says;
# cat
On Sat, Oct 26, 2002 at 10:13:02PM +0900, Yamada Ken Takeshi wrote:
# cat rijndael/rijndael-api-fst.c
::::
switch (cipher-mode) {
case MODE_ECB:
for (i = numBlocks; i 0; i--) {
rijndaelEncrypt(input,
Thank you!
From: Craig Rodrigues [EMAIL PROTECTED]
You don't have the latest sources. Did you use cvsup it
update your sources? If you used cvsup, then you
need to add src-sys-crypto to your cvsup file.
It was my cvsup prroblem. Fixed!!
msg45379/pgp0.pgp
Description: PGP
This is all very true for 4.7, but what about earlier versions.
I compiled fsck using 4.7 srcs, includes and hierarchy with 4.0
libraries and tools, so that I could have an fsck I could use with my
4.0 CDROM (the latest one I have, unfortunately) to repair any changes
made by my CURRENT
With current from yesterday, I get the following error when trying to
burn a cd. I haven't burned one for probably a month or maybe more.
If I remove the -s, the results are the same.
Does anyone have a suggestion, fix or work around?
# burncd -f /dev/acd0c -s 1 data cd0.raw20021022 fixate
Hello,
With sources few minutes old (as well as with sources approx. 3h old):
=== gnu/usr.bin/groff/tmac
/usr/src/gnu/usr.bin/groff/tmac/Makefile, line 2: warning: duplicate
script for target -s ignored
[... 12 times repeated]
make: don't know how to make doc-common-s. Stop
*** Error code 2
jwd A new 5.0-20021025-CURRENT snapshot is available
jwd via anonymous ftp at usw2.freebsd.org:
Wonderful! Is it a time to switch back 'current.FreeBSD.org' name to
that machine?
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in
With sources few minutes old (as well as with sources approx. 3h old):
=== gnu/usr.bin/groff/tmac
/usr/src/gnu/usr.bin/groff/tmac/Makefile, line 2: warning: duplicate
script for target -s ignored
[... 12 times repeated]
make: don't know how to make doc-common-s. Stop
*** Error code 2
attila only problem with snapshot.jp at this point is that
attila release does not build: md0 problems
That should be a local problem IMO, and I believe it was fixed several
hours before (ya, sorry for being lazy.)
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL
- Daniel Flickinger's Original Message -
Sent: Sun, 27 Oct 2002 01:03:43 +0900 by MAR
+ jwd A new 5.0-20021025-CURRENT snapshot is available
+ jwd via anonymous ftp at usw2.freebsd.org:
+
+ Wonderful! Is it a time to switch back 'current.FreeBSD.org' name to
+ that machine?
On Sat, 26 Oct 2002, Ollivier Robert wrote:
According to Ollivier Robert:
During its reading of all fonts available, it get a segv...
Any idea ?
Found that at least one of the Type1 fonts I had (installed by XFree86) does
bad things to freetype and it was getting a segv.
The interesting
Peter Wemm wrote:
'make installworld' without ... a new kernel would be rather messy.
... a reminder of the sequence is probably in order:
buildworld
buildkernel
installkernel
reboot
installworld
reboot
This _does_not_work_ because 'installkernel' does
not update the bootblocks. It
Quoting Tim Kientzle [EMAIL PROTECTED]:
| Peter Wemm wrote:
|
| 'make installworld' without ... a new kernel would be rather messy.
|
| ... a reminder of the sequence is probably in order:
| buildworld
| buildkernel
| installkernel
| reboot
| installworld
| reboot
|
On Sat, Oct 26, 2002 at 11:42:02AM -0700, Tim Kientzle wrote:
Peter Wemm wrote:
'make installworld' without ... a new kernel would be rather messy.
... a reminder of the sequence is probably in order:
buildworld
buildkernel
installkernel
reboot
installworld
reboot
This
Hi,
I updated my kernel now just like told in the last HEADSUP and hesitate
to do a 'make installworld' as also mentioned there...
Now, during boot 'ipfw' complaines:
ipfw: size mismatch (have 64 want 1064)
ipfw: size mismatch (have 52 want 40)
ipfw: size mismatch (have 52 want 40)
This
Matthias Schuendehuette wrote:
Hi,
I updated my kernel now just like told in the last HEADSUP and hesitate
to do a 'make installworld' as also mentioned there...
Now, during boot 'ipfw' complaines:
ipfw: size mismatch (have 64 want 1064)
ipfw: size mismatch (have 52 want 40)
ipfw:
Wesley Morgan wrote:
Im my many hours of playing with fonts, I seem to recall that the Freetype
/ XFT module is perfectly capable of rendering the Type1 fonts. Make sure
you take the PATH out of your XftConfig in addition to the XF86Config
Some fonts have characters with a zero width, and you
On Saturday 26 October 2002 21:48, you wrote:
No, the problem is that you need to installworld to have an updated
ipfw(8) binary.
Confirmed! Thanks a lot!
PS: So the HEADSUP-strategy has its limitations... ;-)
--
Ciao/BSD - Matthias
Matthias Schuendehuette msch [at] snafu.de, Berlin
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
On Sat, Oct 26, 2002 at 10:04:44PM +0200, Matthias Schuendehuette wrote:
On Saturday 26 October 2002 21:48, you wrote:
No, the problem is that you need to installworld to have an updated
ipfw(8) binary.
Confirmed! Thanks a lot!
PS: So the HEADSUP-strategy has its limitations... ;-)
On Saturday 26 October 2002 22:17, you wrote:
You did not reboot to single user mode to installworld.
No need to run ipfw with the new kernel before installworld.
-current readers are expected to know that.
Right!
What I meant was:
For this reason, you probably want to delay an installworld
Thus spake M. Warner Losh [EMAIL PROTECTED]:
: No. You should assume that for i386, at least, that long double will
: have the right LDBL_ constants. I've had them in my local tree for
: about 3 months now and just haven't found the time to commit to
: -current. I'll find the time right
In message: [EMAIL PROTECTED]
David Schultz [EMAIL PROTECTED] writes:
: Thus spake M. Warner Losh [EMAIL PROTECTED]:
: : No. You should assume that for i386, at least, that long double will
: : have the right LDBL_ constants. I've had them in my local tree for
: : about 3 months
Thus spake Tim Kientzle [EMAIL PROTECTED]:
Thus spake Lucky Green [EMAIL PROTECTED]:
... remove ssh1 fallback from the default ...
David Schultz [EMAIL PROTECTED] wrote:
Removing SSH 1 ... is going to break compatibility ...
POLA: before breaking compatibility, warn people.
It's simple
On Tue, 22 Oct 2002 04:25:23 +0200, you wrote:
Is it possible, or do I need to use a more recent installation to be able to
build -CURRENT?
it was possible for me, but i had to go through a lot of hassles
installing -CURRENT from within -STABLE.
i used the DESTDIR-switch to install everything
Lars Eggert wrote:
Hi,
just got this when trying to umount a media from an USB CF reader:
/usr/src/sys/kern/kern_synch.c:146: sleeping with mountlist locked
from /usr/src/sys/kern/vfs_mount.c:1321. I have a core dump, but it's of
the second panic.
Could you tell us what's the revision
On Sat, 26 Oct 2002, Dave Evans wrote:
This is all very true for 4.7, but what about earlier versions.
I compiled fsck using 4.7 srcs, includes and hierarchy with 4.0
libraries and tools, so that I could have an fsck I could use with my
4.0 CDROM (the latest one I have, unfortunately)
On Sat, 26 Oct 2002 [EMAIL PROTECTED] wrote:
With current from yesterday, I get the following error when trying to
burn a cd. I haven't burned one for probably a month or maybe more.
If I remove the -s, the results are the same.
Does anyone have a suggestion, fix or work around?
#
Maxime Henrion wrote:
Lars Eggert wrote:
/usr/src/sys/kern/kern_synch.c:146: sleeping with mountlist locked
from /usr/src/sys/kern/vfs_mount.c:1321. I have a core dump, but it's of
the second panic.
Could you tell us what's the revision of your vfs_mount.c file ?
Just did a
* De: Matthias Schuendehuette [EMAIL PROTECTED] [ Data: 2002-10-26 ]
[ Subjecte: Re: Actual probs with 'ipfw' ]
On Saturday 26 October 2002 22:17, you wrote:
You did not reboot to single user mode to installworld.
No need to run ipfw with the new kernel before installworld.
-current
On Sat, 26 Oct 2002, Nate Lawson wrote:
On Sat, 26 Oct 2002 [EMAIL PROTECTED] wrote:
With current from yesterday, I get the following error when trying to
burn a cd. I haven't burned one for probably a month or maybe more.
If I remove the -s, the results are the same.
Does anyone have
what would it take to allow burncd to work on SCSI devices.?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I'm about to do a make world
so it's possible a gcc change I've not yet picked up
may fix this, but in the meanwhile, I can't compile a kernel
because of:
ref3# make
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
You need a recompile of GCC. This change was made to accomodate the POSIX
%z by renaming the DDB %z to %y, and GCC had to be made aware.
* De: Julian Elischer [EMAIL PROTECTED] [ Data: 2002-10-26 ]
[ Subjecte: possible kernel build breakage. ]
I'm about to do a make world
so it's
On Sat, 26 Oct 2002, Julian Elischer wrote:
what would it take to allow burncd to work on SCSI devices.?
You got it backwards -- is atapicam complete enough to work reliably with
cdrecord? There's no reason for us to replicate a more feature-complete
port in our src tree.
-Nate
To
Quoting Nate Lawson [EMAIL PROTECTED]:
| On Sat, 26 Oct 2002 [EMAIL PROTECTED] wrote:
| With current from yesterday, I get the following error when trying to
| burn a cd. I haven't burned one for probably a month or maybe more.
| If I remove the -s, the results are the same.
|
| Does
Quoting Nate Lawson [EMAIL PROTECTED]:
SNAP
|
| I checked again and my commit had missed the burncd speed conversion. I
| just committed it -- rev 1.28 burncd.c. Sorry about this. CVSUP, rebuild
| burncd, and let me know if there are further problems.
|
Thanks, Nate. Please ignore my
On Sat, Oct 26, 2002 at 05:08:39PM -0700, Juli Mallett wrote:
You need a recompile of GCC. This change was made to accomodate the POSIX
%z by renaming the DDB %z to %y, and GCC had to be made aware.
The recommended upgrade procedure (buildworld, followed by buildkernel
etc) should
I have disk shared between FreeBSD and M$ Win, two slices, and got
incorrect disklabel with GEOM kernel. Namely cylinders and
sectors/unit fields are from _whole_ disk, not from just requested
slice.
It invalidates previously correct 'c' BSD partition too, 'disklabel'
outputs several
If you delete from fstype on in a disklabel line and have it try to write
it, its internal parsing routines go boom. I've fixed it locally, and
would like to commit my delta.
%%%
Index: disklabel.c
===
RCS file:
Over the past few weeks I've had continuous problems booting
my 5-current system with an SMP kernel. Immediately after
the system has booted and the login screen displays the machine
panics. The motherboard is an Abit BP6. Below is the information
provided when it locks up. Based on the kernel
On Sat, 26 Oct 2002, Julian Elischer wrote:
what would it take to allow burncd to work on SCSI devices.?
You got it backwards -- is atapicam complete enough to work reliably with
cdrecord?
I don't see why it shouldn't work on -CURRENT.
It works fine for me on -STABLE, for oh, months and
cdrecord doesn't do DVDs and jorg Schiller is holding back on DVD mods
so he can sell that version..
DVD capable cdrecord is called cdrecord-PRO
and costs $100.
if he commands from burncd could be piped into a SCSI pipe,
then that would probably work...
I have an ATAPI dvd writer on a
This could do with a note in UPDATING, No?
On Sat, 26 Oct 2002, Juli Mallett wrote:
You need a recompile of GCC. This change was made to accomodate the POSIX
%z by renaming the DDB %z to %y, and GCC had to be made aware.
* De: Julian Elischer [EMAIL PROTECTED] [ Data: 2002-10-26 ]
In message: [EMAIL PROTECTED]
Tim Kientzle [EMAIL PROTECTED] writes:
: Peter Wemm wrote:
:
: 'make installworld' without ... a new kernel would be rather messy.
:
: ... a reminder of the sequence is probably in order:
: buildworld
: buildkernel
: installkernel
: reboot
:
52 matches
Mail list logo
