On Mon, Jun 03, 2002 at 01:42:24PM -0700, Kris Kennaway wrote:
> * (lots of ports) The new C++ compiler deprecated a lot of headers by
> moving them to a different directory: this breaks a heck of a lot of
> ports). IMO we should be searching this directory by default.
I believe it is the i
On Mon, Jun 03, 2002 at 03:14:23PM -0700, Paul Herman wrote:
> On Mon, 3 Jun 2002, Maxim Sobolev wrote:
>
> > However, before proceeding I would like to get an advice with regard
> > to the most appropriate procedure for doing the upgrade.
>
> This came up in another list somewhere (don't know
> Actually, it broke fsck_ffs.
>
> Workaround to avoid the known broken case:
The brokenness in ix86_expand_clrstr is quite visible when you
compare the function with ix86_expand_movstr.
- Tor Egge
Index: contrib/gcc/config/i386/i386.c
In message: <[EMAIL PROTECTED]>
"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
: "Scott Penno" <[EMAIL PROTECTED]> wrote:
: > I removed apm from the kernel which appeared to be playing having with acpi
: > and things are now working a treat. The card works fine, however I do
: > recei
On Tue, 4 Jun 2002, I wrote:
> gcc now generates inline code for memset in some cases. Broken code.
Actually, it only generates inline code for memset in a few more cases,
and the case of a non-constant length is broken (and some cases of
constant lengths are pessimized (e.g., length 7)).
> ..
Thank you very much.
After I sent previous question to you, I was still thinking the mail.
and last night when I went to bed, I suddenly found that I was wrong,
choosethread() selects a highest priority thread from queue, if it is
the lastest assigned thread, there is of course no more thread as
On Mon, Jun 03, 2002 at 04:17:14PM -0700, Terry Lambert wrote:
> How long does it take to build world + all ports, vs. just "world",
> if what you are doing is building everything, not caring about
> correcting ports dependencies? E.g. not serializing through the
> ports build farm process? Is
has any of this been reported to the XFree86 folk? I just CVSup'd the
latest XFree86 source code and this #pragma condition appears to still
exist :(
On Mon, 3 Jun 2002, Stanislav Grozev wrote:
> On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote:
> >
> > stupid question, but wha
Terry, I have a high speed connection over here, so if its purely a
'typing' change sort of thing, if you want to tell me what needs to be
done to fix these, I can make the changes and submit patches (I can't
login to my FreeBSD account to make the commits myself ... my key went out
of date *sigh
On Tue, Jun 04, 2002 at 02:10:28AM +0200, Cyrille Lefevre wrote:
> last week, I've began to comlete your work done last year by resyncing
> FreeBSD pax w/ the NetBSD/OpenBSD ones. would be done by the end of this
> week...
Cool! Thanks for doing this.
Kris
msg39139/pgp0.pgp
Description:
On Mon, Jun 03, 2002 at 04:54:32PM -0700, Terry Lambert wrote:
> Kris Kennaway wrote:
> > > But the error handling path of any program is not one of them; if
> > > you are optimizing something other than the success path, there is
> > > something fundamentally wrong with your program or problem st
On Mon, Jun 03, 2002 at 03:49:49PM -0700, Kris Kennaway wrote:
> On Mon, Jun 03, 2002 at 03:14:23PM -0700, Paul Herman wrote:
> > On Mon, 3 Jun 2002, Maxim Sobolev wrote:
> >
> > > However, before proceeding I would like to get an advice with regard
> > > to the most appropriate procedure for doi
Kris Kennaway wrote:
> > But the error handling path of any program is not one of them; if
> > you are optimizing something other than the success path, there is
> > something fundamentally wrong with your program or problem statement.
>
> So how about you do more than the average person's part t
On Mon, Jun 03, 2002 at 04:21:24PM -0700, Terry Lambert wrote:
> > > http://bento.freebsd.org/errorlogs/5-latest/bogosort-0.3.3.log
> >
> > Any program which declares sys_errlist for itself is wrong. In most
> > cases, the program should be using either strerror() or strerror_r(),
> > dependi
gcc now generates inline code for memset in some cases. Broken code.
E.g., compiling the following with -O:
%%%
#include
int foo[100];
int x;
main()
{
memset(&foo[0], 0, x);
}
%%%
gives (at least if you have fixed function alignment):
%%%
.file "z.c"
.text
On Mon, Jun 03, 2002 at 03:14:23PM -0700, Paul Herman wrote:
> On Mon, 3 Jun 2002, Maxim Sobolev wrote:
>
> > However, before proceeding I would like to get an advice with regard
> > to the most appropriate procedure for doing the upgrade.
>
> This came up in another list somewhere (don't know o
Maksim Yevmenkin writes:
> I'm having hard time with Netgraph on recent -current.
>
> First, there is a lot of warnings (see below) related to
> initialization of struct ng_parse_struct_info. I think
> it is related to zero sized "fields" array. Someone else
> already posted about the same proble
Hackers,
I'm having hard time with Netgraph on recent -current.
First, there is a lot of warnings (see below) related to
initialization of struct ng_parse_struct_info. I think
it is related to zero sized "fields" array. Someone else
already posted about the same problem.
Second, my laptop crash
On Mon, 3 Jun 2002, Maxim Sobolev wrote:
> However, before proceeding I would like to get an advice with regard
> to the most appropriate procedure for doing the upgrade.
This came up in another list somewhere (don't know off hand), but
you might also consider having tar wrap around pax.
OpenBS
I have been working on several projects using AIO to break up latency in
large, sequential reads. In my code, I was surprised at what appear to be
performance problems where splitting a 256k read into 4 64k reads was
actually quite a bit slower than a single 256k read (in fact, 3 times
slower).
< said:
> * (>35 ports) Something caused sys_nerr to change prototypes. It looks
> like this might be because the definition of __const from
>has changed, but I can't see why. See for example
> http://bento.freebsd.org/errorlogs/5-latest/bogosort-0.3.3.log
Any program which declares s
Build errors encountered in the latest buildworld of -current.
Error output attached with mail. Hope it helps. Uname(1) of
the system is:
FreeBSD 5.0-CURRENT #0: Sat May 4 19:07:01 BST 2002
Thanks.
--
Hiten Pandya
http://storm.uk.FreeBSD.org/~hiten
Finger [EMAIL PROTECTED] for PGP public
I've done another package build run under a recent 5.0-CURRENT.
Things are not good: only 45% of the ports in the ports collection are
actually building, compared to a build rate of over 90% on 4.x.
The biggest chunk of damage comes from the XFree86-libraries failure
reported here already; apart
Folks,
As you might know GNU Tar in the base system is way too outdated (it
wasn't updated since year 1993). This causes many problems, e.g.
inability to extract POSIX.1 tar files, limitation on major/minor
device numbers, unability to archive/extract files with names more
than 100 chars long etc
Peter Wemm <[EMAIL PROTECTED]> writes:
> The single biggest problem seemed to be NFS, but you're not using that
> anymore are you?
I do, the sources are on NFS, but the obj dir is in /tmp.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
Thanks for looking at it
This is not offtopic..
the answer is:
No, the code is correct..
here is the logic..
If there are N processors, then there are at most N KSEs (kernel
schedulable entities) working to process threads that belong to this
KSEGOUP. (kg). If there are N or more threads
Dag-Erling Smorgrav wrote:
> Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> > I'm doing the daily (-j8) snapshots on a 2-CPU SMP machine for
> > i386, pc98, alpha, ia64, and sparc64, and never saw this problem.
> > Could it be that you have a faulty hardware on your tinderbox,
> > as I already saw a
On Mon, Jun 03, 2002 at 05:06:23PM +0200, Stanislav Grozev wrote:
> On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote:
> >
> > stupid question, but what is the fix for the #pragma weak issue? :(
>
> you replace
> #pragma weak foo = bar
> with either
> #pragma weak foo
On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote:
>
> stupid question, but what is the fix for the #pragma weak issue? :(
you replace
#pragma weak foo = bar
with either
#pragma weak foo = "bar" /* this is easier */
or
if __GNUC__ >= 3
int
stupid question, but what is the fix for the #pragma weak issue? :(
On Mon, 3 Jun 2002, Stanislav Grozev wrote:
> Hello,
>
> I have a -CURRENT system (world from yesterday, ports from today).
> I'm trying to compile the XFree86-libraries-4.2.0 from ports, but
> I have troubles. After resolvin
On Mon, Jun 03, 2002 at 07:23:33AM -0500, Peter Schultz wrote:
> When promted to enter the root password there is no visible indicator
> that it's time to type.
When I last installed a snapshot, it did prompt, but prompted on the wrong
virtual terminal.
Tim
To Unsubscribe: send mail to [EMAI
Hello,
I have a -CURRENT system (world from yesterday, ports from today).
I'm trying to compile the XFree86-libraries-4.2.0 from ports, but
I have troubles. After resolving the one with the #pragma weak,
and also one with a missing ../ from one of the Mesa Makefiles,
now I get the following:
---
Since -current uses devfs now is the remaking devices step still needed?
When promted to enter the root password there is no visible indicator
that it's time to type.
Are these PR material?
Pete...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body
On Mon, Jun 03, 2002 at 12:53:17PM +0200, Dag-Erling Smorgrav wrote:
> Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> > I'm doing the daily (-j8) snapshots on a 2-CPU SMP machine for
> > i386, pc98, alpha, ia64, and sparc64, and never saw this problem.
> > Could it be that you have a faulty hardware
Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> I'm doing the daily (-j8) snapshots on a 2-CPU SMP machine for
> i386, pc98, alpha, ia64, and sparc64, and never saw this problem.
> Could it be that you have a faulty hardware on your tinderbox,
> as I already saw a few reports from you, always in a di
--- Peter Jeremy <[EMAIL PROTECTED]> wrote:
> I decided to do some experimenting with snapshots and managed to
> deadlock my system. (Basically, I had a cron job that was trying
> to snapshot all my filesystems every 5 minutes - with a view to
> being able to undo any "accidents" I might make).
Hello,
what do you thing about following piece of /usr/bin/top output?
Pay attention on "WCPU"
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
71398 igorr 960 4048K 2568K select 0:00 0.0<% 0.29% xterm
385 igorr 960 9504K 5356K select 0:10 0.0
Am Mo, 2002-05-27 um 19.52 schrieb David O'Brien:
> On Mon, May 27, 2002 at 12:23:13PM +0200, Georg-W. Koltermann wrote:
> > Please read bin/38236. I wasn't asking for general directions but for a
> > specific solution to a current -current problem.
>
> RTFM specifically the "-gstabs+" GCC optio
On Sat, Jun 01, 2002 at 09:36:40PM -0700, Dag-Erling Smorgrav wrote:
[...]
> --
> >>> stage 4: building everything..
> --
> ===> gnu/usr.bin/binutils/ar
> ../libbinutils/libbinut
40 matches
Mail list logo
