I have the following error while compiling Sawfish on
recent -current.
Is it my half updated fault or the -current issue?
gmake[1]: Entering directory
`/home/SRC/FreeBSD/FreeBSD-current/ports/x11-wm/sawfish/work/sawfish-0.36/lisp'
SAWFISHLISPDIR=. SAWFISHEXECDIR=../src/.libexec
From: Bruce Evans [EMAIL PROTECTED]
Date: Sun, 11 Feb 2001 07:35:51 +1100 (EST)
On Sat, 10 Feb 2001, Justin T. Gibbs wrote:
Are there any reason device drivers do not check if thier devices are
writable or not when they are opened ? I think returning an error
value, like `od', is the
Thank you for quick reply.
I found that my librep was old one - Sept one living in
/usr/local/libexec/rep., and the latest one (v 1.23 2001/01/07)
goes under /usr/X11R6/libexec/rep/i386--freebsd5.0/.
So, I deleted /usr/local/libexec/rep hoping that new one
living under X11R6 be used.
My computer reboots when trying to print. I'm not shure from which
update it doesn't work.
Am I doing something wrog or?
Rasa
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, Feb 11, 2001 at 03:24:06PM +0100, Rasa Karapandza wrote:
My computer reboots when trying to print. I'm not shure from which
update it doesn't work.
Am I doing something wrog or?
If you're running -current, then this problem has been widely reported
in the list already. Go back to
Okay, I've finally come up with a patch that enables the OpenSSL asm
code in a way which is generically controllable and extends to other
code which may want to enable CPU-specific optimizations (e.g. libgmp).
The patch is at
http://www.freebsd.org/~kris/openssl-asm.patch
It's based on a
Can the people working on the locale stuff test
their changes prior to check-in?
/usr/src/lib/libc/../libc/locale/lmessages.c: In function `__messages_load_locale':
/usr/src/lib/libc/../libc/locale/lmessages.c:61: syntax error before `struct'
/usr/src/lib/libc/../libc/locale/lmessages.c:61: too
Updated patch now available at the same location. Changes:
* Document the MACHINE_CPU types which are currently used
* Make NOPERL mutually exclusive with OpenSSL ASM and document it
* Teach make(1) about MACHINE_CPU and provide sensible defaults for
i386 and alpha.
* Kris Kennaway [EMAIL PROTECTED] [010211 12:32] wrote:
Updated patch now available at the same location. Changes:
* Document the MACHINE_CPU types which are currently used
* Make NOPERL mutually exclusive with OpenSSL ASM and document it
* Teach make(1) about MACHINE_CPU and provide
On Sun, Feb 11, 2001 at 12:47:07PM -0800, Alfred Perlstein wrote:
Looks awesome, someone complained that Linux was able to maintain
an order of magnitude more SSL connections than FreeBSD, since you
say this gives us a 3-5x speed up, I'd really like to see it committed
and ported to -stable
* Kris Kennaway [EMAIL PROTECTED] [010211 12:52] wrote:
On Sun, Feb 11, 2001 at 12:47:07PM -0800, Alfred Perlstein wrote:
Looks awesome, someone complained that Linux was able to maintain
an order of magnitude more SSL connections than FreeBSD, since you
say this gives us a 3-5x speed
What gives ???
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/syv/src/lib/libc/include -D__DBINTERFACE
_PRIVATE -DINET6 -I/usr/obj/syv/src/lib/libc -DPOSIX_MISTAKE -I/syv/src/lib/libc
/../libc/locale -DBROKEN_DES -DYP -DHESIOD -I/usr/obj/syv/src/i386/usr/include -
c
In 38689.981926085@critter, Poul-Henning Kamp wrote:
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/syv/src/lib/libc/include -D__DBINTERFACE
_PRIVATE -DINET6 -I/usr/obj/syv/src/lib/libc -DPOSIX_MISTAKE -I/syv/src/lib/libc
/../libc/locale -DBROKEN_DES -DYP -DHESIOD -I/usr/obj/syv/src/i386/usr/include
On Sun, Feb 11, 2001 at 01:02:43PM -0800, Alfred Perlstein wrote:
* Kris Kennaway [EMAIL PROTECTED] [010211 12:52] wrote:
On Sun, Feb 11, 2001 at 12:47:07PM -0800, Alfred Perlstein wrote:
Looks awesome, someone complained that Linux was able to maintain
an order of magnitude more SSL
On Sun, Feb 11, 2001 at 12:28:02PM -0800, Kris Kennaway wrote:
Updated patch now available at the same location. Changes:
* Document the MACHINE_CPU types which are currently used
Actually, it occurs to me that this will be useful for ports as
well. Currently some of them have nonstandard
On Sun, 11 Feb 2001, Daniel Eischen wrote:
deischen2001/02/11 14:06:46 PST
Modified files:
include stdio.h
Log:
libc MT-safety, part 2.
Add a lock to FILE and define an additional flag.
This commit caused some bootstrap problems. The installworld
On Sun, Feb 11, 2001 at 10:56:18PM +0100, Robert Drehmel wrote:
In 38689.981926085@critter, Poul-Henning Kamp wrote:
[buildworld failure lib/libc/locale/lmessages.c]
It should work with '#include stddef.h'.
Yep, that seems to be enough to get past this point. I don't know if there
are any
On Sun, 11 Feb 2001, Daniel Eischen wrote:
On Sun, 11 Feb 2001, Daniel Eischen wrote:
deischen2001/02/11 14:06:46 PST
Modified files:
include stdio.h
Log:
libc MT-safety, part 2.
Add a lock to FILE and define an additional flag.
This commit
On Mon, 12 Feb 2001, Bruce Evans wrote:
On Sun, 11 Feb 2001, Daniel Eischen wrote:
On Sun, 11 Feb 2001, Daniel Eischen wrote:
deischen2001/02/11 14:06:46 PST
Modified files:
include stdio.h
Log:
libc MT-safety, part 2.
Add a lock
jake2001/02/11 16:20:08 PST
Modified files:
sys/alpha/alpha trap.c
sys/dev/acpica/Osd OsdSchedule.c
sys/i386/i386genassym.c swtch.s trap.c
sys/ia64/ia64trap.c
sys/kern init_main.c kern_condvar.c kern_idle.c
The new libc is incompatible with some old applications, but I'm not
too sure why. The lock was added at the end of FILE...
The size of FILE changed, thus the old application and the new library
no longer agree about the values for stdout and stderr:
#define stdin (__sF[0])
: The new libc is incompatible with some old applications, but I'm not
: too sure why. The lock was added at the end of FILE...
:
:The size of FILE changed, thus the old application and the new library
:no longer agree about the values for stdout and stderr:
:
: #define stdin (__sF[0])
On Sun, Feb 11, 2001 at 04:44:21PM -0800, Matt Dillon wrote:
: The new libc is incompatible with some old applications, but I'm not
: too sure why. The lock was added at the end of FILE...
:
:The size of FILE changed, thus the old application and the new library
:no longer agree about the
:
: This is a major change to libc. The library maj must be bumped if you
: intend to change the sizeof(FILE), or every single third party application
: that uses stdio will break.
:
: -Matt
Oh wait, is libc already bumped in current verses 4.2? If
Matt Dillon wrote:
:
: This is a major change to libc. The library maj must be bumped if you
: intend to change the sizeof(FILE), or every single third party applicatio
n
: that uses stdio will break.
:
: -Matt
Oh wait, is libc already
On Sun, 11 Feb 2001, Peter Wemm wrote:
Matt Dillon wrote:
:
: This is a major change to libc. The library maj must be bumped if you
: intend to change the sizeof(FILE), or every single third party applicatio
n
: that uses stdio will break.
:
:
:
:I cant help but wonder why on earth we didn't have it like this from the
:start:
:
:Index: include/stdio.h
:===
:...
Yah. I say commit it. Might as well, it can't hurt any worse then
changing the size of FILE.
Daniel Eischen wrote:
On Sun, 11 Feb 2001, Peter Wemm wrote:
Matt Dillon wrote:
:
: This is a major change to libc. The library maj must be bumped if yo
u
: intend to change the sizeof(FILE), or every single third party applic
atio
n
: that uses stdio
In his article at http://www.daemonnews.org/200102/armoring.html,
Markus Delves describes the usage of the SSH ftp command to do secure
file copies. I further notice that we install the sftpd server in
both -stable and -current (though we don't include any prototype
information on how to start
On Sun, Feb 11, 2001 at 07:07:40PM -0800, Jordan Hubbard wrote:
In his article at http://www.daemonnews.org/200102/armoring.html,
Markus Delves describes the usage of the SSH ftp command to do secure
file copies. I further notice that we install the sftpd server in
both -stable and -current
On Sun, 11 Feb 2001, Daniel Eischen wrote:
The new libc is incompatible with some old applications, but I'm not
too sure why. The lock was added at the end of FILE...
It's very incompatible. I happened to compile make(1) with the new
stdio.h and the old libc.a (partly because unrelated
On Sun, 11 Feb 2001, Peter Wemm wrote:
I cant help but wonder why on earth we didn't have it like this from the
start:
Index: include/stdio.h
===
RCS file: /home/ncvs/src/include/stdio.h,v
retrieving revision 1.26
diff -u
Bruce Evans wrote:
On Sun, 11 Feb 2001, Peter Wemm wrote:
I cant help but wonder why on earth we didn't have it like this from the
start:
Index: include/stdio.h
===
RCS file: /home/ncvs/src/include/stdio.h,v
Peter Wemm wrote:
Bruce Evans wrote:
On Sun, 11 Feb 2001, Peter Wemm wrote:
I cant help but wonder why on earth we didn't have it like this from the
start:
Index: include/stdio.h
===
RCS file:
Now I'm in the middle of make -j10 buildworld. Is -CURRENT in bad shape?
I'm planning to blow away all /usr/local and /usr/X11R6 to build "a whole
new world", again... ;)
Should I wait for a couple of hours/days?
Thanks...
/john
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
* John Indra [EMAIL PROTECTED] [010211 22:20] wrote:
Now I'm in the middle of make -j10 buildworld. Is -CURRENT in bad shape?
I'm planning to blow away all /usr/local and /usr/X11R6 to build "a whole
new world", again... ;)
Should I wait for a couple of hours/days?
Current from Sat Feb
On Sun, Feb 11, 2001 at 10:39:56PM -0800, Alfred Perlstein wrote:
Current from Sat Feb 10 17:00:18 looks ok, there were just some
patches to the scheduler but no one has complained yet. Let us
know. :)
Thanks for the fast reply. I really need it.
OK... buildworld seems to be running ok right
37 matches
Mail list logo
