initialized incorrectly.
The last few commits to machdep.c bother me, rev 1.539 in particular.
If you are in a position to be able to quickly test it, it would be great
to know if backing out the last few changes fixes this, and which change in
particular.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED
:-).
I suspect it might be time to give up and do the alternative sigtrap and
sigreturn.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED
about trying to run vinum on partition schemes that
do not even *have* disklabels.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Terry Lambert wrote:
Emiel Kollof wrote:
* Peter Wemm ([EMAIL PROTECTED]) wrote:
vinum is so much unbelievable stuff in it. Consider this stuff:
sys/dev/vinum/vinumio.c:
[ ... ]
This crud has *got* to be taken out and shot, then reworked to do it
properly.
Amen
Greg 'groggy' Lehey wrote:
On Friday, 4 October 2002 at 16:03:24 -0700, Peter Wemm wrote:
Terry Lambert wrote:
Emiel Kollof wrote:
* Peter Wemm ([EMAIL PROTECTED]) wrote:
vinum is so much unbelievable stuff in it. Consider this stuff:
sys/dev/vinum/vinumio.c
add a new sigreturn syscall each time we
significantly break the sigreturn ABI (as in this case) and applications
will be able to use the correct one. Paired with a new sigaction syscall
which would specify the new context format we can then be future proof.
Cheers,
-Peter
--
Peter Wemm - [EMAIL
significant regressions to be fixed. The last thing we need during the
'please stabilize 5.0' drive is newly added problems. If other folks are
seeing new ones, please report them here (not to me, I already get too much
email :-]).
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED
is telling you the wrong line. The problem is here:
int nsegments;
vs:
/*nsegments*/BUS_SPACE_UNRESTRICTED,
note that:
bus.h:#define BUS_SPACE_UNRESTRICTED(~0UL)
0x will not fit in an int.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED
that clears libc_r.
This machine has not had an X server crash in over 6 months - until that
one.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED
, this is going to suck. There are thousands and thousands of third
party scripts that use +n syntax.
I am most unhappy with this change. :-(
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
Garrett Wollman wrote:
On Tue, 24 Sep 2002 13:30:11 -0700, Peter Wemm [EMAIL PROTECTED] said:
Oh man, this is going to suck. There are thousands and thousands of third
party scripts that use +n syntax.
I am most unhappy with this change. :-(
The time to complain about it was back
Andrey A. Chernov wrote:
On Tue, Sep 24, 2002 at 13:30:11 -0700, Peter Wemm wrote:
Oh man, this is going to suck. There are thousands and thousands of third
party scripts that use +n syntax.
I am most unhappy with this change. :-(
It will be possible to have both variants, but +N
;
+}
Try something like this:
#include stdlib.h
#include unistd.h
int
posix2_version(void)
{
if (getenv(POSIX_ME_HARDER) || getenv(POSIXLY_CORRECT))
return _POSIX2_VERSION;
else
return 0;
}
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED
of another
change that broke even our own world builds.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
Garrett Wollman wrote:
On Tue, 24 Sep 2002 14:26:43 -0700, Peter Wemm [EMAIL PROTECTED] said:
Closed payware standards do not count as 'fair warning'. I still have
never been able to see a posix standard.
Go to a library. Or go to http://www.opengroup.org/ and register for
free
once we get to the actual
compile. The next run should be interesting. :-]
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
://people.freebsd.org/~mbr/crashes/vmcore.3.txt
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go
weeks.
Note: kernel support for executing a.out binaries remains in the base
system. Be sure to either specify 'options COMPAT_AOUT', or do a
'kldload aout' to load it at runtime if you forgot to include it.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All
Manfred Antar wrote:
At 12:23 AM 9/7/2002 -0700, Terry Lambert wrote:
Peter Wemm wrote:
You will need to either add:
options COMPAT_AOUT
to your kernel config when you next rebuild, or do a 'kldload aout'
when you want to run an old a.out binary.
Is this going to be turned
You will need to either add:
options COMPAT_AOUT
to your kernel config when you next rebuild, or do a 'kldload aout'
when you want to run an old a.out binary.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go
doesn't support it.
As far as I understood it, the 'dont mix 3dnow and SSE' thing was exactly
that.. do not mix the instructions together in the same application
stream.. Apparently the instruction decoder wasn't tuned for both in the
same data stream.
Cheers,
-Peter
--
Peter Wemm - [EMAIL
completely removed..
there are always other ways to do that
(e.g. boot 2.2.6 in a vmware machine or run them in a
chroot)
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe
/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1/../cc_int/libcc_int.a(i386
.o): In function `ix86_expand_int_movcc':
i386.o(.text+0x7bf5): undefined reference to `gen_int_mode'
*** Error code 1
Stop in /usr/src/gnu/usr.bin/cc/cc1.
*** Error code 1
Cheers,
-Peter
--
Peter Wemm
(0x120108000)
36947 foo RET break 0
36947 foo CALL break(0x12010c000)
36947 foo RET break 0
How strange..
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send
-1 src/sys/compat/svr4/svr4_resource.c
1.121 +33 -10src/sys/kern/imgact_elf.c
Probably the later one, the timing is about right.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
Bernd Walter wrote:
On Tue, Sep 03, 2002 at 09:01:07AM -0700, Peter Wemm wrote:
Alexander Kabaev wrote:
On Tue, 3 Sep 2002 16:56:52 +0200
Bernd Walter [EMAIL PROTECTED] wrote:
Do you think this is the same reason?
Yes.
Folks, it is a *kernel* problem
don't think we can do this (the last section), it is quite legal to have
more than one non-text PT_LOAD segment. if the last one was very small,
we'd end up with an artificially low 'data_size' which would make for
interesting RLIMIT_DATA enforcement.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED
be patient.
Please respond immediately if you feel that I need to hold the import
for some reason.
Cool! Thank you for doing hard work, Alexander. BTW, does it mean that
we just got a fresh new gcc maintainer?
I just hope we didn't scare him too much :-)
Cheers,
-Peter
--
Peter Wemm
, but that is no big deal.
gcc has grown a native -funderscores option to help with the source
C vs asm symbol compatability problems.
But quite frankly, I'd rather have a binutils-aout and gcc-aout port if we
really have to have a.out support still.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL
changes.
Oh indeed, it is far from simple. But as a bonus our compiler configuration
for i386 would be a lot closer to what the FSF compiler config looks like.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go
trying to build itself?
Buildworld completes fine on panther, the only FreeBSD sparc64 machine I
have access to.
This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c
is out of sync on the builder machine. This builds fine on
panther.freebsd.org.
Cheers,
-Peter
--
Peter Wemm
with a known broken prerelease compiler?
Would you rather that we changed from 3.1-prerelease to 3.1.1-release?
gcc-3.2 *is* 'gcc-3.1.1 + ABI bugfix'. They renamed the 3.1 branch to 3.2.
All future 3.1.x releases will be called 3.2.x.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED
want it very badly too.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
with better and chalk it up as a learning experience.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL
+ KERNBASE);
+ return (void *)(pa + offset + KERNBASE);
I've committed this as 1.356. If it doesn't solve it, then go ahead and back
out both 1.352 and 1.356.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go
on RELENG_4, but the support all got
MFC'ed. Several release candidates used cdboot for better testing exposure.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL
? A vm86disk driver
would solve a number of problems. If you do one that is respectable, I'll
commit it for you myself.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send
Move your old /usr/include/g++ out of the way before extracting it
and save a copy of your /usr/lib/libstdc++* files as well.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send
Yann Berthier wrote:
On Mon, 22 Jul 2002, Peter Wemm wrote:
It might be just me because I swapped an ISA 'si' card for a PCI version, b
ut
the problems I've been seeing are pretty spectacular. I'm regularly seeing
the following panics:
- selwakeup() taking fatal traps (always
anybody else seen this sort of thing today?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to the
release scripts so that the agp device was filtered out of the BOOTMFS
kernel image. (A quick grep -r for BOOTMFS should show up the sed scripts
that turn GENERIC into BOOTMFS in src/release).
The 'agp' device isn't likely to hurt anything, is it?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED
Peter Wemm wrote:
Peter Wemm wrote:
This is mostly a FYI because I do not expect major problems this time.
I have been extensively testing it in a handful of configurations.
As murphy would dictate, something fishy is going on. In the last 12 hours
or so (I had a long sleep), I've
of this change
that I thought were working but I didn't want to risk them yet.
If I've broken something new, please yell. I must confess that I have not
tried to use vm86 doscmd or anything perverse like that.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All
Peter Wemm wrote:
This is mostly a FYI because I do not expect major problems this time.
I have been extensively testing it in a handful of configurations.
As murphy would dictate, something fishy is going on. In the last 12 hours
or so (I had a long sleep), I've started getting apparent
]
with unsubscribe freebsd-current in the body of the message
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
do finer grained shootdowns.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Peter Wemm wrote:
John Baldwin wrote:
On 11-Jul-2002 Matthew Dillon wrote:
Here is my proposed fix for the page-zeroing problem w/ SMP. It
is untested (I'm about to test it)... I'm looking for comments on
the concept. If the comments are positive and my testing
Peter Wemm wrote:
John Baldwin wrote:
On 08-Jul-2002 Peter Wemm wrote:
A few months ago, I had a bit of a disaster with some pmap optimizations.
After committing, all hell broke loose. It was backed out completely.
I finally found the problem (diff cleaned up to highlight
disruptive than slashing through userland and
fixing something that is already perfectly correct and legal.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL
)
{
printf(NULL);
err(1, NULL);
return 0;
}
peter@panther[4:22pm]~-106 cc -O -Wformat -c foo.c
peter@panther[4:22pm]~-107
ie: it looks like it is completely disabled. Maybe the sparc64 tinderbox
host is simply out of sync with -current?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED
on having
/usr/X11R6/bin/glxinfo installed, but I would wager that you will not miss
it.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED
= vtopte(tmpva);
*pte = pa | PG_RW | PG_V | pgeflag;
size -= PAGE_SIZE;
tmpva += PAGE_SIZE;
- pa += PAGE_SIZE;
}
invltlb();
Excuse me while I go outside and shoot myself.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED
John Baldwin wrote:
On 08-Jul-2002 Peter Wemm wrote:
A few months ago, I had a bit of a disaster with some pmap optimizations.
After committing, all hell broke loose. It was backed out completely.
I finally found the problem (diff cleaned up to highlight the problem
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
blocks, 0.0% fragmentation)
# halt
Notice how it completely exited after da0f and printing WAS MODIFIED ?
Not to mention how we cannot shut down cleanly. :-(
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars
equivalent? I seem to recall that current.freebsd.org
is referenced in sysinstall. Will just a CNAME work?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL
. This is responsible for things like
vipw failing after ^Z/fg (editor=vi), mergemaster failing on ^Z/fg etc.
(it was mergemaster that tipped me off on this.)
Applications that use interval timers would be suffering from this pretty
badly.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL
which
puts me into the USB danger-zone enough as it is.. but what happens when
this bug is triggered?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED
having fun now, I thought I'd mention this one too.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
(e.g. to load into VMWare or via netboot).
Uhh, Terry.. This has absolutely nothing to do with the problem.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL
,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
reports from you, always in a different
place?
I was wondering about that too... Admins, any signs of faulty RAM or
cooling problems in ref5?
The single biggest problem seemed to be NFS, but you're not using that
anymore are you?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED
Dag-Erling Smorgrav wrote:
Peter Wemm [EMAIL PROTECTED] writes:
If you want final commit approval/objections, you really need to either
include or go to developers@ instead since they're the ones dealing with
actual commit process.
s/developers/arch/
I wasn't clear with this comment
Dag-Erling Smorgrav wrote:
Peter Wemm [EMAIL PROTECTED] writes:
But he said he was asking for permission to commit it (Seeking OK to
commit KSE MIII-again), so he should be talking with other committers.
I guess I just don't see why he needs our permission, as long as he's
given us
-current in the body of the message
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Alfred Perlstein wrote:
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
Wilko Bulte wrote:
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
gcc-3.1 appears to have broken
#pragma weak foo = bar
is that David and I configured something
differently or ./configure found something different on our systems when
generating config.h for the library. I'll go back over this again.
I'm pretty sure we had different locale settings, but I'm a little suprised
about the math differences.
Cheers,
-Peter
--
Peter
commit process.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
the long double versions and others that do
not.
To be sure we're all on the same page, simply uncommenting stubs.c solves
your problem with no libm changes, right?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Peter Wemm writes:
As you said, _sleeping_ is the problem. M_WAITOK means you may sleep if
you like. ie: it is a time bomb waiting for the right low memory conditio
n
which will then explode with a 100% authentic crash or lock up
Terry Lambert wrote:
Peter Wemm wrote:
I think _sleeping_ is a problem, but allocation with M_WAITOK
shouldn't be, given it's strange definition of waiting. This
is one of those hacks that John Baldwin was talking about earlier...
As you said, _sleeping_ is the problem. M_WAITOK
Terry Lambert wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Peter Wemm writes:
As you said, _sleeping_ is the problem. M_WAITOK means you may sleep if
you like. ie: it is a time bomb waiting for the right low memory condit
ion
which will then explode with a 100
directory.
There is a bug in /bin/sh. You might like to try something like this:
rm -rf /usr/obj/*
cd /usr/src/bin/sh
make clean
make obj
make depend
make
make install
As long as your /usr/src is up to date, that should save you.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED
Have you done a 'make world' in the last 24 hours or so? What does this show:
ls -l /usr/bin/c++ /usr/lib/libstdc++.so.4 /usr/include/g++/bits/c++config.h
They should all exist and be roughly the same time/date.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED
format just like everybody else.)
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
waiting is explicitly not allowed. There are other functions that can
tsleep as well that we have not added checks for yet, so this is likely
just the tip of the iceberg. :-(
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go
Terry Lambert wrote:
Peter Wemm wrote:
The bug is that things are calling things like malloc with M_WAITOK when
waiting is explicitly not allowed. There are other functions that can
tsleep as well that we have not added checks for yet, so this is likely
just the tip of the iceberg
Dag-Erling Smorgrav wrote:
perl: Perl is not installed, try 'pkg_add -r perl'
Indeed it is installed. Note that you have exposed a fundamental bug
in the perl wrapper. It only searches $PATH, and /usr/local/bin is not
in $PATH for many system tools (eg: pkg_add -r).
Cheers,
-Peter
--
Peter
Dag-Erling Smorgrav wrote:
Peter Wemm [EMAIL PROTECTED] writes:
Indeed it is installed. Note that you have exposed a fundamental bug
in the perl wrapper. It only searches $PATH, and /usr/local/bin is not
in $PATH for many system tools (eg: pkg_add -r).
How about this:
Index: perl.c
, version 1 (FreeBSD), statically
linked, not stripped
Yes, we do run with x86 userland VM size = 4GB on freebsd/ia64 since the
kernel is elsewhere :-)
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
Stop in /d/home/des/tinderbox/src.
*** Error code 1
Stop in /d/home/des/tinderbox/src.
*** Error code 1
Stop in /d/home/des/tinderbox/src.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Cheers,
-Peter
--
Peter Wemm - [EMAIL
until %b is implemented in GCC 3.1 .
Add NO_WERROR=true to /etc/make.conf for the time being.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED
to 'poisoned' malloc/calloc/etc calls.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
David O'Brien is in the process of committing gcc-3.1. If you are not
prepared to do your own fixing, now would be a good time to avoid -current.
It is a big task and will take a while to finish, so please be patient!
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Care to whip up a patch? I'll commit it for you. (I'd do it but I'm working
on something)
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED
?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Peter Wemm wrote:
Maxime Henrion wrote:
Hi,
I think I may have found the bug. Could someone test the attached patch
and report if it fixes the problem or not ?
Thanks in advance,
Maxime
No joy:
FreeBSD 5.0-CURRENT #8: Sat Apr 27 13:48:13 PDT 2002
[EMAIL
Maxime Henrion wrote:
Peter Wemm wrote:
This turned out to be part of the problem. I committed your patch and
another followup that got the rest of it. The outstanding problems were:
1) checkmethod caused use_kenv to be set only once and the next time it
was called, use_kenv would stay
in other modules without
registering a dependency for this reason.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
Matthew N. Dodd wrote:
On Thu, 25 Apr 2002, Peter Wemm wrote:
This is well known. If we recieve an ARP frame before we sent one, then
we print this. eg: a broadcast ARP packet will trigger it. dhclient
etc use bpf etc so ARP isn't initialized at this point.
We could just put
,
even for non-DHCP stuff. I'm not sure what is causing it.
This is well known. If we recieve an ARP frame before we sent one, then
we print this. eg: a broadcast ARP packet will trigger it. dhclient etc
use bpf etc so ARP isn't initialized at this point.
Cheers,
-Peter
--
Peter Wemm
:
if (params (i = narg * sizeof(int))
(error = copyin(params, (caddr_t)args, (u_int)i))) {
(narg comes from the syscall table).
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
again. There is nothing significant that
is still on the vendor branch that is worth messing around with.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL
, and rather have people log in
and 'su' instead. But even then, it's I would rather see it dead. :-)
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED
-CURRENT builds on
4-STABLE systems, not in cross-archetecture builds.
That is a different set of problems. cross-version builds have always been
very trouble-prone. same-version cross builds are far less of a problem.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
201 - 300 of 757 matches
Mail list logo
