On Wed, 11 Jul 2001 at 23:36, Horatio B. Bogbindero wrote:
> this does not look good. i have been using my gcc-3.0 build for about
> a week and a little more.
Until that fateful segfault (that persists until now) I had used gcc-3.0
to build a couple of kernels that worked really great. I downgraded to
gcc-2.95.4 and things seem to be working fine again. I will wait until an
upgrade to gcc-3.0 is available in Debian's unstable before further
testing. I am hoping to be able to get an update so that I can use gcc-3.0
again soon. :)
> no segfaults yet. why not build it from source? maybe be a library
> problems because 2.95.3, 2.96, 3.0 have different libstdc++ abi's this
> means that there cannot be binary compatibility among them. this may
> not be the problem but it could be.
This could be it ... but I was running the gcc-3.0 built kernels and
things were working until that segfault. Unfortunately the libstdc of
Debian's unstable is only for 2.95.4. There are developmental libraries
and the libgcc1 package for 3.0 but I think most packages still depend on
the older libraries. I'm sure in time these will upgrade, though, so for
now I'm holding my horses and using 2.95.4. :)
> jijo is leaving debian? hmmm..... but not back to redhat i presume.
That was a cry of desperation. I tried Mandrake 8.0 and unfortunately do
not like its gooeyness. FreeBSD looks attractive but I can't leave the
journalling filesystems available for Linux (ReiserFS for stuff like the
Squid cache and the root filesystem and XFS for the home directories and
other network-shared partitions).
So now I'm back to loving Debian. ;>
--> Jijo
--
Federico Sevilla III :: [EMAIL PROTECTED]
Network Administrator :: The Leather Collection, Inc.
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
