View previous topic :: View next topic |
Author |
Message |
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Mon Apr 26, 2010 3:35 pm Post subject: Lots of things fail to emerge -- RESOLVED |
|
|
Here is the error from on example Quote: | Running Mkbootstrap for XML::Parser::Expat ()
cp Expat.pm ../blib/lib/XML/Parser/Expat.pm
chmod 644 Expat.bs
cp Expat.bs ../blib/arch/auto/XML/Parser/Expat/Expat.bs
chmod 644 ../blib/arch/auto/XML/Parser/Expat/Expat.bs
x86_64-pc-linux-gnu-gcc -c -fno-strict-aliasing -pipe -fstack-protector -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -march=native -ftree-vectorize -floop-interchange -floop-strip-mine -floop-block -pipe -DVERSION=\"2.36\" -DXS_VERSION=\"2.36\" -fPIC "-I/usr/lib64/perl5/5.10.1/x86_64-linux/CORE" Expat.c
Expat.c:1: sorry, unimplemented: Graphite loop optimizations cannot be used
Expat.xs: In function 'append_error':
Expat.xs:220: warning: format '%d' expects type 'int', but argument 4 has type 'XML_Size'
Expat.xs:220: warning: format '%d' expects type 'int', but argument 5 has type 'XML_Size'
Expat.xs:220: warning: format '%d' expects type 'int', but argument 6 has type 'XML_Index'
make[1]: *** [Expat.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/dev-perl/XML-Parser-2.36-r1/work/XML-Parser-2.36/Expat'
make: *** [subdirs] Error 2
* ERROR: dev-perl/XML-Parser-2.36-r1 failed:
* compilation failed
|
I have been getting similar errors on other packages. I have been using graphite, but on this emerge I had -graphite in my use flag. I also tried this after a re-emerge of expat, which in turn does not seem to depend on graphite and still get the same error. Do I need to re-emerge gcc using -graphite? Help! Thanks,
Fred
Last edited by Fred Krogh on Tue Apr 27, 2010 4:08 am; edited 1 time in total |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Mon Apr 26, 2010 8:50 pm Post subject: |
|
|
Just for the record, I've re-emerged gcc with "-graphite", and I'm getting the same sort of error. According to equery, gcc is the only package on my system that references the graphite use flag. For the time being I'm stuck with a system where it seems most packages can not be emerged. |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10587 Location: Somewhere over Atlanta, Georgia
|
Posted: Mon Apr 26, 2010 8:56 pm Post subject: |
|
|
First, try compiling the failing package with vanilla CFLAGS/CXXFLAGS to see if the error will go away. Vanilla would just be Code: | -march=native -pipe | - John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Mon Apr 26, 2010 9:02 pm Post subject: |
|
|
I am now using Quote: | CFLAGS="-O2 -march=native -pipe"
CXXFLAGS="${CFLAGS}" | When using graphite I was using Quote: | CFLAGS="-O2 -march=native -ftree-vectorize -floop-interchange -floop-strip-mine -floop-block -pipe" | . That has been working for a long long time. I appreciate your suggestion. I've tried your suggestion with my current gcc, and it fails in the same way. I'll try recompiling gcc as you suggested if I really get desperate, but I think the problem must be elsewhere. |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10587 Location: Somewhere over Atlanta, Georgia
|
Posted: Mon Apr 26, 2010 9:07 pm Post subject: |
|
|
You mean that the error message looks exactly the same, including all of those extreme loop optimization flags being passed to the compiler?
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Mon Apr 26, 2010 9:16 pm Post subject: |
|
|
I'm sorry, I think you may be on to something. The error message looks like Quote: | x86_64-pc-linux-gnu-gcc -c -I. -fno-strict-aliasing -pipe -fstack-protector -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -march=native -ftree-vectorize -floop-interchange -floop-strip-mine -floop-block -pipe -DVERSION=\"2.027\" -DXS_VERSION=\"2.027\" -fPIC "-I/usr/lib64/perl5/5.10.1/x86_64-linux/CORE" -Wall -Wno-comment -DBZ_NO_STDIO -DUSE_PPPORT_H Bzip2.c
Bzip2.c:1: sorry, unimplemented: Graphite loop optimizations cannot be used
make: *** [Bzip2.o] Error 1
* ERROR: perl-core/Compress-Raw-Bzip2-2.027 failed:
| So the flags are not what I think they should be. I was under the impression that the flags used were those in /etc/make.conf, and there the flags only include "-march=native". Can you tell me where these flags are getting set? Thanks. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21490
|
Posted: Tue Apr 27, 2010 2:49 am Post subject: |
|
|
Fred Krogh wrote: | I'm sorry, I think you may be on to something. The error message looks like Quote: | x86_64-pc-linux-gnu-gcc -c -I. -fno-strict-aliasing -pipe -fstack-protector -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -march=native -ftree-vectorize -floop-interchange -floop-strip-mine -floop-block -pipe -DVERSION=\"2.027\" -DXS_VERSION=\"2.027\" -fPIC "-I/usr/lib64/perl5/5.10.1/x86_64-linux/CORE" -Wall -Wno-comment -DBZ_NO_STDIO -DUSE_PPPORT_H Bzip2.c
Bzip2.c:1: sorry, unimplemented: Graphite loop optimizations cannot be used
make: *** [Bzip2.o] Error 1
* ERROR: perl-core/Compress-Raw-Bzip2-2.027 failed:
| So the flags are not what I think they should be. I was under the impression that the flags used were those in /etc/make.conf, and there the flags only include "-march=native". Can you tell me where these flags are getting set? Thanks. | They should be. However, some packages have an unfortunate habit of recording the $CFLAGS with which they were built and applying them to dependent packages. Since you are trying to build a Perl module, I would start by examining core Perl functionality. On my system, a file from dev-lang/perl has recorded copies of my $CFLAGS. Rebuilding dev-lang/perl may help you. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Tue Apr 27, 2010 4:08 am Post subject: |
|
|
Emerging dev-lang/perl fixed the problem. Thank you very much. There seems to be some hidden ugliness in how this stuff works. |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10587 Location: Somewhere over Atlanta, Georgia
|
Posted: Tue Apr 27, 2010 12:51 pm Post subject: |
|
|
Hu wrote: | However, some packages have an unfortunate habit of recording the $CFLAGS with which they were built and applying them to dependent packages. | Wow.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
Fred Krogh Veteran
Joined: 07 Feb 2005 Posts: 1036 Location: Tujunga, CA
|
Posted: Tue Apr 27, 2010 2:02 pm Post subject: |
|
|
I regard this sort of problem has a bug and have filed a bug report,
https://bugs.gentoo.org/show_bug.cgi?id=317479
Last edited by Fred Krogh on Tue Apr 27, 2010 4:18 pm; edited 2 times in total |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10587 Location: Somewhere over Atlanta, Georgia
|
Posted: Tue Apr 27, 2010 3:46 pm Post subject: |
|
|
You need to fix up your link.
I'm interested in the result either way, but it may not be a bug, but rather an intentionally implemented Band-Aid to address abstruse requirements of some Perl dependencies.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
|