On Sat, Dec 08, 2007 at 10:43:41PM +0700, Eugene Grosbein wrote:
On Sat, Dec 08, 2007 at 09:37:12AM -0500, Daniel Eischen wrote:
Please reread my original reply to you. If you are going to be
rebuilding or installing new ports, then you really need to do
a portupgrade -af. The same thing
On Sat, 8 Dec 2007, Eugene Grosbein wrote:
On Sat, Dec 08, 2007 at 01:09:47PM +0700, Eugene Grosbein wrote:
Thank you. Now I wonder, how such thing may happen
if qemu was built under 6.2 where there were no
libthr.so.3 and libc.so.7?
Most likely, you have rebuilt some library that brough in
On Sat, Dec 08, 2007 at 09:37:12AM -0500, Daniel Eischen wrote:
Please reread my original reply to you. If you are going to be
rebuilding or installing new ports, then you really need to do
a portupgrade -af. The same thing may happen again for some
other library.
I know. I will never
[cc line trimmed]
In message [EMAIL PROTECTED], Eugene Grosbein
[EMAIL PROTECTED] writes
I know. I will never 'rebuild all ports', I don't think that's Right Thing.
I've upgraded once from 4.11-STABLE to 6.0-RELEASE (binary upgrade
over existing system) and all ports worked nice, including X,
David Wood wrote:
[cc line trimmed]
*useful but already posted details trimmed*
Agree the need to keep ports (and everything) as current as is practical.
Rebuilding frequently is unavoidable.
portupgrade -af can be somewhat painful on systems with plenty of ports
installed.
But
[ Library incompatiblity problems between major FreeBSD releases ]
One of the things that should make life a little easier in
FreeBSD 7.0 and subsequent (-current, 8.x, etc) is that we
now have symbol versioning in some of our libraries. The
libraries that have caused the most problems in the
David Wood [EMAIL PROTECTED] wrote:
It's your choice, but from a security perspective, this worries me.
You will have applications you are using linked against FreeBSD
libraries that no longer have any FreeBSD security team support.
[skip]
The definite need to keep the system secure is
Eugene Grosbein wrote:
David Wood [EMAIL PROTECTED] wrote:
It's your choice, but from a security perspective, this worries me.
You will have applications you are using linked against FreeBSD
libraries that no longer have any FreeBSD security team support.
[skip]
The definite need to keep
On Sat, Dec 08, 2007 at 07:41:04PM +, ? Bill Hacker wrote:
The ability to build from source and have access to source, is prized among
the experienced not so much because we fear hidden 'gotcha's from the
malicious or even proprietary vendor lock-in - but more for the ability to
Eugene Grosbein wrote:
On Sat, Dec 08, 2007 at 07:41:04PM +, ? Bill Hacker wrote:
Deal with that as best you can. ELSE revert to the last century and run
Windows.
Thank you for suggestion. I run dual-boot FreeBSD/Windows system
as my desktop for many years.
Eugene Grosbein
On Fri, 7 Dec 2007 22:48:52 +0700 Eugene Grosbein wrote:
There is FreeBSD box that was 6.2-STABLE before, now it became
7.0-BETA3 via source upgrade. The kernel has 'options COMPAT_FREEBSD6'
How did you upgrade the OS? Did you use make delete-old-libs?
Did you install compat-6x?
compiled in.
Hi!
There is FreeBSD box that was 6.2-STABLE before, now it became
7.0-BETA3 via source upgrade. The kernel has 'options COMPAT_FREEBSD6'
compiled in. However, qemu-0.8.2s.20061225_1 stopped to work,
it dumps core when started with an error:
Fatal error 'Cannot allocate red zone for initial
On Sat, Dec 08, 2007 at 01:09:47PM +0700, Eugene Grosbein wrote:
Thank you. Now I wonder, how such thing may happen
if qemu was built under 6.2 where there were no
libthr.so.3 and libc.so.7?
Most likely, you have rebuilt some library that brough in the dependencies.
Check with
On Sat, Dec 08, 2007 at 11:22:52AM +0700, Eugene Grosbein wrote:
On Fri, Dec 07, 2007 at 11:52:54AM -0500, Daniel Eischen wrote:
You have to either rebuild/install _no_ ports, or rebuild _all_
ports (portupgrade -af). You now seem to have applications
or libraries that are linked to
On Sat, Dec 08, 2007 at 08:02:06AM +0200, Kostik Belousov wrote:
libpthread.so.2 = /lib/libpthread.so.2 (0x481f5000)
RELENG_6 libpthread
libc.so.6 = /lib/libc.so.6 (0x4821c000)
RELENG_6 libc
[skip]
libthr.so.3 = /lib/libthr.so.3 (0x48546000)
On Sat, Dec 08, 2007 at 07:45:52AM +0200, Kostik Belousov wrote:
But I do not see this:
# ldd `which qemu`
/usr/local/bin/qemu:
[skip]
libpthread.so.2 = /lib/libpthread.so.2 (0x481f5000)
RELENG_6 libpthread
libc.so.6 = /lib/libc.so.6 (0x4821c000)
RELENG_6 libc
[skip]
On Sat, Dec 08, 2007 at 12:55:37PM +0700, Eugene Grosbein wrote:
On Sat, Dec 08, 2007 at 07:45:52AM +0200, Kostik Belousov wrote:
But I do not see this:
# ldd `which qemu`
/usr/local/bin/qemu:
[skip]
libpthread.so.2 = /lib/libpthread.so.2 (0x481f5000)
RELENG_6
There is FreeBSD box that was 6.2-STABLE before, now it became
7.0-BETA3 via source upgrade. The kernel has 'options COMPAT_FREEBSD6'
How did you upgrade the OS? Did you use make delete-old-libs?
Did you install compat-6x?
No, I've tried now: install compat-6x port and ran make
On Fri, Dec 07, 2007 at 11:52:54AM -0500, Daniel Eischen wrote:
You have to either rebuild/install _no_ ports, or rebuild _all_
ports (portupgrade -af). You now seem to have applications
or libraries that are linked to multiple FreeBSD library versions
(e.g., libc.so.6 and libc.so.7,
On Fri, 7 Dec 2007, Boris Samorodov wrote:
On Fri, 7 Dec 2007 22:48:52 +0700 Eugene Grosbein wrote:
There is FreeBSD box that was 6.2-STABLE before, now it became
7.0-BETA3 via source upgrade. The kernel has 'options COMPAT_FREEBSD6'
How did you upgrade the OS? Did you use make
20 matches
Mail list logo
