Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 299252 - fail to emerge dev-lang/perl (make fails because of invalid preprocessing directives)
Summary: fail to emerge dev-lang/perl (make fails because of invalid preprocessing dir...
Status: VERIFIED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-01 19:15 UTC by Martin
Modified: 2010-01-01 22:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
environment (environment,113.42 KB, text/plain)
2010-01-01 19:18 UTC, Martin
Details
build.log (build.log,30.71 KB, text/plain)
2010-01-01 19:20 UTC, Martin
Details
emerge --info (emerge_info.txt,3.75 KB, text/plain)
2010-01-01 19:21 UTC, Martin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2010-01-01 19:15:53 UTC
I am not able to emerge dev-lang/perl-5.8.8-r8 or re-emerge dev-lang/perl-5.8.8-r5

Reproducible: Always

Steps to Reproduce:
1. emerge =dev-lang/perl-5.8.8-r5




make[2]: Entering directory `/var/tmp/portage/dev-lang/perl-5.8.8-r5/work/perl-5.8.8/x2p'           
echo Makefile.SH cflags.SH | tr ' ' '\n' >.shlist                                                   
make[2]: Leaving directory `/var/tmp/portage/dev-lang/perl-5.8.8-r5/work/perl-5.8.8/x2p'            
Updating makefile...                                                                                
make[1]: Leaving directory `/var/tmp/portage/dev-lang/perl-5.8.8-r5/work/perl-5.8.8/x2p'            
Now you must run 'make'.                                                                            

If you compile perl5 on a different machine or from a different object
directory, copy the Policy.sh file from this object directory to the  
new one before you run Configure -- this will help you with most of   
the policy defaults.                                                  

`sh  cflags "optimize='-O2 -march=i686 -pipe'" miniperlmain.o` -fPIC miniperlmain.c
          CCCMD =  i686-pc-linux-gnu-gcc -DPERL_CORE -c -fno-strict-aliasing -pipe -Wdeclaration-after-statement -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -march=i686 -pipe  -Wall                                                                                                
In file included from perl.h:37,                                                                    
                 from miniperlmain.c:36:                                                            
config.h:2340:3: error: invalid preprocessing directive #HAS_MSG_CTRUNC                             
config.h:2341:3: error: invalid preprocessing directive #HAS_MSG_DONTROUTE                          
config.h:2342:3: error: invalid preprocessing directive #HAS_MSG_OOB                                
config.h:2343:3: error: invalid preprocessing directive #HAS_MSG_PEEK                               
config.h:2344:3: error: invalid preprocessing directive #HAS_MSG_PROXY                              
config.h:2345:3: error: invalid preprocessing directive #HAS_SCM_RIGHTS                             
make: *** [miniperlmain.o] Error 1                                                                  
 *                                                                                                  
 * ERROR: dev-lang/perl-5.8.8-r5 failed.                                                            
 * Call stack:                                                                                      
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2644:  Called die
 * The specific snippet of code:
 *       emake -j1 || die "Unable to make"
 *  The die message:
 *   Unable to make
Comment 1 Martin 2010-01-01 19:18:56 UTC
Created attachment 214868 [details]
environment
Comment 2 Martin 2010-01-01 19:20:00 UTC
Created attachment 214870 [details]
build.log
Comment 3 Martin 2010-01-01 19:21:08 UTC
Created attachment 214871 [details]
emerge --info
Comment 4 Martin 2010-01-01 19:24:47 UTC
It would be great if someone could have a look at this.  It's a complete mystery to me.  Unfortunately, a lot of packages depend on perl, so I am not able to update a whole lot of my world.

Thanks,
Martin
Comment 5 Rafał Mużyło 2010-01-01 20:06:14 UTC
Most probably, not really a mystery:
> /usr/local/bin/echo
Clean your /usr/local.
Comment 6 Martin 2010-01-01 22:29:27 UTC
That helped, thanks Rafal.  I only had to delete /usr/local/bin/echo which was an empty file and I have no clue where it came from.