Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-12 Thread Neil Bothwick
On Wed, 11 Feb 2009 20:22:32 -0800, Mark Knecht wrote:

  CFLAGS? The machine that fails:
 
  CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe 

 CFLAGS=-O2 -march=i686 -fomit-frame-pointer -pipe

You have more aggressive flags on the failing machine, have you tried
using the more conservative (less ricey) flags?


-- 
Neil Bothwick

USENET: Uniting Spammers, Erotomaniacs, Newbies, Extroverts and Trolls


signature.asc
Description: PGP signature


Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-12 Thread Mark Knecht
On Thu, Feb 12, 2009 at 12:58 AM, Neil Bothwick n...@digimed.co.uk wrote:
 On Wed, 11 Feb 2009 20:22:32 -0800, Mark Knecht wrote:

  CFLAGS? The machine that fails:
 
  CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe

 CFLAGS=-O2 -march=i686 -fomit-frame-pointer -pipe

 You have more aggressive flags on the failing machine, have you tried
 using the more conservative (less ricey) flags?


 --
 Neil Bothwick

I have not and intend to do that today. The flags have been set like
this since 2003 so I'm surprised that it might be something like this
but it's clearly possible.

I'm unqualified to say what part of the differences is making this set
more aggressive. Line by line what's your opinion?

-O3 vs -O2 ?
-march=athlon-xp vs -march=i686
-funroll-loops
-fprefetch-loop-arrays
not using -fomit-frame-pointer

I would think that I should be able to also make the flags more
aggressive on a passing machine and see the same failure, assuming
this is the root cause.

Strange taht after 6-years this would come up but stranger thing happen.

Thanks,
Mark



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-12 Thread Mark Knecht
On Thu, Feb 12, 2009 at 6:20 AM, Mark Knecht markkne...@gmail.com wrote:
SNIP

 -O3 vs -O2 ?
 -march=athlon-xp vs -march=i686
 -funroll-loops
 -fprefetch-loop-arrays
 not using -fomit-frame-pointer
SNIP

I started by removing -funroll-loops  -fprefetch-loop-arrays and it
emerged fine.

Thanks,
Mark



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-12 Thread Neil Bothwick
On Thu, 12 Feb 2009 06:20:28 -0800, Mark Knecht wrote:

  You have more aggressive flags on the failing machine, have you tried
  using the more conservative (less ricey) flags?

 I have not and intend to do that today. The flags have been set like
 this since 2003 so I'm surprised that it might be something like this
 but it's clearly possible.
 
 I'm unqualified to say what part of the differences is making this set
 more aggressive. Line by line what's your opinion?
 
 -O3 vs -O2 ?

Not much difference.

 -march=athlon-xp vs -march=i686

The former is better, providing you're using an AthlonXP.

 -funroll-loops

You only have to look at http://funroll-loops.org/ to know this is a bad
option...

 not using -fomit-frame-pointer

That's pretty safe, the frame-pointer isn't much use anyway if you're
compiling without debug symbols, which most build do by default.

 Strange taht after 6-years this would come up but stranger thing happen.

Indeed.


-- 
Neil Bothwick

Obscenity is the crutch of inarticulate motherfuckers.


signature.asc
Description: PGP signature


[gentoo-user] python-2.5.2-r7 build problems

2009-02-11 Thread Mark Knecht
Hi,
   I had two machine that for some reason wouldn't build the 2.5 slot
for python. I've waited weeks for the possibility that something would
get cleaned up in portage or on a server somewhere but as of yet it
hasn't happened. For kicks today I cleaned out distfiles and did an
emerge -e @system but it failed the same way. I'm wondering what to
try next?

   Is it allowable to remove ebuilds by hand? Will an eix-sync get new
versions if ebuilds are missing and I change the servers that the
machine is pointing to?

   Looking for ideas about how to move forward.

Thanks,
Mark



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-11 Thread Joshua D Doll

Mark Knecht wrote:

Hi,
   I had two machine that for some reason wouldn't build the 2.5 slot
for python. I've waited weeks for the possibility that something would
get cleaned up in portage or on a server somewhere but as of yet it
hasn't happened. For kicks today I cleaned out distfiles and did an
emerge -e @system but it failed the same way. I'm wondering what to
try next?

   Is it allowable to remove ebuilds by hand? Will an eix-sync get new
versions if ebuilds are missing and I change the servers that the
machine is pointing to?

   Looking for ideas about how to move forward.

Thanks,
Mark


  

What's the error message?

--Joshua Doll



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-11 Thread Mark Knecht
On Wed, Feb 11, 2009 at 6:25 PM, Joshua D Doll joshua.d...@gmail.com wrote:
 Mark Knecht wrote:

 Hi,
   I had two machine that for some reason wouldn't build the 2.5 slot
 for python. I've waited weeks for the possibility that something would
 get cleaned up in portage or on a server somewhere but as of yet it
 hasn't happened. For kicks today I cleaned out distfiles and did an
 emerge -e @system but it failed the same way. I'm wondering what to
 try next?

   Is it allowable to remove ebuilds by hand? Will an eix-sync get new
 versions if ebuilds are missing and I change the servers that the
 machine is pointing to?

   Looking for ideas about how to move forward.

 Thanks,
 Mark




 What's the error message?

 --Joshua Doll

Not much unfortunately:

Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xml/sax/xmlreader.py
...
Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmllib.py
...
Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmlrpclib.py
...
Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/zipfile.py
...
make: *** [libinstall] Error 1
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m ERROR: dev-lang/python-2.5.2-r7 failed.
 ^[[31;01m*^[[0m Call stack:
 ^[[31;01m*^[[0m   ebuild.sh, line   49:  Called src_install
 ^[[31;01m*^[[0m environment, line 3469:  Called die
 ^[[31;01m*^[[0m The specific snippet of code:
 ^[[31;01m*^[[0m   make DESTDIR=${D} altinstall maninstall || die;
 ^[[31;01m*^[[0m  The die message:
 ^[[31;01m*^[[0m   (no error message)
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m If you need support, post the topmost build error,
and the call stack if relevant.
 ^[[31;01m*^[[0m A complete build log is located at
'/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/build.log'.
 ^[[31;01m*^[[0m The ebuild environment file is located at
'/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/environment'.
 ^[[31;01m*^[[0m



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-11 Thread Joshua D Doll

Mark Knecht wrote:

On Wed, Feb 11, 2009 at 6:25 PM, Joshua D Doll joshua.d...@gmail.com wrote:
  

Mark Knecht wrote:


Hi,
  I had two machine that for some reason wouldn't build the 2.5 slot
for python. I've waited weeks for the possibility that something would
get cleaned up in portage or on a server somewhere but as of yet it
hasn't happened. For kicks today I cleaned out distfiles and did an
emerge -e @system but it failed the same way. I'm wondering what to
try next?

  Is it allowable to remove ebuilds by hand? Will an eix-sync get new
versions if ebuilds are missing and I change the servers that the
machine is pointing to?

  Looking for ideas about how to move forward.

Thanks,
Mark



  

What's the error message?

--Joshua Doll



Not much unfortunately:

Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xml/sax/xmlreader.py
...
Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmllib.py
...
Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmlrpclib.py
...
Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/zipfile.py
...
make: *** [libinstall] Error 1
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m ERROR: dev-lang/python-2.5.2-r7 failed.
 ^[[31;01m*^[[0m Call stack:
 ^[[31;01m*^[[0m   ebuild.sh, line   49:  Called src_install
 ^[[31;01m*^[[0m environment, line 3469:  Called die
 ^[[31;01m*^[[0m The specific snippet of code:
 ^[[31;01m*^[[0m   make DESTDIR=${D} altinstall maninstall || die;
 ^[[31;01m*^[[0m  The die message:
 ^[[31;01m*^[[0m   (no error message)
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m If you need support, post the topmost build error,
and the call stack if relevant.
 ^[[31;01m*^[[0m A complete build log is located at
'/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/build.log'.
 ^[[31;01m*^[[0m The ebuild environment file is located at
'/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/environment'.
 ^[[31;01m*^[[0m


  


I might be mistaken, but I don't think that is make error message. You 
might want to check further up in the build.log for more information.


--Joshua Doll



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-11 Thread Mark Knecht
On Wed, Feb 11, 2009 at 7:04 PM, Joshua D Doll joshua.d...@gmail.com wrote:
 Mark Knecht wrote:

 On Wed, Feb 11, 2009 at 6:25 PM, Joshua D Doll joshua.d...@gmail.com
 wrote:


 Mark Knecht wrote:


 Hi,
  I had two machine that for some reason wouldn't build the 2.5 slot
 for python. I've waited weeks for the possibility that something would
 get cleaned up in portage or on a server somewhere but as of yet it
 hasn't happened. For kicks today I cleaned out distfiles and did an
 emerge -e @system but it failed the same way. I'm wondering what to
 try next?

  Is it allowable to remove ebuilds by hand? Will an eix-sync get new
 versions if ebuilds are missing and I change the servers that the
 machine is pointing to?

  Looking for ideas about how to move forward.

 Thanks,
 Mark





 What's the error message?

 --Joshua Doll


 Not much unfortunately:

 Compiling
 /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xml/sax/xmlreader.py
 ...
 Compiling
 /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmllib.py
 ...
 Compiling
 /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmlrpclib.py
 ...
 Compiling
 /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/zipfile.py
 ...
 make: *** [libinstall] Error 1
  ^[[31;01m*^[[0m
  ^[[31;01m*^[[0m ERROR: dev-lang/python-2.5.2-r7 failed.
  ^[[31;01m*^[[0m Call stack:
  ^[[31;01m*^[[0m   ebuild.sh, line   49:  Called src_install
  ^[[31;01m*^[[0m environment, line 3469:  Called die
  ^[[31;01m*^[[0m The specific snippet of code:
  ^[[31;01m*^[[0m   make DESTDIR=${D} altinstall maninstall || die;
  ^[[31;01m*^[[0m  The die message:
  ^[[31;01m*^[[0m   (no error message)
  ^[[31;01m*^[[0m
  ^[[31;01m*^[[0m If you need support, post the topmost build error,
 and the call stack if relevant.
  ^[[31;01m*^[[0m A complete build log is located at
 '/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/build.log'.
  ^[[31;01m*^[[0m The ebuild environment file is located at
 '/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/environment'.
  ^[[31;01m*^[[0m




 I might be mistaken, but I don't think that is make error message. You might
 want to check further up in the build.log for more information.

 --Joshua Doll


Thanks. I really see nothing else in the file unless I'm just missing
it somehow. I've grepped the file for error/Error/ERROR. The only
thing that shows up is this for 'Error':
mkdir: cannot create directory `Include': File exists
make: [Include/graminit.h] Error 1 (ignored)
Parser/pgen ./Grammar/Grammar ./Include/graminit.h ./Python/graminit.c
mkdir: cannot create directory `Include': File exists
make: [Python/graminit.c] Error 1 (ignored)
Parser/pgen ./Grammar/Grammar ./Include/graminit.h ./Python/graminit.c

and this:

Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/test/test_multibytecodec.py
...
Sorry: UnicodeDecodeError: ('unicodeescape', '\\N{SOFT HYPHEN}', 0,
15, 'unknown Unicode character name')
Compiling 
/var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/test/test_multibytecodec_support.py
...

For kicks I erased the work directory which gets left around when a
build fails. That didn't help.

Mostly I was thinking if I knew what I could safely delete then I
could let emerge download new copies. I'm assuming that this is being
caused by some corrupted file on my machine, or on the server. If I
change servers then maybe I'll get a good copy, etc. It's weak but
this has been hanging around for a month. I've filed a bug. I haven't
heard a word from bugzilla folks. Not like the old days when you'd see
a response from someone within hours.

- Mark



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-11 Thread Mark Knecht
On Wed, Feb 11, 2009 at 7:04 PM, Joshua D Doll joshua.d...@gmail.com wrote:
SNIP

 I might be mistaken, but I don't think that is make error message. You might
 want to check further up in the build.log for more information.

 --Joshua Doll



CFLAGS? The machine that fails:

CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe
CHOST=i686-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2


A machine that passes:



Re: [gentoo-user] python-2.5.2-r7 build problems

2009-02-11 Thread Mark Knecht
On Wed, Feb 11, 2009 at 8:22 PM, Mark Knecht markkne...@gmail.com wrote:
 On Wed, Feb 11, 2009 at 7:04 PM, Joshua D Doll joshua.d...@gmail.com wrote:
 SNIP

 I might be mistaken, but I don't think that is make error message. You might
 want to check further up in the build.log for more information.

 --Joshua Doll



 CFLAGS? The machine that fails:

 CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe
 CHOST=i686-pc-linux-gnu
 CXXFLAGS=${CFLAGS}
 MAKEOPTS=-j2


 A machine that passes:


CFLAGS=-O2 -march=i686 -fomit-frame-pointer -pipe
CHOST=i686-pc-linux-gnu
CXXFLAGS=${CFLAGS}
MAKEOPTS=-j2