* [gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates
@ 2011-07-23 21:09 walt
2011-07-23 21:32 ` Dale
2011-07-23 22:44 ` [gentoo-user] " walt
0 siblings, 2 replies; 5+ messages in thread
From: walt @ 2011-07-23 21:09 UTC (permalink / raw
To: gentoo-user
This will affect (I think) only ~arch users.
If you are running the new linux kernel version 3.0, you will
find that today's update of python will fail with the error
"plat-linux2 not found".
That's because the python configure scripts will detect the
version 3 kernel and will try to use "plat-linux3" instead of
"plat-linux2".
To finish today's update of python2 and python3, just boot
with any kernel-2.6.x and repeat the python update.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates
2011-07-23 21:09 [gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates walt
@ 2011-07-23 21:32 ` Dale
2011-07-23 22:01 ` Alan McKinnon
2011-07-23 22:44 ` [gentoo-user] " walt
1 sibling, 1 reply; 5+ messages in thread
From: Dale @ 2011-07-23 21:32 UTC (permalink / raw
To: gentoo-user
walt wrote:
> This will affect (I think) only ~arch users.
>
> If you are running the new linux kernel version 3.0, you will
> find that today's update of python will fail with the error
> "plat-linux2 not found".
>
> That's because the python configure scripts will detect the
> version 3 kernel and will try to use "plat-linux3" instead of
> "plat-linux2".
>
> To finish today's update of python2 and python3, just boot
> with any kernel-2.6.x and repeat the python update.
>
>
>
Did you by chance file a roach report? If so, number or link please.
Sounds like 2.6.40 may have been a better idea. lol
Dale
:-) :-)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates
2011-07-23 21:32 ` Dale
@ 2011-07-23 22:01 ` Alan McKinnon
2011-07-23 22:07 ` Dale
0 siblings, 1 reply; 5+ messages in thread
From: Alan McKinnon @ 2011-07-23 22:01 UTC (permalink / raw
To: gentoo-user
On Saturday 23 July 2011 16:32:39 Dale did opine thusly:
> walt wrote:
> > This will affect (I think) only ~arch users.
> >
> > If you are running the new linux kernel version 3.0, you will
> > find that today's update of python will fail with the error
> > "plat-linux2 not found".
> >
> > That's because the python configure scripts will detect the
> > version 3 kernel and will try to use "plat-linux3" instead of
> > "plat-linux2".
> >
> > To finish today's update of python2 and python3, just boot
> > with any kernel-2.6.x and repeat the python update.
>
> Did you by chance file a roach report? If so, number or link
> please.
>
> Sounds like 2.6.40 may have been a better idea. lol
Dear god, no!
May I point your attention over to portage so you can see for yourself
how silly that can get? 100 _rc versions and currently at 46 _alphas.
It's starting to look like svn commit numbers would be a better number
scheme :-)
Maintainers everywhere will simply have to update their install
scripts (the usual point of failure for something like this) and it
will be mostly fixed everywhere in about a fortnight.
--
alan dot mckinnon at gmail dot com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates
2011-07-23 22:01 ` Alan McKinnon
@ 2011-07-23 22:07 ` Dale
0 siblings, 0 replies; 5+ messages in thread
From: Dale @ 2011-07-23 22:07 UTC (permalink / raw
To: gentoo-user
Alan McKinnon wrote:
> On Saturday 23 July 2011 16:32:39 Dale did opine thusly:
>
>> walt wrote:
>>
>>> This will affect (I think) only ~arch users.
>>>
>>> If you are running the new linux kernel version 3.0, you will
>>> find that today's update of python will fail with the error
>>> "plat-linux2 not found".
>>>
>>> That's because the python configure scripts will detect the
>>> version 3 kernel and will try to use "plat-linux3" instead of
>>> "plat-linux2".
>>>
>>> To finish today's update of python2 and python3, just boot
>>> with any kernel-2.6.x and repeat the python update.
>>>
>> Did you by chance file a roach report? If so, number or link
>> please.
>>
>> Sounds like 2.6.40 may have been a better idea. lol
>>
> Dear god, no!
>
> May I point your attention over to portage so you can see for yourself
> how silly that can get? 100 _rc versions and currently at 46 _alphas.
> It's starting to look like svn commit numbers would be a better number
> scheme :-)
>
> Maintainers everywhere will simply have to update their install
> scripts (the usual point of failure for something like this) and it
> will be mostly fixed everywhere in about a fortnight.
>
>
>
Looks like they could have went to 2.6.99 then. ;-)
Dale
:-) :-)
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-user] Re: [HEADS UP] New kernel version 3.0 breaks build of latest python updates
2011-07-23 21:09 [gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates walt
2011-07-23 21:32 ` Dale
@ 2011-07-23 22:44 ` walt
1 sibling, 0 replies; 5+ messages in thread
From: walt @ 2011-07-23 22:44 UTC (permalink / raw
To: gentoo-user
On 07/23/2011 02:09 PM, walt wrote:
> To finish today's update of python2 and python3, just boot
> with any kernel-2.6.x and repeat the python update.
Well, not just any kernel-2.6.x. Python needs the kernel sources
for your 2.6.x kernel to be installed and configured. And (maybe)
needs the /usr/src/linux symlink to point at the 2.6 sources, but
I'm not sure of that last point.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-07-23 22:46 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-23 21:09 [gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates walt
2011-07-23 21:32 ` Dale
2011-07-23 22:01 ` Alan McKinnon
2011-07-23 22:07 ` Dale
2011-07-23 22:44 ` [gentoo-user] " walt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox