On Wed, May 15, 2002 at 09:31:11AM +0300, Ruslan Ermilov wrote:
I insist we should officially support upgrading from X.any to X+1.0-R,
minimally.
You need to either get concensis from arch@ or core@ then.
This actually doesn't affect only cross-arch case, the subject is wrong.
It affects
Fwiw, with tonight's -current I am seeing
cc -O -pipe -march=pentiumpro -ffreestanding -DCOMPORT=0x3f8 -DCOMSPEED=9600
-DTERM_EMU -I/disk0/usr/src/sys/boot/i386/libi386/../../common
-I/disk0/usr/src/sys/boot/i386/libi386/../btx/lib
On Tue, May 14, 2002 at 12:18:14PM -0700, David O'Brien wrote:
On Tue, May 14, 2002 at 04:10:51PM +0300, Ruslan Ermilov wrote:
Why change in the first place?
What was wrong with 'make includes'? Why break POLA?
They were broken. See commit log for share/mk/bsd.incs.mk,v 1.1 for
On Tue, May 14, 2002 at 06:43:01AM +, Hiten Pandya wrote:
--- Ruslan Ermilov [EMAIL PROTECTED] wrote:
People might want to use it like that:
make world
mv /usr/include /usr/include.old
Sorry to butt in; but wouldn't it be more good if this step was done
by the build scripts
On Tue, 14 May 2002, David O'Brien wrote:
On Wed, May 15, 2002 at 12:38:49PM +1000, Bruce Evans wrote:
I really do not like this change, please return things such that the
long-ingraned cd /usr/src ; make includes.
I planned to fix this by changing make includes to print
Unwarranted
On Tue, May 14, 2002 at 11:40:48PM -0700, David O'Brien wrote:
On Wed, May 15, 2002 at 09:31:11AM +0300, Ruslan Ermilov wrote:
I insist we should officially support upgrading from X.any to X+1.0-R,
minimally.
You need to either get concensis from arch@ or core@ then.
I first plan to
On Wed, May 15, 2002 at 05:05:02PM +1000, Bruce Evans wrote:
I prefer not to do this. There are simpler methods to get broken
headers, starting with rm -rf :). I prefer everyone to use (documented)
user-level targets like world and install for installing includes,
since it would be
On Wed, May 15, 2002 at 09:59:19AM +0300, Ruslan Ermilov wrote:
Actually, from what I've read, I plan on renaming these targets to
buildincludes and installincludes, and restoring the `includes' to
mean build + install.
Thank you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Wed, May 15, 2002 at 05:05:02PM +1000, Bruce Evans wrote:
On Tue, 14 May 2002, David O'Brien wrote:
On Wed, May 15, 2002 at 12:38:49PM +1000, Bruce Evans wrote:
I really do not like this change, please return things such that the
long-ingraned cd /usr/src ; make includes.
I
Hi,
On Tue, May 14, 2002 at 06:05:27PM +0300, Ruslan Ermilov wrote:
On Wed, May 15, 2002 at 12:18:04AM +1000, Bruce Evans wrote:
That's rather hackish, and doesn't handle garbage other than includes.
I usually find stale files by comparing my world with a world installed
in a nonstandard
The following email address, [EMAIL PROTECTED] has been removed from the
Verba Volant Newsletter list.
If you did not cancel your email address or you wish to continue receiving Verba
Volant, please send an e-mail to [EMAIL PROTECTED]
Thank you and best regards,
Verba Volant
To Unsubscribe:
Currently, a new runnable thread cannot preempt the thread on any
processor other than the thread that called mi_switch(). For
instance, we do something like the following in _mtx_unlock_sleep():
--- v --- _mtx_unlock_sleep() --- v ---
setrunqueue(th_waken_up);
if (curthread-preemptable
On 15-May-2002 Seigo Tanimura wrote:
Currently, a new runnable thread cannot preempt the thread on any
processor other than the thread that called mi_switch(). For
instance, we do something like the following in _mtx_unlock_sleep():
--- v --- _mtx_unlock_sleep() --- v ---
Trying to boot with a newly-built loader (make world earlier today
from fresh sources) results in:
FreeBSD/alpha SRM disk boot, Revision 1.2
([EMAIL PROTECTED], Wed May 15 08:01:43 CEST 2002)
Memory: 262144 k
Loading /boot/defaults/loader.conf
/boot/kernel/kernel data=0x283780+0x63670 /
Hit
On 15-May-2002 Bruce Evans wrote:
On Tue, 14 May 2002, David O'Brien wrote:
On Wed, May 15, 2002 at 12:38:49PM +1000, Bruce Evans wrote:
I really do not like this change, please return things such that the
long-ingraned cd /usr/src ; make includes.
I planned to fix this by changing
On 15-May-2002 Dag-Erling Smorgrav wrote:
Trying to boot with a newly-built loader (make world earlier today
from fresh sources) results in:
FreeBSD/alpha SRM disk boot, Revision 1.2
([EMAIL PROTECTED], Wed May 15 08:01:43 CEST 2002)
Memory: 262144 k
Loading /boot/defaults/loader.conf
Hi list,
I get a persistent Signal 12 when upgrading from -stable to -current :
stage 4: populating /usr/obj/usr/src/i386/usr/include
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386
Dag-Erling Smorgrav writes:
Trying to boot with a newly-built loader (make world earlier today
from fresh sources) results in:
..
boot failure
no matter which kernel I try to boot. Booting my new kernel with the
old loader (from the DP1 dist) works fine until it tries to start
On Wed, May 15, 2002 at 03:32:45PM +0200, Hans Lambermont wrote:
Hi list,
I get a persistent Signal 12 when upgrading from -stable to -current :
Signal 12 indicates a non-existent system call. This means that
your running world is incompatible with your kernel. Fix this
first. (You
On Wed, May 15, 2002 at 02:22:04PM +0200, Dag-Erling Smorgrav wrote:
Trying to boot with a newly-built loader (make world earlier today
from fresh sources) results in:
FreeBSD/alpha SRM disk boot, Revision 1.2
([EMAIL PROTECTED], Wed May 15 08:01:43 CEST 2002)
Memory: 262144 k
Loading
What do you think about doing a little more polishing and rolling a new
set of patches taking this /etc/rc.conf option into account? Your kernel
env dhcp variables are really good.
i was thinking of adding something like this to dhcp:
option FBSD.rc-conf
On Wed, May 15, 2002 at 09:26:29AM -0700, David O'Brien wrote:
Almost correct. For the record and future ports:
It's useful for a new arch that doesn't have make world yet. When I would
update world on my sparc before gcc was bmake'd it went something like this:
sudo make
... and then I got a panic. Hmmm More particulars:
The events being described occur on my SMP build machine (the
laptop is still working on building today's -CURRENT as I type).
I've been tracking -CURRENT daily on this machine for some time; each
day, I build the day's -CURRENT while
I observed gcc 2.95.4 and gcc 3.1 interpret (or maybe optimize) the
following code differently (CFLAGS=-O):
int main(void)
{
unsigned char i = 127;
printf(%d\n, ((char)(i 1)) / 2);
return 0;
}
gcc 2.95.4 says it's -1, whereas gcc 3.1 says it's 127. On FreeBSD
char should be signed, so I
[putting anti-flame on]
--
N'aimer qu'un seul est barbarie, car c'est au détriment de tous les
autres. Fût-ce l'amour de Dieu.
- Nietzsche, Par delà le bien et le mal
---BeginMessage---
On Wed, 15 May 2002 13:16:52 -0400
The Anarcat [EMAIL PROTECTED] wrote:
Why isn't
On Wed, 15 May 2002, David O'Brien wrote:
Almost correct. For the record and future ports:
[jhb wrote]
It's useful for a new arch that doesn't have make world yet. When I would
update world on my sparc before gcc was bmake'd it went something like this:
sudo make hierarchy
sudo
The Anarcat wrote:
[putting anti-flame on]
To invite a normal discussion you should at least provide the
following information:
- What `rclean' is for?
- Why do you think it could be useful in base system?
Your assumption that the list readers know answers to those two
questions (or would
Akinori MUSHA wrote:
I observed gcc 2.95.4 and gcc 3.1 interpret (or maybe optimize) the
following code differently (CFLAGS=-O):
int main(void)
{
unsigned char i = 127;
printf(%d\n, ((char)(i 1)) / 2);
return 0;
}
Cool...
gcc 2.95.4 says it's -1,
Promotion of operand to
On Wed May 15, 2002 at 09:55:42PM +0300, Maxim Sobolev wrote:
The Anarcat wrote:
[putting anti-flame on]
s/on/suit on/
To invite a normal discussion you should at least provide the
following information:
Well, I expected people to look at the port, but I'll provide more
information
I had a -current system with the old version of gcc, and build world/kernel
that contained gcc-3.1:
5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon May 6 19:31:16 EDT 2002
Now for the first time with gcc-3.1 in place I have updated source (as of
just minutes ago 1500EDT 5.15.02) and am trying to build
gcc 3.1 simply defaults to unsigned chars. 127 1 = 254; 254 / 2 = 127.
My machine is too slow to test this expeditiously, but I'm trying
adding #define DEFAULT_SIGNED_CHAR 1 into freebsd-native.h .
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the
On Thu, May 16, 2002 at 02:42:34AM +0900, Akinori MUSHA wrote:
I observed gcc 2.95.4 and gcc 3.1 interpret (or maybe optimize) the
following code differently (CFLAGS=-O):
int main(void)
{
unsigned char i = 127;
printf(%d\n, ((char)(i 1)) / 2);
return 0;
}
I think GCC 3.1 does a
Bill Fenner wrote:
gcc 3.1 simply defaults to unsigned chars. 127 1 = 254; 254 / 2 = 127.
My machine is too slow to test this expeditiously, but I'm trying
adding #define DEFAULT_SIGNED_CHAR 1 into freebsd-native.h .
I will bet today's lunch money that you have found it for sure.
I guess
Duh. Sometimes I wish I had the patience to wait for my tests to complete
before sharing my guesses. I jumped to a wildly incorrect conclusion; gcc
3.1 still defaults to signed chars. Sorry for the bizarre misdirection.
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Bill Fenner wrote:
Duh. Sometimes I wish I had the patience to wait for my tests to complete
before sharing my guesses. I jumped to a wildly incorrect conclusion; gcc
3.1 still defaults to signed chars. Sorry for the bizarre misdirection.
There goes my lunch money. 8-(.
Man, your
John Baldwin [EMAIL PROTECTED] writes:
The kernel overflowed it's stack. In SRM, you can try to debug this
by using 'e sp' to get the stack pointer then get a stack dump and save
a copy of it in a log or something, reboot the machine, then use gdb's
list command on the kernel.debug to figure
Ruslan Ermilov wrote:
On Wed, May 15, 2002 at 03:32:45PM +0200, Hans Lambermont wrote:
I get a persistent Signal 12 when upgrading from -stable to -current :
Signal 12 indicates a non-existent system call. This means that
your running world is incompatible with your kernel. Fix this
I observed gcc 2.95.4 and gcc 3.1 interpret (or maybe optimize) the
following code differently (CFLAGS=-O):
int main(void)
{
unsigned char i = 127;
printf(%d\n, ((char)(i 1)) / 2);
return 0;
}
gcc 2.95.4 says it's -1, whereas gcc 3.1 says it's 127. On FreeBSD
char should
Date: Wed, 15 May 2002 09:58:50 -0700 (PDT)
From: David Wolfskill [EMAIL PROTECTED]
[Following up after getting today's -CURRENT built on my laptop; I have
some additional information. This is hand-transcribed, since I don't
have a serial console on my laptop. I was able ot get the build
Terry Lambert [EMAIL PROTECTED] wrote:
Bill Fenner wrote:
gcc 3.1 simply defaults to unsigned chars. 127 1 = 254; 254 / 2 = 127.
My machine is too slow to test this expeditiously, but I'm trying
adding #define DEFAULT_SIGNED_CHAR 1 into freebsd-native.h .
I will bet today's lunch
no matter which kernel I try to boot. Booting my new kernel with the
old loader (from the DP1 dist) works fine until it tries to start
init(8):
spec_getpages: preposterous offset 0xfff8f446
exec /sbin/init: error 5
spec_getpages: preposterous offset 0xfff81426c000
Brian Somers [EMAIL PROTECTED] writes:
This was fixed an hour or so ago. Phk backed out the daddr_t size
change pending investigation.
Does that fix the loader too, or just the kernel?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Brian Somers [EMAIL PROTECTED] writes:
This was fixed an hour or so ago. Phk backed out the daddr_t size
change pending investigation.
Does that fix the loader too, or just the kernel?
I'm not sure, I'm just rebuilding now.
Remember, /boot/loader.old is left around... handy in this
On 15-May-2002 Dag-Erling Smorgrav wrote:
John Baldwin [EMAIL PROTECTED] writes:
The kernel overflowed it's stack. In SRM, you can try to debug this
by using 'e sp' to get the stack pointer then get a stack dump and save
a copy of it in a log or something, reboot the machine, then use gdb's
Brian Somers [EMAIL PROTECTED] writes:
This was fixed an hour or so ago. Phk backed out the daddr_t size
change pending investigation.
Does that fix the loader too, or just the kernel?
I'm not sure, I'm just rebuilding now.
Remember, /boot/loader.old is left around... handy
On Wed, May 15, 2002 at 03:15:39PM -0400, Jeff Ito wrote:
I had a -current system with the old version of gcc, and build world/kernel
that contained gcc-3.1:
...
cc1: warnings being treated as errors
/usr/src/sys/ddb/db_command.c: In function `db_fncall':
/usr/src/sys/ddb/db_command.c:549:
On Wed, May 15, 2002 at 07:43:22PM +0300, Ruslan Ermilov wrote:
one can easily ``make buildworld TARGET_ARCH=foo -DNO_cross-tools''.
I am now doing many cross buildworlds. Is there a target (used with
-DNOCLEAN) to use to save time and resume a build at stage 4?
To Unsubscribe: send mail to
On Wed, May 15, 2002 at 03:15:47PM -0700, David O'Brien wrote:
On Wed, May 15, 2002 at 03:15:39PM -0400, Jeff Ito wrote:
I had a -current system with the old version of gcc, and build world/kernel
that contained gcc-3.1:
...
cc1: warnings being treated as errors
On Tue, 2002-05-14 at 05:34, Alexander Leidinger wrote:
On 7 Mai, Benjamin Lewis wrote:
Now, on to the problem. I use amanda for backups, and since mid-April
I've been seeing items like the following in the backup report:
[edited for brevity]
| DUMP: slave couldn't reopen disk:
Date: Wed, 15 May 2002 17:14:10 -0700 (PDT)
From: David Xu [EMAIL PROTECTED]
Yesterday 'cvs update' and 'make world' causes BTX halted:
Yes; use /boot/loader.old to boot /boot/kernel.old. Once you've done
that, update src/sys/sys/types.h to rev. 1.62 rebuild.
(Procedure worked for me, b oth
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Wednesday 15 May 2002 04:14 pm, you wrote:
Yesterday 'cvs update' and 'make world' causes BTX halted:
int=000e err=0002 efl=00010002 eip=c02cdeec
eax=0001 ebx=003b9c00 ecx=01ff edx=10fc
esi=003b9001 edi=003c1000 ebp= esp=c03bcd99
cs=0008 ds=0010 es=0010
First: It's great to see gcc3 in -CURRENT, a round of cheers for obrien@! :)
So, please, don't misread this question as some kind of hurry, hurry!,
but: Is libstdc++-v3 already on anyone's schedule, and if so, when can
we expect it to hit the tree?
--
Michael Nottebrock
To Unsubscribe:
So - yes - it seems gcc 3.1 does have a problem...
Indeed - easily determined by breaking down the expression.
So, who's gonna report it to gcc-bugs? knu?...
int
main()
{
unsigned char i = 127;
char j;
printf(%d\n, ((char)(i 1)));
j = ((char)(i 1)) / 2;
printf(%d\n, j);
Thomas David Rivers wrote:
Well - it's not counter-intuitive on many machines... For example,
on the IBM mainframe - there is an instruction to load a character
into a register - but not one that loads *and* sign-extends. So,
you can get much better code if characters are unsigned by
On Wed, May 15, 2002 at 03:18:15PM -0700, David O'Brien wrote:
On Wed, May 15, 2002 at 07:43:22PM +0300, Ruslan Ermilov wrote:
one can easily ``make buildworld TARGET_ARCH=foo -DNO_cross-tools''.
I am now doing many cross buildworlds. Is there a target (used with
-DNOCLEAN) to use to save
56 matches
Mail list logo
