Apologies to everyone who will get this e-mail twice. My previuos
attempt usig different email account has been bounced back by
hub.freebsd.org.
I reported this bug to Julian and he promised to fix it soon. Unfortunately,
that didn't happen yet. In a meantime, I am using
the patch attached.
Of
My previos mail
a) is missing a Subject
b) contains typo in the patch,
(td ? td->td_proc : NULLi)^ Unwanted 'i' is here
:(
Apologies to everyone again. I was in a bit of a hurry
when sending previos messages.
___
> and I've "made world" a lot of times like that.
> and if I do it by hand as sugested, it doesn;t make any difference
> either.
Just a guess - have you removed existing old libraries from /usr/lib?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of t
> no, should I?
Only if you have older libraries with the same names as as ones
installed in /usr/lib/compat. As Ruslan pointed out, existing Makefiles
in lib/compat should take care of that automatically. The change was
added in last September.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
>
> Sorry, no hint by my side, but I can report exactly the same problem
> on an Athlon-C System equipped with a VIA-KT133A chipset.
> (actually it has the same USB controller, so it was expectable)
>
> Riggs
I am seeing the same symptoms while using Microsoft USB mouse with
KT133A-based comp
I had no problem with kernel from February 14, but failed ums probes are
happening very consistently with kernel from Feb 18. Kernels from dates
earlier than Feb 14 failed to attach USB mouse most of the time but
sometimes misteriously managed to work. No configuration was changing
between success
L PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
E-Mail: Alexander Kabaev <[EMAIL PROTECTED]>
Date: 21-Apr-2001
Time: 10:49:59
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>
> Ciao,
> Sheldon.
Sorry for butting in. Adding new non-portable functionality to solve the problem
which could be adequitely taken care of using existing and well known
techniquies is not appropriate, I completely agree with you on that.
----------
E-Mail: Alexander
ECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
E-Mail: Alexander Kabaev <[EMAIL PROTECTED]>
Date: 19-Jul-2001
Time: 07:37:04
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
calling convention back
have been applied to both CURRENT and RELENG_5_0 branch. Unfortunately,
this means that all the software, compiled during the breakage window
and which is using functions returning structs by value, will have to be
recompiled.
--
Alexander Kabaev
To Unsubscribe: send mail
I've seen similar erratic behaviour myself when using gdb without -k
command switch. Can it be your problem too?
Also, you might want to look for sample .gdbinit files for useful gbd
macros other people are using. These files are in the tree somewhere.
--
Alexander Kabaev
To Unsubscribe:
the
> console:
>
> uhub0: port error, giving up port 2
> uhub0: port error, restarting port 2
>
What USB devices are connected to these ports?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
dies with 'short read' error there.
> Alexander, please commit your patch for gas(1). It works!
> It was very kind of you to develop it, and it was done
> incredibly fast. Thanks a lot!
Not going to happen until binutils people approve it. I am not sure
if the behavior I fixed was no
I plan to upgrade GCC to the version 3.2.2. Please hold your updates for
a while.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The import should be complete now. Please let us know if you
see any problems introduced with this GCC version.
On Sun, Feb 09, 2003 at 11:39:25PM -0500, Alexander Kabaev wrote:
> I plan to upgrade GCC to the version 3.2.2. Please hold your updates for
> a while.
--
Alexander Kaba
Apparently, you caught the src tree at the bad moment. See if another
cvsup/buildworld changes anything.
On Mon, 10 Feb 2003 02:33:48 -0500
Rahul Siddharthan <[EMAIL PROTECTED]> wrote:
> Alexander Kabaev wrote:
> > The import should be complete now. Please let us know if you
>
d as a list
> :but it's very easy to change.
>
> Does this list want a lock to protect it? I am unfamiliar with usb
> locking at the moment, so ignore if stupid.
There is nothing to be familiar with at the moment. UBS stack relies on
spls on -stable and Giant on -current to
#x27;s uic binary does not use libwizards.so. Please take time to dig a
little deeper and figure what binary exactly is failing. It is doubtful
someone will be able to help you otherwise.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Just committed /usr/src/libexec/rtld-elf/rtld.c v1.76 should fix that.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
r opinions about which method is preferred, or
> if there may be another good way to solve the bootstrap compiler
> issue.
>
> I have also attached two patches to this mail, which can be applied to
> head, to show the exact set of changes required for each method.
>
Does method 1)
is wrong. Just for the record. What FBSD* symbol versions
have to do with the library independently versioned by FSF?
--
Alexander Kabaev
signature.asc
Description: PGP signature
where we already are ;)
>
> well...i tried playing back a 1080p vide files while doing
> `make -j64 buildkernel` and FreeBSD's interactivity seems far from
> perfect.
One thing that just begs to be asked: since when decoding 1080p became
an interactive task?
--
Alexander Kabaev
signature.asc
Description: PGP signature
world, mergemaster) brought things back
> to normal. I can do a binary search if desired. Did someone else also
> see this?
>
> Happy 2011,
> Rene
Try backing out rtld down to version prior to this commit
http://svn.freebsd.org/changeset/base/216695 . There is an issue with
rtld's use of SSE on amd64 which will be fixed soon.
--
Alexander Kabaev
signature.asc
Description: PGP signature
al error: error in backend: SSE register return with SSE disabled
> *** Error code 1
>
> in lib/libcompiler_rt.
>
> cheers.
> alex
>
I do not remember instructing anyone to do what you did.
--
Alexander Kabaev
signature.asc
Description: PGP signature
de
> formatting. So do we still have vgrind(1) users out there?
>
> Regards,
> Uli
Why it needs to be in bootsrap tools at all? We have build tools for
this exact purpose.
--
Alexander Kabaev
signature.asc
Description: PGP signature
On Thu, 20 Jan 2011 17:11:13 -0800
Marcel Moolenaar wrote:
>
> On Jan 20, 2011, at 12:31 PM, Alexander Kabaev wrote:
>
> > On Thu, 20 Jan 2011 21:17:40 +0100
> > Ulrich Spörlein wrote:
> >
> >> Hello,
> >>
> >> Currently our buildworld
On Thu, 20 Jan 2011 23:11:43 +0100
Ulrich Spörlein wrote:
> On Thu, 20.01.2011 at 15:31:03 -0500, Alexander Kabaev wrote:
> > On Thu, 20 Jan 2011 21:17:40 +0100
> > Ulrich Spörlein wrote:
> >
> > > Hello,
> > >
> > > Currently our b
On Sat, 29 Jan 2011 13:21:44 -0500
Alexander Kabaev wrote:
> On Sat, 29 Jan 2011 13:02:24 -0500 (EST)
> Daniel Eischen wrote:
>
> > On Sat, 29 Jan 2011, Alexey Shuvaev wrote:
> >
> > > Hello!
> > >
> > > It seems www/seamonkey2 is bro
the shared
> library (libxpcom_core.so), but they are not.
>
My wild guess: seamonkey tries to hide symbols that are coming from
different .o file (this time one from libiconv.a) and that fails with
our toolchain.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20218
--
Alexander Kabaev
signature.asc
Description: PGP signature
4 /usr/local/lib/libiconv.so -> libiconv.so.3 -r--r--r-- 1 root
> wheel 1078567 Jan 27 13:14 /usr/local/lib/libiconv.so.3
>
> I'm not so lame :)
>
> On Sat, Jan 29, 2011 at 01:39:15PM -0500, Alexander Kabaev wrote:
> > On Sat, 29 Jan 2011 13:21:44 -0
.
% sudo dtrace -l -f acl
ID PROVIDERMODULE FUNCTION
NAME
1840 dtmalloc acl malloc
1841 dtmalloc act free
--
Alexander Kabaev
signature.asc
Description: PGP signature
that decision.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Fri, Jul 18, 2003 at 07:07:55PM +0200, Michael Nottebrock wrote:
Content-Description: signed data
> On Friday 18 July 2003 18:14, Alexander Kabaev wrote:
>
> > Configure ailing due to warnings is a real bug.
>
> What do you mean now? Configure is not failing because of warning
hough merge
conflicts in texi files after each import is hardly my idea of
fun, but I will not stop you for trying :)
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, se
I am about to import an official GCC 3.3.1-release into our
source tree. Please hold your updates until 'all clear' message
is posted.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
On Thu, Aug 21, 2003 at 07:55:00PM -0700, Alexander Kabaev wrote:
> I am about to import an official GCC 3.3.1-release into our
> source tree. Please hold your updates until 'all clear' message
> is posted.
Done.
___
[EMAIL PROTECTED
urces in
/usrc/contrib/{gcc|libstdc++|libf2c|libobjc} is all you need.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ere's a better way of
> resolving this. Thanks.
>
ld is not supposed to pull in anything except what was given to it on
the command line. Why your build tries to use LD where it should be
using CC is a separate question though...
--
Alexander Kabaev
__
sync() at ffs_sync+0x24f
> sync() at sync+0xdb
> syscall() at syscall+0x320
> Xfast_syscall() at Xfast_syscall+0xa7
> --- syscall (36, FreeBSD ELF64, sync), rip = 0x402084, rsp =
> 0x7648, rbp = 0x3 --- db>
Known and being looked at.
--
Alexander Kabaev
___
cal/include comes from. If I remove that it
> compiles smoothly.
Uhm, from you command line? What _this_ has to do with a compiler?
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Thu, 6 Nov 2003 17:44:59 +0100
Marius Strobl <[EMAIL PROTECTED]> wrote:
> This happens with g++ 3.x ...
This will happen with g++ 3.x, 2.x, 1.x and future 4.x too. I.e. the
GCC is not at fault and the subject of the original message is
misleading.
--
Alexand
. Unortunately,
some of these fixes did not make into GCC 3.3.3-release,
hence the snapshot.
This will take about two hours, please hold your updates
until an 'all clear' message is posted here.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing
On Thu, Nov 06, 2003 at 06:19:40PM -0800, Alexander Kabaev wrote:
>
> This will take about two hours, please hold your updates
> until an 'all clear' message is posted here.
Done.
___
[EMAIL PROTECTED] mailing list
http://lists.
ld cause invalid code which will be removed
> with the patch for this bug.
>
Sure,
I'll let the system to settle after last snapshot as it is still not
clear whether or not it has broken anything.
--
Alexander Kabaev
___
[EM
BSD Unix files containing
it is hereby deleted in its entirety.
William Hoskins
Director, Office of Technology Licensing
University of California, Berkeley
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/fre
hat changes
anything?
--
Alexander Kabaev
signature.asc
Description: PGP signature
ort)?
It used to possible, but people who did the work to support ICC dropped
any support for their work the minute changes hit the tree and now it
is impossible to say how far exactly it has rotten.
--
Alexander Kabaev
signature.asc
Description: PGP signature
GCC import on my
memory. Every single major GCC release has claimed better optimizations
and more compact generated code and yet they all inevitably generated
code which was appreciably bigger than code produced by previus GCC
version. This should not be used as an excuse to hold clang at bay,
provided base src still comes with working way for building the working
boot2 image (gcc).
--
Alexander Kabaev
signature.asc
Description: PGP signature
possible to compile
> -CURRENT by GCC 2.95.x in the way it has to be. Buildkernel is
> broken in several places by different means, however GCC 3.2.x
> passes them successfully, even with no warnings shown.
>
> Thank you for reading!
>
> ---
> Regards,
> Rhett
--
Alexan
On Tue, 27 May 2003 10:49:40 -0500
David Leimbach <[EMAIL PROTECTED]> wrote:
>
> On Tuesday, May 27, 2003, at 10:40AM, Alexander Kabaev <[EMAIL PROTECTED]>
> wrote:
>
> >On Tue, 27 May 2003 10:32:42 -0500
> >David Leimbach <[EMAIL PROTECTED]> wrote:
&
On Sun, 1 Jun 2003 11:26:12 +0200 (CEST)
Martin Blapp <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I just got this panic during compile of openoffice
>
> Fatal trap 12 while in kernel mode
> fault virtual address = 0x68
> fault code= supervisor read, page not present
> instruction poi
; differently?
>
> Pete
Got your buildworld log saved somewhere? Could you send it to me please.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> I suggest that the original poster double-check that he has RELENG_5_1
> and not HEAD. And I do have buildworld logs. I'll send in a separate
> mail.
No need that. This is a bug and it needs to be fixed. I am working on
this. Thanks for the reports.
--
Alexander Kabaev
On Tue, 10 Jun 2003 02:50:27 +0100
Bruno Afonso <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm using -current from monday and I'm having a lot of crashes on my
> athlon 2.4+. So far, I've had to stop using it with mozilla 1.4b,
> FireBird and now it seems to crash pymol too. (python based)
> I thi
able in GCC 3.3+ only. The new compiler is
likely to enter the tree at the end of this month/first week of June.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ween FreeBSD kernel internals and Irix interfaces which
arguably can be traced to common Unix roots of both systems. SCO might
consider XFS theirs some day :)
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
as deprecated in favor of sys/types.h:
$ find /usr/include -name types.h
/usr/include/rpc/types.h
/usr/include/sys/types.h
Your /usr/include dir contains stale files.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ck on.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_all_
previous releases.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Wed, 09 Jul 2003 15:26:40 -0600 (MDT)
"M. Warner Losh" <[EMAIL PROTECTED]> wrote:
> In message: <[EMAIL PROTECTED]>
> Alexander Kabaev <[EMAIL PROTECTED]> writes:
> : GCC 3.3+ will be a system compiler throughout RELENG_5 lifetime.
>
>
On Wed, 9 Jul 2003 17:09:56 -0400
Alexander Kabaev <[EMAIL PROTECTED]> wrote:
> Unfortunately, importing a newer GCC means that we'll have yet another
> ABI breakage on our hands.
^^^
This should read 'API breakage'. GCC 3.3 is supposed to be binary
compatible
Sorry for false alarm. There is one more last-minute change I am not
comfortable committing without some more test.
It is official - the import is going to happen tomorrow. I promise... :)
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http
Due to unforeseen circumstances the new compiler import scheduled
for today is not going to happen. I will complete it tomorrow once
yet another round of testing is complete.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http
I'll be importing a GCC 3.3.1 snapshot in a couple of minutes.
Please hold your updates until I post 'all clear' message.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
All of these failures are caused by incomplete compiler import.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Thu, Jul 10, 2003 at 08:15:48PM -0700, Alexander Kabaev wrote:
> I'll be importing a GCC 3.3.1 snapshot in a couple of minutes.
> Please hold your updates until I post 'all clear' message.
OK, things are in somewhat working shape back again. The world/kernel
builds on
w and will keep you posed on progress.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
=2400
+
CFLAGS+= ${DEBUG_FLAGS}
OBJS+= ${SRCS:N*.h:R:S/$/.o/g}
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Fri, 11 Jul 2003 14:32:44 -0400
Alexander Kabaev <[EMAIL PROTECTED]> wrote:
> May be I am paranoid, but could you people please make sure you have
> removed /usr/src/sys/i386/compile/ before rebuilding a
> new kernel with GCC 3.3?
>
I forgot to add: both my test boxes are
Out of curiosity: do you have any non-standard CPUTYPE set?
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
Bull's eye! Peter has identified this problem already and hopefully will
be committing a patch soon.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sat, 12 Jul 2003 06:08:57 +0400
Sergey Matveychuk <[EMAIL PROTECTED]> wrote:
> Don't forget bump __FreeBSD_version. :)
>
What for? Bumped __FreeBSD_cc_version is enough.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/fre
we _want_ to know about them. Your Linux distribution
apparently does not care.
>
> Any GCC/FreeBSD expert care to comment? ;)
>
Short of fixing offending files in FSF libstdc++ or turning warning
suppression back on for standard C++ include files selectively, I have
no suggestion.
e with 5.2-current?
Hardly a bug report. Care to shed more details?
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
s/gcc-3.3/ports/ issues and we are in agreement.
Patches to fix broken ports are welcome. Kris is doing a fine job
generating a list of what needs to be fixed with his cluster packabe
building runs.
--
Alexander Kabaev
___
[EMAIL PROTECTED] mailing
On Thu, 17 Jul 2003 14:02:20 -0700
Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> Sorry, I missed the patch in your email. I'm not certain about your
> approach...can someone who understands the issues comment on it?
>
> Kris
>
I'd rather see all varargs.h consumers be converted to stdarg.h. Old
Perhaps you wanted another value from
> >
>http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html
>
> Fear not. I'm modifying the patch. Proper documentation will be
> included.
>
> Joe
--
Alexander Kabaev
To Unsubscribe: send mail
weak the asm statements to make
> things happy? :-)
--
Alexander Kabaev
Index: i386/lockdflt.c
===
RCS file: /usr/ncvs/src/libexec/rtld-elf/i386/lockdflt.c,v
retrieving revision 1.6
diff -u -r1.6 lockdflt.c
--- i386/lockdflt.c
ater today unless I find something wrong with it.
>
> John
>
>
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The last commit to sys/sys/stat.h made by Kirk broke compilation of
_POSIX_SOURCE programs. It uses sizeof(struct timespec) to pad the
st_createtimespec field to 16 bytes, but struct timespec is not visible
when _POSIX_SOURCE is defined.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL
I made the following patch to get C++ exceptions working with
system GCC 3.1. STLPort and all other previously failing
test cases appear to be working fine.
Please test this patch and let me know if it breaks anything.
--
Alexander Kabaev
Index: config/i386/freebsd.h
-pthread
> +# endif
Sheldon,
AFAIK _REENTRANT has to be defined on -CURRENT too.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
nk
it has anything to do with my patch.
Has anyone else tried the patch? Someone who has a backup copy of
important system binaries handy?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
problems with symbol tables or
dynamic linker.
My apologies for [EMAIL PROTECTED]
On Wed, 26 Jun 2002 14:21:17 -0400
Alexander Kabaev <[EMAIL PROTECTED]> wrote:
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
does cause problems with symbol tables or
dynamic linker.
My apologies for [EMAIL PROTECTED]
On Wed, 26 Jun 2002 14:21:17 -0400
Alexander Kabaev <[EMAIL PROTECTED]> wrote:
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
7;m going to sit and
> watch for awhile before going back in the water.
Just booting an older kernel would have solved your problem.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
output, so that majority of output was displayed upon
pkg_version exit.
pkg_version 2>&1 | tee pkg_version.log
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> This is because of the rewrite of pkg_version into C (from perl) and
> has nothing to do with pipes.
>
> Regards,
> -Jeremy
Oops! I forgot about the big perl rewrite. Apologies for false alarm.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
d c++ things aren't found.
This is FAQ. Have you deleted obsolete g++ include files?
Do mv /usr/include /usr/include.old; mkdir /usr/inlcude before making
buildworld.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
wrote:
> > This is FAQ. Have you deleted obsolete g++ include files? Do mv
> > /usr/include /usr/include.old; mkdir /usr/inlcude before making
> > buildworld.
>
> I think I did that but I guess another try couldn't hurt...
>
> Ken
--
Alexander Kabaev
To Unsubsc
s more info
> and fixes a spelling error (*blush*).
Bruce,
I am reliably get these messages while using gdb on user processes. This
started long before KSEIII.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
@@ -190,12 +190,14 @@
}
}
+#if 0
if (i == 0)
{
/* Zero interrupts is invalid! */
return_ACPI_STATUS (AE_BAD_DATA);
}
+#endif
OutputStruct->Data.Irq.NumberOfInterrupts = i;
/*
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL
/sys/kern/kern_timeout.c:187
#18 0xc02198fc in ithread_loop (arg=0xc1593900)
at /usr/src/sys/kern/kern_intr.c:535
#19 0xc0218e1d in fork_exit (callout=0xc0219788 ,
arg=0xc1593900, frame=0xd4a5fd48) at /usr/src/sys/kern/kern_fork.c:861
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL
he VESA mode doesn't work on -stable now either. I knew I
> shouldn't have cvsup'd, with all the problem reports I'm seeing on the
> lists. Dohh! But I just ordered a Dell 8200, so maybe my problems
> will become "different" Rob.
--
Alexander Kabaev
with PAM, AFAIK. Someone has to call PAM session cleanup
hooks, that's why another process for the command is forked.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
This can be related: occasionally top terminates after displaying the
process list only once. Unfortunately, this is hard to reproduce and
when run again top just start working properly.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curren
shots, bypassing the GCC 3.2 version altogether. Early FreeBSD 5.x
release(s) will not be polished for general consumption anyway, so that
makes sense. By the time FreeBSD stabilizes, GCC 3.3 release will be
ready.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
ying to keep C++ ABI compatible between 3.2 and 3.3, but they are
not giving any guaranrtees.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
right? Do you really want to repeat this
deeply satisfying experiment again?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
at
> me.
3.1-pre to 3.2 upgrade breaks compatibility already. Can you guarantee
that 3.3 will be backwards compatible with 3.2? This is yet another
potential ABI breakage at the time when we'll be _forced_ to upgrade.
How often do you expect GCC developers to break ABI with release
scheduled to
1 - 100 of 220 matches
Mail list logo
