Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)
David Benfell
I have tried rebuilding ports numerous times, and I can't seem to get rid
of this error:
Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)
I can't even get into X (xfce-session is affected) and now the problem seems
to be spreading, affecting lynx.
I have a couple questions here. First, if I understand correctly, this error
indicates that I have binaries linked against two versions of a threading
library. How can this not be a bug in the port/build configuration? Second,
how do I make this go away? Third, I have a lot of ports that won't build;
how do I fix this?
A considerable amount of information about the system--everything I could
think of that might be relevant--is available at:
<http://www.parts-unknown.org/systems/earth.cybernude.org/>
Look in the .html file for more than just a list of packages.
Thanks!
--
David Benfell, LCP
ben...@parts-unknown.org
---
Resume available at http://www.parts-unknown.org/
NOTE: I sign all messages with GnuPG (0DD1D1E3).
Kris Kennaway
> Hello all,
>
> I have tried rebuilding ports numerous times, and I can't seem to get rid
> of this error:
>
> Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)
>
> I can't even get into X (xfce-session is affected) and now the problem seems
> to be spreading, affecting lynx.
>
> I have a couple questions here. First, if I understand correctly, this error
> indicates that I have binaries linked against two versions of a threading
> library. How can this not be a bug in the port/build configuration? Second,
> how do I make this go away? Third, I have a lot of ports that won't build;
> how do I fix this?
>
> A considerable amount of information about the system--everything I could
> think of that might be relevant--is available at:
>
> <http://www.parts-unknown.org/systems/earth.cybernude.org/>
>
> Look in the .html file for more than just a list of packages.
>
> Thanks!
>
portupgrade -fa
Kris
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
David Benfell
>
> portupgrade -fa
>
Tried that. Several times. And the portmaster and portmanager
equivalents. It looks like I would have to manually rebuild each of
over 1000 ports I have installed to restore functionality.
In many cases, even this won't work, however, as 'make fetch' returns
some error about dates mismatching. Or, less commonly, there are
other problems in the build.
But to demonstrate this, I will initiate a job with the following
command:
sudo portupgrade -fa | tee parts-unknown.org/systems/earth.cybernude.org//portupgrade-fa.log
You can see the output at http://www.parts-unknown.org/systems/earth.cybernude.org/portupgrade-fa.log
Problems are widespread and it seems unreasonable to blame individual
ports for many of them.
Doug Barton
Hash: RIPEMD160
On Tue, 6 Nov 2007, David Benfell wrote:
> On Mon, 05 Nov 2007 23:33:14 +0100, Kris Kennaway wrote:
>>
>> portupgrade -fa
>>
> Tried that. Several times. And the portmaster and portmanager
> equivalents. It looks like I would have to manually rebuild each of
> over 1000 ports I have installed to restore functionality.
Sorry I missed the beginning of this thread, but it sounds to me like
you're trying to upgrade ports after a FreeBSD major version upgrade? If
so, the only safe way to do that is to delete all your existing ports, and
start over from scratch. The procedure I use is:
1. portmaster -l > ~/portmaster-list
2. pkg_delete -f * (repeat as necessary)
3. find /usr/local/ -type f This should produce very little output,
except in etc. Clean up as needed.
4. Install portmaster :)
5. Look at the list generated in 1, and first install all the root ports,
then install all the leaves. Portmaster will handle the dependencies.
Given that you seem to be having problems with stale distfiles as well you
might want to insert a step 4.5 of 'rm -rf /usr/ports/distfiles/*' but I'd
only do that as a last resort.
hth,
Doug
- --
This .signature sanitized for your protection
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (FreeBSD)
iD8DBQFHMN4zyIakK9Wy8PsRA6Q2AKDsGcF0ETdKwQPeYSGPPQ/szlnEqACeJHC+
xR+BFIwCQvominhEocAq+JI=
=l3w3
-----END PGP SIGNATURE-----
Kris Kennaway
> On Mon, 05 Nov 2007 23:33:14 +0100, Kris Kennaway wrote:
>> portupgrade -fa
>>
> Tried that. Several times. And the portmaster and portmanager
> equivalents. It looks like I would have to manually rebuild each of
> over 1000 ports I have installed to restore functionality.
>
> In many cases, even this won't work, however, as 'make fetch' returns
> some error about dates mismatching. Or, less commonly, there are
> other problems in the build.
>
> But to demonstrate this, I will initiate a job with the following
> command:
>
> sudo portupgrade -fa | tee parts-unknown.org/systems/earth.cybernude.org//portupgrade-fa.log
>
> You can see the output at http://www.parts-unknown.org/systems/earth.cybernude.org/portupgrade-fa.log
>
> Problems are widespread and it seems unreasonable to blame individual
> ports for many of them.
You have stale or corrupted distfiles for some of them, but I didn't
spot any other problems there. Obviously the ports that fail to rebuild
will still be 6.x binaries and causing problems, so you should only be
declaring victory once you manage to get them all recompiled
successfully. It seems like this has not yet happened.
To address the old distfiles, either use 'make distclean' on those
ports, or rm -rf /usr/ports/distfiles and allow them to be fetched anew.
If you are having problems recompiling other specific ports, please
follow up on ports@.