Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 3383 - Unable to emerge rcs - fails on make error 139
Summary: Unable to emerge rcs - fails on make error 139
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Brandon Low (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-04 11:48 UTC by nailed_barnacle
Modified: 2003-02-04 19:42 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nailed_barnacle 2002-06-04 11:48:36 UTC
With the current 1.1a build with working X, icewm, and kde, 'emerge lyx'  
reliably fails while trying to emerge rcs. The output leading up to the error  
is as follows:  
  
---------------------  
./conf.sh: configuring #include <vfork.h> ... commenting it out  
./conf.sh: configuring has_sys_param_h ... OK  
./conf.sh: configuring errno ... OK  
./conf.sh: configuring has_readlink, readlink_isreg_errno ... 1, EINVAL  
./conf.sh: configuring mode_t ... OK  
./conf.sh: configuring off_t ... OK  
./conf.sh: configuring pid_t ... OK  
./conf.sh: configuring sig_atomic_t ... OK  
./conf.sh: configuring size_t ... OK  
./conf.sh: configuring ssize_t ... OK  
./conf.sh: configuring time_t ... OK  
./conf.sh: configuring uid_t ... OK  
./conf.sh: configuring const ... OK  
./conf.sh: configuring volatile ... OK  
./conf.sh: configuring has_prototypes, has_stdarg, has_varargs, va_start_args  
...  
1, 1, -1, 2  
./conf.sh: configuring bad_chmod_close ... OK  
./conf.sh: configuring bad_creat0 ... will work around bug  
./conf.sh: configuring bad_fopen_wplus ... OK  
./conf.sh: configuring has_attribute_noreturn ... OK  
./conf.sh: configuring has_dirent, void_closedir ... OK  
./conf.sh: configuring has_fchmod ... does not work  
./conf.sh: configuring has_fflush_input ... OK  
./conf.sh: configuring has_fputs ... OK  
./conf.sh: configuring has_ftruncate ... OK  
./conf.sh: configuring has_getuid ... OK  
./conf.sh: configuring has_getpwuid ... OK  
./conf.sh: configuring has_kill ... OK  
./conf.sh: configuring has_memcmp ... OK  
./conf.sh: configuring has_memcpy ... OK  
./conf.sh: configuring has_memmove ... OK  
./conf.sh: configuring has_map_fd, has_mmap, has_madvise, mmap_signal ...  
make[1]: Leaving directory `/var/tmp/portage/rcs-5.7-r1/work/rcs-5.7/src'  
   ...done!  
>>> emerge app-text/rcs-5.7-r1 to /  
>>> md5 ;-) rcs-5.7.tar.gz  
!!! emerge aborting on  /usr/portage/app-text/rcs/rcs-5.7-r1.ebuild .  
  
make[1]: *** [conf.h] Error 139  
make: *** [all] Error 2  
make[1]: *** [conf.h] Error 139  
make: *** [all] Error 2  
  
!!! ERROR: The ebuild did not complete successfully.  
!!! Function src_compile, Line 9, Exitcode 2  
!!! (no error message)  
  
------------------  
  
All other dependencies for lyx can be emerged. This also fails if only emerge  
rcs is attempted.  
 
System has 400MB free on / and approx 6G free on /usr/local and /home. 
750MB ram, 750MHz Duron processor. 
  
Regards,  
  
Neil Barnes
Comment 1 Dan Armak (RETIRED) gentoo-dev 2002-06-04 12:02:02 UTC
This is a problem with the rcs ebuild, and has nothing to do with lyx. I'm changing the title appropriately. 
Comment 2 Brandon Low (RETIRED) gentoo-dev 2002-06-04 20:21:09 UTC
Hmm, works here on my gcc-3.1 system, what compiler/other system tools versions
are you using?
Comment 3 nailed_barnacle 2002-06-05 15:34:25 UTC
Erm... I'm using the default stage three build, as of last friday.  
 
# gcc --version 
2.95.3 
 
# make --version 
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. 
Built for i686-pc-linux-gnu 
 
# automake --version 
automake (GNU automake) 1.4-p5 
 
# bash --version 
GNU bash, version 2.05a.0(1)-release (i686-pc-linux-gnu) 
 
Anything else? I'll try and emerge the 3.1 gcc and see what happens... 
 
Neil 
 
Comment 4 Brandon Low (RETIRED) gentoo-dev 2002-06-05 15:40:45 UTC
Well I just had carpaski@gentoo.org test it on his 2.95.3 box and it worked
there too, the way it is crashing there looks like it may be a glibc issue, if
you haven't already keep your gcc-2.95.3, remerge glibc and then try it.
Comment 5 nailed_barnacle 2002-06-06 15:45:31 UTC
Sorry guys, 
 
Still using gcc 2.95.3, emerged glibc again (no errors) but still got the same 
problem :( 
 
Neil 
Comment 6 Michael Cohen (RETIRED) gentoo-dev 2002-06-06 20:55:12 UTC
works for me with 3.1
Comment 7 Brandon Low (RETIRED) gentoo-dev 2002-06-06 20:57:27 UTC
Works for us, check for possible other problems with your system...
Comment 8 Brandon Low (RETIRED) gentoo-dev 2002-06-06 21:01:54 UTC
you might try running memtest86 on your system because Micheal and I have a
feeling that it could be hardware related.
Comment 9 nailed_barnacle 2002-06-07 00:44:10 UTC
Will try the memtest later today. No doubt it will take a little while to run, 
I'll get back in a couple of days :) 
 
Neil