J. Roeleveld wrote:
Update:
No issues with glibc.
I am not doing any parallel builds (eg. default of -j 1 is used)
Let me know if you want any files for comparison.
--
Joost
I tried the same tarball you are using and it still failed. Basically,
I unpacked the thing, copied
On 18 July 2014 11:18:27 CEST, Dale rdalek1...@gmail.com wrote:
J. Roeleveld wrote:
Update:
No issues with glibc.
I am not doing any parallel builds (eg. default of -j 1 is used)
Let me know if you want any files for comparison.
--
Joost
I tried the same tarball you are using
2014-07-18 3:18 GMT-06:00 Dale rdalek1...@gmail.com:
I tried the same tarball you are using and it still failed. Basically, I
unpacked the thing, copied over the portage tree and distfiles and tried to
emerge glibc and it failed. It has to be something wrong on my end here.
Heck, this
On Thursday, July 17, 2014 06:52:20 AM J. Roeleveld wrote:
On 16 July 2014 19:26:39 CEST, Dale rdalek1...@gmail.com wrote:
Dark Templar wrote:
When I reinstalled gcc and glibc, migrating from non-multilib amd64
arch
to multilib one, I just unpacked gentoo stage3 into temporary
J. Roeleveld wrote:
Update:
Using a 32bit VM with current x86 stage3 file, glibc builds
succesfully. (On first run)
Will do a second emerge -ve @system when this one is finished.
I used the following stage file:
stage3-i686-20140708.tar.bz2
I have not change anything in
On Thursday, July 17, 2014 04:03:34 AM Dale wrote:
J. Roeleveld wrote:
Update:
Using a 32bit VM with current x86 stage3 file, glibc builds
succesfully. (On first run)
Will do a second emerge -ve @system when this one is finished.
I used the following stage file:
On Thursday 17 July 2014 04:03:34 Dale wrote:
---8
Sounds good. I'm downloading that one and will try to install it next.
Let's hope it was a one time event.
Thanks for testing it.
I've just started installing a 64-bit chroot to do the emerge work for my
laptop and I fell into the same
On Thursday, July 17, 2014 11:19:36 AM J. Roeleveld wrote:
On Thursday, July 17, 2014 04:03:34 AM Dale wrote:
J. Roeleveld wrote:
Update:
Using a 32bit VM with current x86 stage3 file, glibc builds
succesfully. (On first run)
Will do a second emerge -ve @system
On Thursday 17 July 2014 10:20:59 I wrote:
On Thursday 17 July 2014 04:03:34 Dale wrote:
---8
Sounds good. I'm downloading that one and will try to install it next.
Let's hope it was a one time event.
Thanks for testing it.
I've just started installing a 64-bit chroot to do the
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
/
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
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
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
On 16 July 2014 11:19:20 CEST, Dale rdalek1...@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
16.07.2014 14:33, J. Roeleveld пишет:
On 16 July 2014 11:19:20 CEST, Dale rdalek1...@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
J. Roeleveld wrote:
On 16 July 2014 11:19:20 CEST, Dale rdalek1...@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.
Dark Templar wrote:
When I reinstalled gcc and glibc, migrating from non-multilib amd64 arch
to multilib one, I just unpacked gentoo stage3 into temporary directory,
chrooted there, made binary packages out of installed ones (quickpkg
name), copied resulted binary packages and their metadata
On Wednesday 16 Jul 2014 18:26:39 Dale wrote:
Dark Templar wrote:
When I reinstalled gcc and glibc, migrating from non-multilib amd64 arch
to multilib one, I just unpacked gentoo stage3 into temporary directory,
chrooted there, made binary packages out of installed ones (quickpkg
name),
Mick wrote:
On Wednesday 16 Jul 2014 18:26:39 Dale wrote:
If I can install something as a binary and then get a clean emerge -e
system/world out of it, I think it would be OK. Thing is, I'm concerned
something is amiss with the stage3 tarball. If that is the case, I want
to inform the
On 16 July 2014 19:26:39 CEST, Dale rdalek1...@gmail.com wrote:
Dark Templar wrote:
When I reinstalled gcc and glibc, migrating from non-multilib amd64
arch
to multilib one, I just unpacked gentoo stage3 into temporary
directory,
chrooted there, made binary packages out of installed ones
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):
*
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
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
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
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
On Tue, Jul 15, 2014 at 2:25 AM, Dale rdalek1...@gmail.com wrote:
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 know you say you have the latest kernel installed, Dale, but are you
Douglas J Hunley wrote:
On Tue, Jul 15, 2014 at 2:25 AM, Dale rdalek1...@gmail.com
mailto:rdalek1...@gmail.com wrote:
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.
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
On Mon, Jul 14, 2014 at 08:50:58PM -0500, 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
Hinnerk van Bruinehsen wrote:
Hi Dale,
first you should check if you have this line in your /etc/locale.gen:
en_US.UTF-8 UTF-8
If you do, run locale-gen to create the locale. This should in theory
fix the
LC_foo errors (Note: there are some LC_ settings best left undisturbed,
especially
On Mon, Jul 14, 2014 at 09:19:27PM -0500, Dale wrote:
Hinnerk van Bruinehsen wrote:
Hi Dale,
first you should check if you have this line in your
/etc/locale.gen:
en_US.UTF-8 UTF-8
If you
Hinnerk van Bruinehsen wrote:
On Mon, Jul 14, 2014 at 09:19:27PM -0500, Dale wrote:
Howdy,
I looked at that file. On both my systems, it is not a text file. When I
look at it in a file manager, Konqueror via fish, it shows up as GENESIS
rom for type. Since it is not text on
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
33 matches
Mail list logo
