[gentoo-user] Re: glibc-2.17 fails and warning: setlocale: LC_ALL error

[gentoo-user] Re: glibc-2.17 fails and warning: setlocale: LC_ALL error

[((RayDar))]

Hello,

I think I can offer some some more clues to the problem in thread started by 
Dale, as archived here:
https://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg147315.html

I too get the "Your old kernel is broken.  You need to update it to a newer 
version as syscall(<bignum>) will break." message whenever I try to emerge 
glibc-2.17. This happens on all three of my machines, which are kept up to 
date and have slightly different configurations. It is likely that many people 
are in a broken state, but they don't know it because they haven't tried re-
emerging glibc.

Previously in this thread, I see that Hinnerk van Bruinehsen asked:

> Can you run;

 > printf "#include <unistd.h>\n#include <sys/syscall.h>\nint main(){return \
 > syscall(1000)!=-1;}\n" > syscall.c && make syscall && ./syscall && echo $? 

When I try this on each of my systems, I get the same output:

cc     syscall.c   -o syscall

Notice that the line with the 0 is missing.

I found a work around: move to an earlier kernel. This problem happens for me 
on kernel-3.14.14 and for Dale on kernel-3.15.5. But, it DOESN'T happen for me 
on 3.12.21-r1.

When I boot into the 3.12.21-r1 kernel, the printf() above outputs:

cc     syscall.c   -o syscall
0

as it should.

Could the emerge glibc fail be due to a required kernel configuration option 
that didn't make it into 3.14.14 or above?

[gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

Howdy,

I'm reinstalling Gentoo on my OLD rig.  It's x86.  I have two issues
which will be seen in the error below.  Sort of hard to miss.  Anyway, I
started with the latest stage3 tarball.  I've got it to where it boots
up and all and am in the process of trying to do a emerge -e system
which will also update everything as well.  My problem is glibc and the
locale settings.  May be a separate issue or related.  Here is the boo
boo. 

localhost linux # emerge -v glibc
sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)

 * IMPORTANT: 5 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-libs/glibc-2.17:2.2  USE="-debug -gd (-hardened)
(-multilib) -nscd -profile (-selinux) -suid -systemtap -vanilla" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB

>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-libs/glibc-2.17
>>> Failed to emerge sys-libs/glibc-2.17, Log file:
>>>  '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'
>>> Jobs: 0 of 1 complete, 1 failed                 Load avg: 0.16,
0.39, 1.44
 * Package:    sys-libs/glibc-2.17
 * Repository: gentoo
 * Maintainer: toolchain@gentoo.org
 * USE:        abi_x86_32 elibc_glibc kernel_linux userland_GNU x86
 * FEATURES:   preserve-libs sandbox
[sys-libs/glibc-2.17] bash: warning: setlocale: LC_ALL: cannot change
locale (en_US.UTF8)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale
(en_US.UTF8)  <<-- This error right here. :-( 
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
make -j3 -s glibc-test
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
make -j3 -s glibc-test
 * Your old kernel is broken.  You need to update it to
 * a newer version as syscall(<bignum>) will break.
 * http://bugs.gentoo.org/279260
 * ERROR: sys-libs/glibc-2.17::gentoo failed (setup phase):
 *   keeping your system alive, say thank you
 *
 * Call stack:
 *           ebuild.sh, line  93:  Called pkg_setup
 *   glibc-2.17.ebuild, line 151:  Called eblit-run 'pkg_setup'
 *   glibc-2.17.ebuild, line 137:  Called eblit-glibc-pkg_setup
 *     pkg_setup.eblit, line  75:  Called die
 * The specific snippet of code:
 *                      die "keeping your system alive, say thank you"
 *
 * If you need support, post the output of `emerge --info
'=sys-libs/glibc-2.17::gentoo'`,
 * the complete build log and the output of `emerge -pqv
'=sys-libs/glibc-2.17::gentoo'`.
 * The complete build log is located at
'/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-libs/glibc-2.17/temp/die.env'.
 * Working directory: '/usr/lib/portage/pym'
 * S: '/var/tmp/portage/sys-libs/glibc-2.17/work/glibc-2.17'
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
 *
 * The following package has failed to build or install:
 *
 *  (sys-libs/glibc-2.17::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'
 *
localhost linux #


One reason I want to re-emerge glibc, I'm HOPING it will fix the other
LC_ALL error.  I'm pretty sure glibc takes care of that but not 100%
sure.  I checked my main rig for differences in USE flags, multilib is
the only one I see.  It is set on my main rig and doesn't seem to be
available on x86 for obvious reasons. 

If this is not enough info, let me know what you need.  I don't want to
flood with tons of unneeded info when usually that above gives enough of
a hint.  ;-) 

Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

Dale wrote:
> Howdy,
>
> I'm reinstalling Gentoo on my OLD rig.  It's x86.  I have two issues
> which will be seen in the error below.  Sort of hard to miss.  Anyway, I
> started with the latest stage3 tarball.  I've got it to where it boots
> up and all and am in the process of trying to do a emerge -e system
> which will also update everything as well.  My problem is glibc and the
> locale settings.  May be a separate issue or related.  Here is the boo
> boo. 
>
> localhost linux # emerge -v glibc
> sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
>
>  * IMPORTANT: 5 news items need reading for repository 'gentoo'.
>  * Use eselect news to read news items.
>
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R    ] sys-libs/glibc-2.17:2.2  USE="-debug -gd (-hardened)
> (-multilib) -nscd -profile (-selinux) -suid -systemtap -vanilla" 0 kB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 kB
>
>>>> Verifying ebuild manifests
>>>> Emerging (1 of 1) sys-libs/glibc-2.17
>>>> Failed to emerge sys-libs/glibc-2.17, Log file:
>>>>  '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'
>>>> Jobs: 0 of 1 complete, 1 failed                 Load avg: 0.16,
> 0.39, 1.44
>  * Package:    sys-libs/glibc-2.17
>  * Repository: gentoo
>  * Maintainer: toolchain@gentoo.org
>  * USE:        abi_x86_32 elibc_glibc kernel_linux userland_GNU x86
>  * FEATURES:   preserve-libs sandbox
> [sys-libs/glibc-2.17] bash: warning: setlocale: LC_ALL: cannot change
> locale (en_US.UTF8)
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale
> (en_US.UTF8)  <<-- This error right here. :-( 
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> make -j3 -s glibc-test
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> make -j3 -s glibc-test
>  * Your old kernel is broken.  You need to update it to
>  * a newer version as syscall(<bignum>) will break.
>  * http://bugs.gentoo.org/279260
>  * ERROR: sys-libs/glibc-2.17::gentoo failed (setup phase):
>  *   keeping your system alive, say thank you
>  *
>  * Call stack:
>  *           ebuild.sh, line  93:  Called pkg_setup
>  *   glibc-2.17.ebuild, line 151:  Called eblit-run 'pkg_setup'
>  *   glibc-2.17.ebuild, line 137:  Called eblit-glibc-pkg_setup
>  *     pkg_setup.eblit, line  75:  Called die
>  * The specific snippet of code:
>  *                      die "keeping your system alive, say thank you"
>  *
>  * If you need support, post the output of `emerge --info
> '=sys-libs/glibc-2.17::gentoo'`,
>  * the complete build log and the output of `emerge -pqv
> '=sys-libs/glibc-2.17::gentoo'`.
>  * The complete build log is located at
> '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/sys-libs/glibc-2.17/temp/die.env'.
>  * Working directory: '/usr/lib/portage/pym'
>  * S: '/var/tmp/portage/sys-libs/glibc-2.17/work/glibc-2.17'
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
> sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
>  *
>  * The following package has failed to build or install:
>  *
>  *  (sys-libs/glibc-2.17::gentoo, ebuild scheduled for merge), Log file:
>  *   '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'
>  *
> localhost linux #
>
>
> One reason I want to re-emerge glibc, I'm HOPING it will fix the other
> LC_ALL error.  I'm pretty sure glibc takes care of that but not 100%
> sure.  I checked my main rig for differences in USE flags, multilib is
> the only one I see.  It is set on my main rig and doesn't seem to be
> available on x86 for obvious reasons. 
>
> If this is not enough info, let me know what you need.  I don't want to
> flood with tons of unneeded info when usually that above gives enough of
> a hint.  ;-) 
>
> Thanks.
>
> Dale
>
> :-)  :-) 
>


UPDATE:  Thanks to Hinnerk, the locale error is fixed.  I am still
looking for ideas on the glibc error tho.  Since this original post, I
have tried the following versions of glibc with the same result.

sys-libs/glibc-2.18-r1
sys-libs/glibc-2.19-r1

So, it seems something else is wrong here.  I have googled and most
things I find are with older kernels and I'm using the newest kernel I
can find in the tree.  3.15.5-gentoo 

Ideas?  Fixes?  Bug that needs Raid?

Dale

:-)  :-) 

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Hinnerk van Bruinehsen]

[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]

On Tue, Jul 15, 2014 at 12:33:57AM -0500, Dale wrote:
<SNIP>
> > make -j3 -s glibc-test
> >  * Your old kernel is broken.  You need to update it to
> >  * a newer version as syscall(<bignum>) will break.
> >  * http://bugs.gentoo.org/279260
> >  * ERROR: sys-libs/glibc-2.17::gentoo failed (setup phase):
> >  *   keeping your system alive, say thank you
> >  *
> >  * Call stack:
<SNIP>
> UPDATE:  Thanks to Hinnerk, the locale error is fixed.  I am still
> looking for ideas on the glibc error tho.  Since this original post, I
> have tried the following versions of glibc with the same result.
>
> sys-libs/glibc-2.18-r1
> sys-libs/glibc-2.19-r1
>
> So, it seems something else is wrong here.  I have googled and most
> things I find are with older kernels and I'm using the newest kernel I
> can find in the tree.  3.15.5-gentoo
>
> Ideas?  Fixes?  Bug that needs Raid?

I've taken a look at the bug that is mentioned in the error and there were
several things mentioned that are supposed to fix this:

	1. disable auditd (if you have it running) - this was the newest (from '14)
	   So if you have it installed run /etc/init.d/auditd stop
	2. reemerge several packages because python may have issues:
	   - sync your tree
	   - emerge portage (which will likely pull in some python stuff if the box
		 wasn't updated for some time)
	  (- optional: run eselect python and select a sane version and run python
	  updater - this wasn't mentioned but may make sense nonetheless)
	   - emerge linux-headers
	   - emerge glibc (hopefully with success this time)

WKR
Hinnerk

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

Hinnerk van Bruinehsen wrote:
> I've taken a look at the bug that is mentioned in the error and there were
> several things mentioned that are supposed to fix this:
>
> 	1. disable auditd (if you have it running) - this was the newest (from '14)
> 	   So if you have it installed run /etc/init.d/auditd stop
> 	2. reemerge several packages because python may have issues:
> 	   - sync your tree
> 	   - emerge portage (which will likely pull in some python stuff if the box
> 		 wasn't updated for some time)
> 	  (- optional: run eselect python and select a sane version and run python
> 	  updater - this wasn't mentioned but may make sense nonetheless)
> 	   - emerge linux-headers
> 	   - emerge glibc (hopefully with success this time)
>
> WKR
> Hinnerk

I didn't have the audit stuff installed BUT it was turned on in the
kernel.  I kicked that out and also got rid of all that cgroup stuff I
don't have any need for.  Rebooted then tried your list.  Audit stuff,
gone. Sync is maybe a couple days old so should be OK.  Portage is up to
date.  Python as follows:

dev-lang/python-2.7.6
dev-lang/python-3.3.3

localhost ~ # eselect python list
Available Python interpreters:
  [1]   python2.7 *
  [2]   python3.3
localhost ~ #

Updated linux-headers.  It was a little out of sync with kernel
version.  After all that, I get this:

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-libs/glibc-2.17:2.2  USE="-debug -gd (-hardened)
(-multilib) -nscd -profile (-selinux) -suid -systemtap -vanilla" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB

>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-libs/glibc-2.17
>>> Failed to emerge sys-libs/glibc-2.17, Log file:
>>>  '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'
>>> Jobs: 0 of 1 complete, 1 failed                 Load avg: 0.27,
0.59, 0.43
 * Package:    sys-libs/glibc-2.17
 * Repository: gentoo
 * Maintainer: toolchain@gentoo.org
 * USE:        abi_x86_32 elibc_glibc kernel_linux userland_GNU x86
 * FEATURES:   preserve-libs sandbox
make -j3 -s glibc-test
make -j3 -s glibc-test
 * Your old kernel is broken.  You need to update it to
 * a newer version as syscall(<bignum>) will break.
 * http://bugs.gentoo.org/279260
 * ERROR: sys-libs/glibc-2.17::gentoo failed (setup phase):
 *   keeping your system alive, say thank you
 *
 * Call stack:
 *           ebuild.sh, line  93:  Called pkg_setup
 *   glibc-2.17.ebuild, line 151:  Called eblit-run 'pkg_setup'
 *   glibc-2.17.ebuild, line 137:  Called eblit-glibc-pkg_setup
 *     pkg_setup.eblit, line  75:  Called die
 * The specific snippet of code:
 *                      die "keeping your system alive, say thank you"
 *
 * If you need support, post the output of `emerge --info
'=sys-libs/glibc-2.17::gentoo'`,
 * the complete build log and the output of `emerge -pqv
'=sys-libs/glibc-2.17::gentoo'`.
 * The complete build log is located at
'/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-libs/glibc-2.17/temp/die.env'.
 * Working directory: '/usr/lib/portage/pym'
 * S: '/var/tmp/portage/sys-libs/glibc-2.17/work/glibc-2.17'
 *
 * The following package has failed to build or install:
 *
 *  (sys-libs/glibc-2.17::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'
 *
localhost ~ #

So, the locale junk is gone but glibc is still not liking something. 
Where did I put that hammer the last time I used it??  ;-) 

Ideas?  I'm pretty much out of them right now.  My idea is the hammer. 
lol 

Dale

:-)  :-) 

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Hinnerk van Bruinehsen]

[-- Attachment #1: Type: text/plain, Size: 3605 bytes --]

On Tue, Jul 15, 2014 at 02:40:13AM -0500, Dale wrote:
> Hinnerk van Bruinehsen wrote:
> > I've taken a look at the bug that is mentioned in the error and there were
> > several things mentioned that are supposed to fix this:
> >
> > 	1. disable auditd (if you have it running) - this was the newest (from '14)
> > 	   So if you have it installed run /etc/init.d/auditd stop
> > 	2. reemerge several packages because python may have issues:
> > 	   - sync your tree
> > 	   - emerge portage (which will likely pull in some python stuff if the box
> > 		 wasn't updated for some time)
> > 	  (- optional: run eselect python and select a sane version and run python
> > 	  updater - this wasn't mentioned but may make sense nonetheless)
> > 	   - emerge linux-headers
> > 	   - emerge glibc (hopefully with success this time)
> >
> > WKR
> > Hinnerk
> 
> I didn't have the audit stuff installed BUT it was turned on in the
> kernel.  I kicked that out and also got rid of all that cgroup stuff I
> don't have any need for.  Rebooted then tried your list.  Audit stuff,
> gone. Sync is maybe a couple days old so should be OK.  Portage is up to
> date.  Python as follows:
> 
> dev-lang/python-2.7.6
> dev-lang/python-3.3.3
> 
> localhost ~ # eselect python list
> Available Python interpreters:
>   [1]   python2.7 *
>   [2]   python3.3
> localhost ~ #
> 
> Updated linux-headers.  It was a little out of sync with kernel
> version.  After all that, I get this:
> 
<SNIP>
> 
> So, the locale junk is gone but glibc is still not liking something. 
> Where did I put that hammer the last time I used it??  ;-) 
> 
> Ideas?  I'm pretty much out of them right now.  My idea is the hammer. 
> lol 

Generally hammers tend to make things worse... ;-)

Can you run;

 printf "#include <unistd.h>\n#include <sys/syscall.h>\nint main(){return \
 syscall(1000)!=-1;}\n" > syscall.c && make syscall && ./syscall && echo $?

(It should be all one line).
It will compile the test that seems to fail on your system and runs it,
expected output would be:

cc     syscall.c   -o syscall
0

The "0" says that all went well, if it reports something else then it's not
just the buildsystem...

If it's the system you'll have to reinstall glibc (no kidding, as it provides
the used headers (though they should be somewhat dependent on linux-headers)).

You could do the following to break out of this chicken-and-egg-problem:
you can download an appropriate stage3-tarball (x86 or amd64) and extract it to
some arbitrary location. Then you essentially do the same as if you would
install gentoo from scratch (bind mount dev and sys and mount proc) and chroot
into it.
Inside the chroot you sync your tree (you could also bind-mount it from the
default location) and emerge glibc again but this time with the --build-pkg
flag set (emerge --buildpkg glibc). As long as you kernel is new enough (which
3.15.5 definitely is) the build should succeed and leave you with a nice binpkg
of glibc sitting in <path-to-chroot>/usr/portage/packages (in case of the
bind mount it should also be there inside your real system). If needed copy
it to /usr/portage/packages and run emerge -K glibc (this will force portage
to use the binpkg).

I hope that this es enough to circumvent the check (if not you could also try
to boot your rig from usb and copy the contents of the binpkg manually).

If the build breaks even inside the chroot run uname -a and take a look if the
kernel you're running acutally reports to be a 3.15.5 one.

Good luck,
Hinnerk



[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Hinnerk van Bruinehsen]

[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

On a side note:

You can also boot into a chroot, move your /etc and /var directories elsewhere
(e.g. etc_old and var_old) (do the same for other directories where you
yourself made changes), extract a stage 3 tarball on top of your normal
/ directory (overwriting potentially broken stuff), move etc_old and var_old
back to their old locations/names, chroot into it (like during install) and
emerge @system @world -evDNa (to rebuild everything from the known-good start
that the stage3 provides).

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

Hinnerk van Bruinehsen wrote:
> On a side note:
>
> You can also boot into a chroot, move your /etc and /var directories elsewhere
> (e.g. etc_old and var_old) (do the same for other directories where you
> yourself made changes), extract a stage 3 tarball on top of your normal
> / directory (overwriting potentially broken stuff), move etc_old and var_old
> back to their old locations/names, chroot into it (like during install) and
> emerge @system @world -evDNa (to rebuild everything from the known-good start
> that the stage3 provides).

It's getting close to nap time here.  Also, more stormy stuff could pop
up at any time.  I shut the old rig back down again.  It doesn't have a
UPS or anything on it.  Anyway, I suspect strongly that the error is on
the stage3 tarball.  I got it installed but I have not been able to get
a clean emerge -e system as of yet.  I generally unpack, get things to
where I can emerge and then do a emerge -e system as soon as I can. 
That way anything else I build is built on top of updated packages.  I
have installed Gentoo so many times it is pitiful. 

What I may do, unpack the stage3 somewhere, recompile glibc to create a
binary and then install that package.  I'm not going to be to shocked if
it fails to build straight out of the stage3 tarball tho. 

I'm going to work on this some more when I get both eyes open. 

Dale

:-)  :-) 

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

Dale wrote:
> Hinnerk van Bruinehsen wrote:
>> On a side note:
>>
>> You can also boot into a chroot, move your /etc and /var directories elsewhere
>> (e.g. etc_old and var_old) (do the same for other directories where you
>> yourself made changes), extract a stage 3 tarball on top of your normal
>> / directory (overwriting potentially broken stuff), move etc_old and var_old
>> back to their old locations/names, chroot into it (like during install) and
>> emerge @system @world -evDNa (to rebuild everything from the known-good start
>> that the stage3 provides).
> It's getting close to nap time here.  Also, more stormy stuff could pop
> up at any time.  I shut the old rig back down again.  It doesn't have a
> UPS or anything on it.  Anyway, I suspect strongly that the error is on
> the stage3 tarball.  I got it installed but I have not been able to get
> a clean emerge -e system as of yet.  I generally unpack, get things to
> where I can emerge and then do a emerge -e system as soon as I can. 
> That way anything else I build is built on top of updated packages.  I
> have installed Gentoo so many times it is pitiful. 
>
> What I may do, unpack the stage3 somewhere, recompile glibc to create a
> binary and then install that package.  I'm not going to be to shocked if
> it fails to build straight out of the stage3 tarball tho. 
>
> I'm going to work on this some more when I get both eyes open. 
>
> Dale
>
> :-)  :-) 
>

I tried this.  I unpacked the stage3 tarball just like I would for a new
install, in /mnt/gentoo of course.  I set it up just enough to where I
could try and emerge glibc and just see if it would complete or if it
would fail.  It failed.  It seems to me that while it may be complaining
about the kernel version, something else is really the issue.  I'm using
the latest kernel so it can't be that.  I also installed linux-headers
and tried again, still failed. 

I also checked on the locale,gen file.  It is the wrong file type within
the tarball.  It shows up as GENESIS rom there as well instead of a
plain text file. 

It seems to me that the stage3 tarball is broke.  I'm not sure what else
to try at this point.  When the source is broke, it's sort of hard to
fix the rest. 

Where to go from here?

Dale

:-)  :-) 

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Helmut Jarausch]

On 07/16/2014 09:32:31 AM, Dale wrote:
> I tried this.  I unpacked the stage3 tarball just like I would for a  
> new
> install, in /mnt/gentoo of course.  I set it up just enough to where I
> could try and emerge glibc and just see if it would complete or if it
> would fail.  It failed.  It seems to me that while it may be  
> complaining
> about the kernel version, something else is really the issue.  I'm  
> using
> the latest kernel so it can't be that.  I also installed linux-headers
> and tried again, still failed.

What kernel version are you using?
On one machine I have strange effects with kernel 3.15.x (including  
3.15.5)
Portage hangs. Attaching gdb to it one can see that hangs in the glibc  
call
__epoll_wait_nocancel
called from pyepoll_poll from  PyRun_FileExFlags

Just stepping back to 3.14.12 solves the problem.
(I do have linux-headers-3.15 installed here)

Helmut

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

Helmut Jarausch wrote:
> On 07/16/2014 09:32:31 AM, Dale wrote:
>> I tried this.  I unpacked the stage3 tarball just like I would for a new
>> install, in /mnt/gentoo of course.  I set it up just enough to where I
>> could try and emerge glibc and just see if it would complete or if it
>> would fail.  It failed.  It seems to me that while it may be complaining
>> about the kernel version, something else is really the issue.  I'm using
>> the latest kernel so it can't be that.  I also installed linux-headers
>> and tried again, still failed.
>
> What kernel version are you using?
> On one machine I have strange effects with kernel 3.15.x (including
> 3.15.5)
> Portage hangs. Attaching gdb to it one can see that hangs in the glibc
> call
> __epoll_wait_nocancel
> called from pyepoll_poll from  PyRun_FileExFlags
>
> Just stepping back to 3.14.12 solves the problem.
> (I do have linux-headers-3.15 installed here)
>
> Helmut
>
>
>

3.15.5-gentoo

I got a different tarball, going to test that.  If it fails, may step
back a kernel version and see if that helps.  It's faster than
re-installing from scratch again.  ;-)

Dale

:-)  :-) 

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

Dale wrote:
> Helmut Jarausch wrote:
>> On 07/16/2014 09:32:31 AM, Dale wrote:
>>> I tried this.  I unpacked the stage3 tarball just like I would for a new
>>> install, in /mnt/gentoo of course.  I set it up just enough to where I
>>> could try and emerge glibc and just see if it would complete or if it
>>> would fail.  It failed.  It seems to me that while it may be complaining
>>> about the kernel version, something else is really the issue.  I'm using
>>> the latest kernel so it can't be that.  I also installed linux-headers
>>> and tried again, still failed.
>> What kernel version are you using?
>> On one machine I have strange effects with kernel 3.15.x (including
>> 3.15.5)
>> Portage hangs. Attaching gdb to it one can see that hangs in the glibc
>> call
>> __epoll_wait_nocancel
>> called from pyepoll_poll from  PyRun_FileExFlags
>>
>> Just stepping back to 3.14.12 solves the problem.
>> (I do have linux-headers-3.15 installed here)
>>
>> Helmut
>>
>>
>>
> 3.15.5-gentoo
>
> I got a different tarball, going to test that.  If it fails, may step
> back a kernel version and see if that helps.  It's faster than
> re-installing from scratch again.  ;-)
>
> Dale
>
> :-)  :-) 
>

UPDATE:  I downloaded a different stage3 tarball and I think I see
progress.  It has a couple errors that I had to fix, had to run
gcc-config for one, but it looks like glibc is running longer than
before.  It seems to be compiling now.  So, it seems that other tarball
has some issues and needs a hammer. 

Now to figure out if I want to try and use the binary from this new
tarball on the current install OR just install Gentoo again from scratch. 

Dale

:-)  :-)

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[J. Roeleveld]

On 16 July 2014 11:19:20 CEST, Dale <rdalek1967@gmail.com> wrote:
>Dale wrote:
>> Helmut Jarausch wrote:
>>> On 07/16/2014 09:32:31 AM, Dale wrote:
>>>> I tried this.  I unpacked the stage3 tarball just like I would for
>a new
>>>> install, in /mnt/gentoo of course.  I set it up just enough to
>where I
>>>> could try and emerge glibc and just see if it would complete or if
>it
>>>> would fail.  It failed.  It seems to me that while it may be
>complaining
>>>> about the kernel version, something else is really the issue.  I'm
>using
>>>> the latest kernel so it can't be that.  I also installed
>linux-headers
>>>> and tried again, still failed.
>>> What kernel version are you using?
>>> On one machine I have strange effects with kernel 3.15.x (including
>>> 3.15.5)
>>> Portage hangs. Attaching gdb to it one can see that hangs in the
>glibc
>>> call
>>> __epoll_wait_nocancel
>>> called from pyepoll_poll from  PyRun_FileExFlags
>>>
>>> Just stepping back to 3.14.12 solves the problem.
>>> (I do have linux-headers-3.15 installed here)
>>>
>>> Helmut
>>>
>>>
>>>
>> 3.15.5-gentoo
>>
>> I got a different tarball, going to test that.  If it fails, may step
>> back a kernel version and see if that helps.  It's faster than
>> re-installing from scratch again.  ;-)
>>
>> Dale
>>
>> :-)  :-) 
>>
>
>UPDATE:  I downloaded a different stage3 tarball and I think I see
>progress.  It has a couple errors that I had to fix, had to run
>gcc-config for one, but it looks like glibc is running longer than
>before.  It seems to be compiling now.  So, it seems that other tarball
>has some issues and needs a hammer. 
>
>Now to figure out if I want to try and use the binary from this new
>tarball on the current install OR just install Gentoo again from
>scratch. 
>
>Dale
>
>:-)  :-)

I would start from scratch.  Who knows what else is broken?

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

J. Roeleveld wrote:
> On 16 July 2014 11:19:20 CEST, Dale <rdalek1967@gmail.com> wrote:
>>
>> UPDATE:  I downloaded a different stage3 tarball and I think I see
>> progress.  It has a couple errors that I had to fix, had to run
>> gcc-config for one, but it looks like glibc is running longer than
>> before.  It seems to be compiling now.  So, it seems that other tarball
>> has some issues and needs a hammer. 
>>
>> Now to figure out if I want to try and use the binary from this new
>> tarball on the current install OR just install Gentoo again from
>> scratch. 
>>
>> Dale
>>
>> :-)  :-)
> I would start from scratch.  Who knows what else is broken?
>
> --
> Joost

And then I went back to add the -B option and it failed.  So, it built
the first time but fails the 2nd time.  I'm beginning to wonder about
those stage3 tarballs for x86.  Do they test those from time to time to
make sure they work or do they just autobuild them and upload them?  I'm
following the install guide so I'm pretty sure I'm not doing anything
wrong but at the same time, I don't want to file a bug when it is just me. 

I may play with this some more.  It is starting to get old tho.  What
concerns me is if it has the same issue for someone new to Gentoo.  At
least I been around the block a few times.  A noobie is going to pull
all their hair out thinking they are not doing something right. 

Dale

:-)  :-) 

[gentoo-user] Re: glibc-2.17 fails and warning: setlocale: LC_ALL error

[walt]

On 07/16/2014 10:21 AM, Dale wrote:
> I'm beginning to wonder about
> those stage3 tarballs for x86.  Do they test those from time to time to
> make sure they work or do they just autobuild them and upload them?  I'm
> following the install guide so I'm pretty sure I'm not doing anything
> wrong but at the same time, I don't want to file a bug when it is just me. 

Over the years I remember maybe three times I've had to untar a stage3 on
top of a "working" system, and IIRC the catastrophic problem was glibc each
time :/

Anyway, the first time I tried it I learned that the stage3 overwrites the
existing /etc directory. (That was so painful I remembered to move /etc out
of the way the next two times it did it :)

I mention all this because /etc/locale.conf may not be the file you expect,
based on how your compile environment and chroot stuff is configured, etc.

I been there/done that :)

Re: [gentoo-user] Re: glibc-2.17 fails and warning: setlocale: LC_ALL error

[Dale]

walt wrote:
> On 07/16/2014 10:21 AM, Dale wrote:
>> I'm beginning to wonder about
>> those stage3 tarballs for x86.  Do they test those from time to time to
>> make sure they work or do they just autobuild them and upload them?  I'm
>> following the install guide so I'm pretty sure I'm not doing anything
>> wrong but at the same time, I don't want to file a bug when it is just me. 
> Over the years I remember maybe three times I've had to untar a stage3 on
> top of a "working" system, and IIRC the catastrophic problem was glibc each
> time :/
>
> Anyway, the first time I tried it I learned that the stage3 overwrites the
> existing /etc directory. (That was so painful I remembered to move /etc out
> of the way the next two times it did it :)
>
> I mention all this because /etc/locale.conf may not be the file you expect,
> based on how your compile environment and chroot stuff is configured, etc.
>
> I been there/done that :)
>

I haven't done this on top of a working system tho.  The first tarball
was a fresh install.  The Gentoo that was there hadn't been updated in
like 3 years or so.  I wasn't about to jump in and try to update all
that.  The 2nd time, I just unpacked the tarball in /mnt/gentoo just
like I would a fresh install just that it was in the first install. 

The locale.gen file was untouched from the tarball so it was the wrong
file type when I downloaded it.  No clue on that yet. 

Dale

:-)  :-)