Solaris does not do that
and then saying 'NO' again to description on how Solaris really does
things - that's where I lost you.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
libc_r linked libraries into non-threaded processes din't
work ever since libc_r got split from libc. This is a weird case which
does not happen a lot in the wild anyway.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to
specfs_vnops.c. Find a block in specfs_strategy function which goes into
tsleep for niced processes and comment it out. Let us know if that helps
:)
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
provided by the system.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Anyone cares to post a ktrace?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, 22 Oct 2002 11:39:43 -0400
Alexander Kabaev [EMAIL PROTECTED] wrote:
Anyone cares to post a ktrace?
--
Alexander Kabaev
If this is a case of a brk(2) failing, then I have a patch in testing to fix
that. Give me some time to finish.
--
Alexander Kabaev
To Unsubscribe: send mail
.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
libstdc++ is supposed to provide crude replacements for missing -l functions
in its libmath/stubs.c file. Apparently, missing fabsl is an omission and
should be fixed in FSF sources.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
I hope this problem is fixed now. Let me know if I am sadly mistaken
about that :)
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, 18 Oct 2002 08:00:19 -0700
walt [EMAIL PROTECTED] wrote:
I suppose I need to build emacs with debugging enabled?
Any hints how to do that?
Anyone else seeing this problem?
xemacs dies here. Global variables are getting corrupted somehow during
startup.
--
Alexander Kabaev
please try to compile libmsun with with GCC 3.3 snapshot David
just committed and see if that changes anything?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I am going to import a new GCC 3.2.1 snapshot in about 10 minutes. This
update fixes the problem with cpp0 dumping core while building a kernels
many people reported on the list.
Due to popular demand, it was decided to do another import today.
--
Alexander Kabaev
To Unsubscribe: send mail
On Thu, 10 Oct 2002 00:13:04 -0400
Alexander Kabaev [EMAIL PROTECTED] wrote:
I am going to import a new GCC 3.2.1 snapshot in about 10 minutes.
This update fixes the problem with cpp0 dumping core while building a
kernels many people reported on the list.
Due to popular demand
/gcc-cpp.diff.
Will be fixed with new GCC import.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
death in approximate first 20 minutes.
--
Andrey A. Chernov
http://ache.pp.ru/
I can confirm this. CVSUP is dying on me exactly the same way Andrey
describes. XFree86 dies with signal 6 too.
Both run reliably when I downgrade i386/machdep.c to rev. 1.358.
--
Alexander Kabaev
To Unsubscribe
.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
. The bug is there and it is triggered by -march={athlon|p[234]}.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
? URL is the same
http://people.freebsd.org/~kan/gcc-cpp.diff
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
?
You might want to do a make clean in /usr/src/gnu/usr.bin/cc before
building a new copy of gcc.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
still see the same segmentation
fault. Alexander, how can I easily build gcc with full debugging
symbols? That might make the backtrace more useful for you.
cd /usr/src/gnu/usr.bin/cc
CFLAGS=-g STRIP= make clean all install
Always worked for me.
--
Alexander Kabaev
To Unsubscribe: send
get past that
initial mkdep.
By adding or removing configuration options, you change the exact layout
of the string buffer in CPP0 and this prevents crash from happening.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
your complaints here. Some help finding the offending function
and providing people with additional information will come a long way
toward having this bug finally fixed. Please consult
http://gcc.gnu.org/bugs.html for instructions if you decide to do so.
--
Alexander Kabaev
To Unsubscribe: send
appears to be more
correct.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
for that.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sun, 22 Sep 2002 17:20:14 +0200
Alexander Leidinger [EMAIL PROTECTED] wrote:
Alexander, can you get me a backtrace from the failed GCC process? What
process it is, by the way? GCC, CC1, CPP1?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
the event. If anything, this should give you the name of the
process which has died. Running 'gcc' or 'c++' under debugger is not
very helpful, because these are just driver programs. The real processes
which do the work are cpp1, cc1, ccp1 etc.
--
Alexander Kabaev
To Unsubscribe: send mail
.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I am asking people having CPP0 dying with SIG11 to try the patch at URL
below. Success/failure reports are appreciated.
http://people.freebsd.org/~kan/gcc-cpp.diff
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
help you can provide.
Kris
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
I will take a look at these.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
://people.freebsd.org/~kan/gcc-all.diff.
People having problems compiling their problems with the new
system compiler are encouraged to give this patch a try and
let me know if their problem is fixed ot not.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
On Tue, 3 Sep 2002 04:23:39 -0700 (PDT)
Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:
=== usr.bin/getconf
Virtual memory exhausted in `operator new'
*** Error code 1
This one I can reproduce. Will fix soon.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED
On Tue, 3 Sep 2002 16:56:52 +0200
Bernd Walter [EMAIL PROTECTED] wrote:
Do you think this is the same reason?
Yes.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
The patch is not mine.
I extracted it from GCC FSF CVS repository.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
aout binaries and compatibility cruft
to support old binaries should have been dropped too.
Do we have an agreement here? A.OUT support is to be dropped with the
next gcc upgrade, when/if it will happen?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
On Mon, 2 Sep 2002 08:52:56 -0700
Steve Kargl [EMAIL PROTECTED] wrote:
O -pipe -march=athlon
^^
This bug is in GCC PR database. Do not use -march=athlon for now.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
BTW, the bug is present in official 3.2 release too.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
time they reallocate their 'string_space' to accomodate
(n+1)th entry.
Building gmake without --with-included gettext sugddenly seems like a
very good idea for me.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, 2 Sep 2002 13:06:31 -0400
Alexander Kabaev [EMAIL PROTECTED] wrote:
Do they really believe malloc
^^^ I meant realloc here.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, 2 Sep 2002 11:10:11 -0700
David O'Brien [EMAIL PROTECTED] wrote:
On Mon, Sep 02, 2002 at 12:08:41PM -0400, Alexander Kabaev wrote:
BTW, the bug is present in official 3.2 release too.
What about 3.1.1 release?
I have GCC 3.1.1 port installed on STABLE. libiconv barf when compiled
completes fine on panther, the only FreeBSD sparc64 machine I
have access to.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
The complete transcript is available here:
http://sparc64.style9.org/sparc64.log
Which still does not answer my question. What GCC version is on this
machine?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
if_convert optomization.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
The patch I sent is reversed. Use patch -R to apply.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Where can I find this patch? I didn't see it in the message body or attached to any
of your previous messages.
Sorry,
apparently attachments are stripped now before being delivered
to the mailing lists. The patch is below:
Index: cp/cp-lang.c
that I need to hold the import
for some reason.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
is using vendor-independent C++ ABI. Assuming they got it right
this time, this will allow us to upgrade to 3.3 more painlessly later.
People who were asking for an upgrade got what they deserved :)
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
in?
About five buildworlds on i386 and two on Alpha. Does that count as dry
runs?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
GCC 3.2.1-pre is now in the tree. Please let me know if you see any
problems recompiling your world/kernel.
Remember to recompile your C++ ports. GCC 3.2 is not binary compatible
with 3.1.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
do not remember me switching thunks off.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
,
^^
There are no such files in gcc 3.1, AFAIK.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
There are, but they are in:
/usr/include/g++/backward/iostream.h
/usr/include/g++/backward/strstream.h
They are in different place = they are different. Alexander, remove
/usr/include/g++ before your next installworld.
This is FAQ.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL
/usr.sbin/pkg_install/version/main.c:79
#4 0x08049879 in _start ()
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Hi Josef,
On Mon, 19 Aug 2002 13:22:52 +0100
Josef Karthauser [EMAIL PROTECTED] wrote:
Is it just me or is libstdc++ linking broken on -current right now?
Remove /usr/include/g++ before making your next installworld.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED
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 unsubscribe freebsd-current
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
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
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 happed and the end of the year?
--
Alexander Kabaev
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-current
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
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
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
/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 ithread_loop,
arg=0xc1593900, frame=0xd4a5fd48) at /usr/src/sys/kern/kern_fork.c:861
--
Alexander Kabaev
To Unsubscribe: send
)
{
/* Zero interrupts is invalid! */
return_ACPI_STATUS (AE_BAD_DATA);
}
+#endif
OutputStruct-Data.Irq.NumberOfInterrupts = i;
/*
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
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
.
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
:
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 Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
output, so that majority of output was displayed upon
pkg_version exit.
pkg_version 21 | 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 unsubscribe freebsd-current
_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
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 the body of the message
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
constraints
are allowed only for registers. But read-modify-write operands can
still be specified in other ways, specifically using the +
modifier. Here's the patch which I'm testing at the moment. I'll
commit it later today unless I find something wrong with it.
John
--
Alexander Kabaev
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
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 17 Jul 2000
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 to [EMAIL PROTECTED]
with unsubscribe freebsd-current
?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to track down what older library shadows the new one. The usual suspects
are libgcc and libstdc++.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Thanks Bruce. It sounds like we'll have to live with this problem for now?
For the lack of better ideas, I am just reposting the patch I sent to
Bruce about one year ago. I have been happily using it on all my systems
since then.
Index: su.c
programs.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Serial console and remote GDB were working just fine for me ever since
that entry has been added to the task SMPng unresolved issues list.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
:
On 10-May-2002 Alexander Kabaev wrote:
Serial console and remote GDB were working just fine for me ever
since that entry has been added to the task SMPng unresolved issues
list.
At 115200?
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power
Calling freeenv with the pointerm different from one received from
getenv seldom is a good idea :) Indeed, CURRENT panics with the
following stack trace (patch below fixes that):
_mtx_lock_sleep(c08300e4,0,c03644b1,649,c08300e4) at
_mtx_lock_sleep+0x122
Apologies if you will get this message twice. My ISP seems to be
blocked in hub.freebsd.org so I had to use temporary hotmail account.
I found the reason for crashes I was experiencing ever since UMA has
been committed into -CURRENT. Apparently UMA has nothing to do with the
breakage.
You could add one, it would be trivial to add a TAILQ_ENTRY to the
vnode strcture as well as add/remove the nodes from
the list in the vnode allocation and deallocation code.
I was thinking about mp-mnt_nvnodelist, unless there are compelling
reasons not to trust it.
Feel ambitious? :)
Feel like
This is a case of exception context register getting clobbered in
shared library function call. GCC does not reload it when needed and
this ultimately leads to semi-random word in program memory decremented
by the __cp_pop_exception function. The bug is only triggered under very
specific
This is a case of exception context register getting clobbered in
shared library function call. GCC does not reload it when needed and
this ultimately leads to semi-random word in program memory decremented
by the __cp_pop_exception function. The bug is only triggered under very
specific
Do you have a patch for this ?
I do not fully understand the parts of GCC involved, so I need some
time to verify my initial diagnosis and to create a patch. In other
words - not yet :)
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
2) Bug is in os delivered gcc but not in port gcc.
a) port has more or less patches / os gcc has been modified
-- Didn't someone told they are the same?
GCC from ports uses DWARF2 exception unwinding while GCC in src tree
uses sjlj exceptions. The exception handling code generated by
The stack trace below shows exactly the symptoms of the binutils
DT_TEXTREL bug, which has been fixed by the latest vendor import.
Rebuilding world IS NOT ENOUGH to solve the problem. You will need to
rebuild all the incorrect libraries which have been built with broken
binutils before. Libpng
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 computer.
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
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 the
101 - 200 of 204 matches
Mail list logo
