[gentoo-user] [HEADS UP] New kernel version 3.0 breaks build of latest python updates

July 23rd, 2011 - 05:20 pm ET by walt | Report spam
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.
email Follow the discussionReplies 4 repliesReplies Make a reply

Similar topics

Replies

#1 Dale
July 23rd, 2011 - 05:40 pm ET | Report spam
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

:-) :-)
Replies Reply to this message
#2 Alan McKinnon
July 23rd, 2011 - 06:10 pm ET | Report spam
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
Replies Reply to this message
#3 Dale
July 23rd, 2011 - 06:20 pm ET | Report spam
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

:-) :-)
Replies Reply to this message
#4 walt
July 23rd, 2011 - 06:50 pm ET | Report spam
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.
email Follow the discussion Replies Reply to this message
Help Create a new topicReplies Make a reply
Search Make your own search