On 2014-01-11 10:06 PM, Rick Zero_Chaos Farina wrote:
On 01/08/2014 01:03 PM, Tanstaafl wrote:
Could this have anything to do with the fact that I don't have either of
these set in /etc/portage/make.comf:
PYTHON_TARGETS="python2_7 python3_3"
PYTHON_SINGLE_TARGET="python2_7"
You really do no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/08/2014 01:03 PM, Tanstaafl wrote:
> Could this have anything to do with the fact that I don't have either of
> these set in /etc/portage/make.comf:
>
> PYTHON_TARGETS="python2_7 python3_3"
> PYTHON_SINGLE_TARGET="python2_7"
>
You really do not
On 2014-01-09 4:24 AM, Alan McKinnon wrote:
On 08/01/2014 20:03, Tanstaafl wrote:
On 2014-01-08 11:54 AM, Tanstaafl wrote:
I just updated glibc to 2.1.17, and got the following error at the very
end of the emerge:
/usr/bin/python2.7: relocation error: /lib64/libresolv.so.2: symbol
__sendmms
On 08/01/2014 20:03, Tanstaafl wrote:
> On 2014-01-08 11:54 AM, Tanstaafl wrote:
>> I just updated glibc to 2.1.17, and got the following error at the very
>> end of the emerge:
>>
>>> /usr/bin/python2.7: relocation error: /lib64/libresolv.so.2: symbol
>>> __sendmmsg, version GLIBC_PRIVATE not def
On 2014-01-08 11:54 AM, Tanstaafl wrote:
I just updated glibc to 2.1.17, and got the following error at the very
end of the emerge:
/usr/bin/python2.7: relocation error: /lib64/libresolv.so.2: symbol
__sendmmsg, version GLIBC_PRIVATE not defined in file libc.so.6 with
lin
I just updated glibc to 2.1.17, and got the following error at the very
end of the emerge:
/usr/bin/python2.7: relocation error: /lib64/libresolv.so.2: symbol __sendmmsg,
version GLIBC_PRIVATE not defined in file libc.so.6 with lin
k time
On Friday 20 March 2009 03:52:10 Jorge Morais wrote:
> This was a doubt of mine. One of the reasons I prefer to use a stable
> kernel is that I don't know if, when using a newer (and ~x86) kernel,
> I should also use the corresponding linux-headers version. So you say
> I can be 99.999% sure that,
On Wed, 18 Mar 2009 23:49:12 +0200
Alan McKinnon wrote:
> > msoul...@anton:~$ equery belongs /usr/include/linux/quota.h
> > [ Searching for file(s) /usr/include/linux/quota.h in *... ]
> > sys-kernel/linux-headers-2.6.23-r3 (/usr/include/linux/quota.h)
> >
> > ul...@anton:~$ uname -a
> > Linux ant
On Wednesday 18 March 2009 23:43:50 Michael P. Soulier wrote:
> On 18/03/09 Alan McKinnon said:
> > Well, this is gentoo and we don't need no stinking Changelogs on gentoo
> > :-)
> >
> :)
> :
> > Seriously, you are running a stable arch. All known issues should be
> > resolved by the time glibc hi
On Wed, Mar 18, 2009 at 4:43 PM, Michael P. Soulier
wrote:
> On 18/03/09 Alan McKinnon said:
>
>> Seriously, you are running a stable arch. All known issues should be resolved
>> by the time glibc hits stable. You can always askhere, or look at b.g.o for
>> any outstanding issues
>
> Bulgarian Gay
On 18/03/09 Alan McKinnon said:
> Well, this is gentoo and we don't need no stinking Changelogs on gentoo :-)
:)
> Seriously, you are running a stable arch. All known issues should be resolved
> by the time glibc hits stable. You can always askhere, or look at b.g.o for
> any outstanding issue
On Wednesday 18 March 2009 20:05:27 Michael P. Soulier wrote:
> > Sometimes, glibc is all fsck'ed up. Like sys-libs/glibc-2.9_p20081201-r1.
> > It looks great, till you start firefox and find that it doesn't run
> > anymore...
>
> So, how would I know, in general, whether it's safe to upgrade when
On 18/03/09 Alan McKinnon said:
> You said "glibc is the basis of the whole system". That's not quite true,
> it's actually "glibc provides the C library, which is a collection of basic
> function calls that just about every other program uses sooner or later"
I wasn't sure if any interface chang
On Wednesday 18 March 2009 13:23:47 Michael P. Soulier wrote:
> Hello,
>
> Looking at what I'm about to pick up via emerge, I notice this
>
> [ebuild U ] sys-libs/glibc-2.8_p20080602-r1 [2.6.1]
>
> This immediately sets off alarm bells for me, since glibc is the basis of
> the whole system. If
Hello,
Looking at what I'm about to pick up via emerge, I notice this
[ebuild U ] sys-libs/glibc-2.8_p20080602-r1 [2.6.1]
This immediately sets off alarm bells for me, since glibc is the basis of the
whole system. If I pick this up do I have to rebuild everything?
I've also frozen my kernel
Michael [Plouj] Ploujnikov ha scritto:
>> Try also using the "emergency shell" /bin/bb, it should be statically
>> linked and therefore independent from glibc.
> Thanks. I had no idea I had that thing.
Me too, but Google is always a bliss. :)
m.
--
gentoo-user@gentoo.org mailing list
First of all, thanks for the replies.
Just so you know, I was able to get my system to a working state. Read
the bit about untarring the old glibc into my system in my email.
I don't reallly have a clue if any of those are relevant but have a look
yourself.. Otherwise go ahead and file the bug.
On Saturday 03 March 2007 23:56:19 Michael [Plouj] Ploujnikov wrote:
> Before I file this as a bug I'd like to make sure it's not caused by
> something wrong with my system. Please help me determine that.
> In the past two days I was trying to upgrade my glibc from version 2.4
> to 2.5. Each time I
Michael [Plouj] Ploujnikov ha scritto:
> Hi,
> What happens after this is pretty nasty. Any program that I run segfaults:
>
> # ls
> Segmentation fault
Try also using the "emergency shell" /bin/bb, it should be statically
linked and therefore independent from glibc.
m.
--
gentoo-user@gentoo.org
Michael [Plouj] Ploujnikov ha scritto:
> Hi,
> Before I file this as a bug I'd like to make sure it's not caused by
> something wrong with my system. Please help me determine that.
> In the past two days I was trying to upgrade my glibc from version 2.4
> to 2.5. Each time I tried it the emerge pro
Hi,
Before I file this as a bug I'd like to make sure it's not caused by
something wrong with my system. Please help me determine that.
In the past two days I was trying to upgrade my glibc from version 2.4
to 2.5. Each time I tried it the emerge process failed at the very
last point - I think whe
Hi,
Before I file this as a bug I'd like to make sure it's not caused by
something wrong with my system. Please help me determine that.
In the past two days I was trying to upgrade my glibc from version 2.4
to 2.5. Each time I tried it the emerge process failed at the very
last point - I think whe
On 8/31/06, Neil Isaac <[EMAIL PROTECTED]> wrote:
I do have nptl and nptlonly in USE (that message had a yellow star, so
I guess it's just a warning) but my CHOST is set to
CHOST="i386-pc-linux-gnu" in make.conf. How do I correct this problem?
Assuming you are using a processor made in the last
I'm trying to upgrade to glibc-2.4-rc3 (in x86 stable) and get the
following error:
Emerging (1 of 2) sys-libs/glibc-2.4-r3 to /
checking glibc-linuxthreads-20060605.tar.bz2 ;-)
checking glibc-powerpc-cpu-addon-v0.01.tgz ;-)
* glibc-2.4 is nptl-only!
* NPTL requires a CHOST of i486 or be
24 matches
Mail list logo
