| View previous topic :: View next topic |
| Author |
Message |
roarkh n00b

Joined: 24 May 2003 Posts: 43 Location: Bellingham, Washington
|
Posted: Sun Feb 19, 2006 3:41 am Post subject: configure error expected absolute directory name for datadir |
|
|
I just did an emerge -u system and all went fine but now I can't seem to emerge anything else.
Here is some example output of what I am getting...
| Code: | ender roarkh # emerge -u gtk+
Calculating dependencies ...done!
>>> emerge (1 of 1) x11-libs/gtk+-2.8.12 to /
>>> checksums files ;-) gtk+-2.8.8.ebuild
>>> checksums files ;-) gtk+-1.2.10-r10.ebuild
>>> checksums files ;-) gtk+-1.2.10-r11.ebuild
>>> checksums files ;-) gtk+-2.8.12.ebuild
>>> checksums files ;-) gtk+-2.6.10-r1.ebuild
>>> checksums files ;-) gtk+-2.8.11.ebuild
>>> checksums files ;-) files/gtk+-1.2-locale_fix.patch
>>> checksums files ;-) files/digest-gtk+-1.2.10-r10
>>> checksums files ;-) files/digest-gtk+-1.2.10-r11
>>> checksums files ;-) files/gtk+-2.4.9-ppc64.patch
>>> checksums files ;-) files/gtk+-2.8.10-xinerama.patch
>>> checksums files ;-) files/digest-gtk+-2.8.12
>>> checksums files ;-) files/digest-gtk+-2.8.8
>>> checksums files ;-) files/gtkrc
>>> checksums files ;-) files/digest-gtk+-2.8.11
>>> checksums files ;-) files/gtk+-2.8.0-multilib.patch
>>> checksums files ;-) files/gtk+-2.2.1-disable_icons_smooth_alpha.patch
>>> checksums files ;-) files/digest-gtk+-2.6.10-r1
>>> checksums files ;-) files/gtk+-2-xpm_loader.patch
>>> checksums files ;-) files/gtk+-gdk-pixbuf-testfix.patch
>>> checksums files ;-) files/gtk+-1.2.10-m4.patch
>>> checksums src_uri ;-) gtk+-2.8.12.tar.bz2
>>> Unpacking source...
>>> Unpacking gtk+-2.8.12.tar.bz2 to /var/tmp/portage/gtk+-2.8.12/work
* Applying gtk+-2.2.1-disable_icons_smooth_alpha.patch ... [ ok ] * Applying gtk+-2.8.10-xinerama.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/gtk+-2.8.12/work/gtk+-2.8.12' ...
* Running aclocal -I . ... [ ok ] * Running autoconf ... [ ok ] * Running automake --add-missing --copy ... [ !! ]
* Failed Running automake !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/gtk+-2.8.12/temp/automake-9747.out
!!! ERROR: x11-libs/gtk+-2.8.12 failed.
Call stack:
ebuild.sh, line 1894: Called dyn_unpack
ebuild.sh, line 694: Called src_unpack
gtk+-2.8.12.ebuild, line 94: Called eautoreconf
autotools.eclass, line 68: Called eautomake
autotools.eclass, line 149: Called autotools_run_tool 'unpack' 'automake' '- -add-missing'
!!! Failed Running automake !
!!! If you need support, post the topmost build error, and the call stack if relevant. |
and...
| Code: | ender roarkh # emerge xscreensaver
Calculating dependencies ...done!
>>> emerge (1 of 1) x11-misc/xscreensaver-4.24 to /
>>> checksums files ;-) xscreensaver-4.23-r1.ebuild
>>> checksums files ;-) xscreensaver-4.22-r4.ebuild
>>> checksums files ;-) xscreensaver-4.24.ebuild
>>> checksums files ;-) files/xscreensaver-4.23-words.patch
>>> checksums files ;-) files/digest-xscreensaver-4.23-r1
>>> checksums files ;-) files/xscreensaver-4.24-norpm.patch
>>> checksums files ;-) files/xscreensaver-4.22-interaggregate.patch
>>> checksums files ;-) files/xscreensaver-4.22-nsfw-webcollage.patch
>>> checksums files ;-) files/digest-xscreensaver-4.24
>>> checksums files ;-) files/xscreensaver-4.16-nsfw.patch
>>> checksums files ;-) files/xscreensaver-4.23-app-defaults.patch
>>> checksums files ;-) files/xscreensaver-4.23-nsfw.patch
>>> checksums files ;-) files/xscreensaver-4.23-norpm.patch
>>> checksums files ;-) files/digest-xscreensaver-4.22-r4
>>> checksums files ;-) files/xscreensaver-4.22-configure.patch
>>> checksums files ;-) files/xscreensaver-blank-screen.patch
>>> checksums files ;-) files/xscreensaver-4.22-settings.patch
>>> checksums files ;-) files/xscreensaver-4.24-app-defaults.patch
>>> checksums files ;-) files/xscreensaver-4.24-nsfw.patch
>>> checksums files ;-) files/xscreensaver-4.24-settings.patch
>>> checksums files ;-) files/xscreensaver-4.24-silent.patch
>>> checksums files ;-) files/xscreensaver-4.24-words.patch
>>> checksums files ;-) files/desktop_entries/screensaver-properties.desktop
>>> checksums src_uri ;-) xscreensaver-4.24.tar.gz
>>> Unpacking source...
>>> Unpacking xscreensaver-4.24.tar.gz to /var/tmp/portage/xscreensaver-4.24/work
* Applying xscreensaver-4.24-norpm.patch ... [ ok ] * Applying xscreensaver-4.24-settings.patch ... [ ok ] * Applying xscreensaver-4.24-silent.patch ... [ ok ] * Applying xscreensaver-4.24-nsfw.patch ... [ ok ] * Applying xscreensaver-4.24-words.patch ... [ ok ] * Applying xscreensaver-4.24-app-defaults.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/xscreensaver-4.24/work/xscreensaver-4.24' ...
* Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Replacing obsolete head/tail with POSIX compliant ones
* - fixed Makefile.in
* - fixed driver/stderr.c
* - fixed hacks/fontglide.c
* - fixed hacks/glx/dolphin.c
* - fixed hacks/glx/fliptext.c
* - fixed hacks/glx/shark.c
* - fixed hacks/glx/starwars.c
* - fixed hacks/glx/whale.c
* - fixed hacks/worm.c
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/xscreensaver-4.24/work/xscreensaver-4.24 ...
* econf: updating xscreensaver-4.24/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating xscreensaver-4.24/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-hackdir=/usr/lib/misc/xscreensaver --with-configdir=/usr/share/xscreensaver/config --x-libraries=/usr/lib --x-includes=/usr/include --with-mit-ext --with-dpms-ext --with-xf86vmode-ext --with-xf86gamma-ext --with-proc-interrupts --with-xpm --with-xshm-ext --with-xdbe-ext --enable-locking --with-gtk --with-xml --without-setuid-hacks --without-login-manager --without-xinerama-ext --with-pam --with-gl --with-gle --with-jpeg --enable-nls --without-kerberos --build=i686-pc-linux-gnu
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
configure: error: expected an absolute directory name for --datadir:
!!! ERROR: x11-misc/xscreensaver-4.24 failed.
Call stack:
ebuild.sh, line 1894: Called dyn_compile
ebuild.sh, line 941: Called src_compile
xscreensaver-4.24.ebuild, line 113: Called econf 'compile' '--with-hackdir=/usr/lib/misc/xscreensaver' '--with-configdir=/usr/share/xscreensaver/config' '--x-libraries=/usr/lib' '--x-includes=/usr/include' '--with-mit-ext' '--with-dpms-ext' '--with-xf86vmode-ext' '--with-xf86gamma-ext' '--with-proc-interrupts' '--with-xpm' '--with-xshm-ext' '--with-xdbe-ext' '--enable-locking' '--with-gtk' '--with-xml' '--without-setuid-hacks' '--without-login-manager' '--without-xinerama-ext' '--with-pam' '--with-gl' '--with-gle' '--with-jpeg' '--enable-nls'
!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant. |
and one more...
| Code: | ender roarkh # emerge -u eject
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/eject-2.1.4 to /
>>> checksums files ;-) eject-2.1.4.ebuild
>>> checksums files ;-) eject-2.0.13-r1.ebuild
>>> checksums files ;-) eject-2.0.13-r2.ebuild
>>> checksums files ;-) eject-2.1.0-r1.ebuild
>>> checksums files ;-) files/eject-2.0.13-autoclose.patch
>>> checksums files ;-) files/digest-eject-2.0.13-r1
>>> checksums files ;-) files/digest-eject-2.1.4
>>> checksums files ;-) files/eject-2.0.13-use-mountpoints.patch
>>> checksums files ;-) files/eject-2.0.13-finddev.patch
>>> checksums files ;-) files/eject-2.0.13-header.patch
>>> checksums files ;-) files/eject-2.0.13-kernel25-support.patch
>>> checksums files ;-) files/eject-2.0.13-close-check.patch
>>> checksums files ;-) files/digest-eject-2.0.13-r2
>>> checksums files ;-) files/eject-2.0.13-fstab-error.patch
>>> checksums files ;-) files/eject-2.0.13-no-umount.patch
>>> checksums files ;-) files/eject-2.0.13-toggle.patch
>>> checksums files ;-) files/eject-2.0.13-prefix-defaultdevice-with-dev.patch
>>> checksums files ;-) files/eject-2.0.13-xmalloc.patch
>>> checksums files ;-) files/eject-2.0.13-xregcomp.patch
>>> checksums files ;-) files/eject-2.0.13-pumount.patch
>>> checksums files ;-) files/eject-2.0.13-i18n-uclibc.patch
>>> checksums files ;-) files/eject-2.1.0-regcomp-check.patch
>>> checksums files ;-) files/eject-2.1.0-scsi-io-update.patch
>>> checksums files ;-) files/digest-eject-2.1.0-r1
>>> checksums files ;-) files/eject-2.1.0-toggle.patch
>>> checksums files ;-) files/eject-2.1.4-toggle.patch
>>> checksums src_uri ;-) eject-2.1.4.tar.gz
>>> Unpacking source...
>>> Unpacking eject-2.1.4.tar.gz to /var/tmp/portage/eject-2.1.4/work
* Applying eject-2.0.13-xmalloc.patch ... [ ok ] * Applying eject-2.1.4-toggle.patch ... [ ok ]>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/eject-2.1.4/work/eject ...
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
configure: error: expected an absolute directory name for --datadir:
!!! ERROR: sys-apps/eject-2.1.4 failed.
Call stack:
ebuild.sh, line 1894: Called dyn_compile
ebuild.sh, line 941: Called src_compile
ebuild.sh, line 589: Called econf
!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant. |
I have tried emerging other packages as well and all fail with one thing in common (more or less)...
| Code: | Call stack:
ebuild.sh, line 1894: Called dyn_compile
ebuild.sh, line 941: Called src_compile
ebuild.sh, line 589: Called econf
|
Maybe I am not searching for the right terms but I have not been able to find a solution on the forums. Can anyone help?
It's much appreciated.
Roark
Mod Edit: made sticky and changed the title from "Emerge -u failing on all packages [Solved]" to "configure error expected absolute directory name for datadir" - tomk
Edit: Unstuck (2006-03-11) --Maedhros
Last edited by roarkh on Mon Feb 20, 2006 9:05 pm; edited 1 time in total |
|
| Back to top |
|
 |
embobo Guru

Joined: 19 May 2003 Posts: 311
|
Posted: Sun Feb 19, 2006 4:26 am Post subject: |
|
|
I have the same problem. This may be ugly. Did you just upgrade glibc?
Try this command:
It should return 'a':
| Code: |
cthulhu ~ # /mirror/cthulhu/_/daily.0/bin/expr a : '\(a\)'
a
cthulhu ~ #
|
Mine doesn't:
| Code: |
cthulhu ~ # expr a : '\(a\)'
cthulhu ~ #
|
On an AMD64 box:
| Code: |
freddy ~ # expr a : '\(a\)'
Segmentation fault
freddy ~ #
|
I suspect glibc is FUBAR.
Edit: Forgot to add
Edit2: Maybe it is coreutils 5.94. |
|
| Back to top |
|
 |
roarkh n00b

Joined: 24 May 2003 Posts: 43 Location: Bellingham, Washington
|
Posted: Sun Feb 19, 2006 4:45 am Post subject: |
|
|
Thanks for your reply. I did just upgrade glibc.
When I try your command this is what I get...
| Code: | ender roarkh # expr a : '\(a\)'
expr: error in regular expression matcher: Value too large for defined data typee |
I suppose this is the price I pay for running unstable! |
|
| Back to top |
|
 |
bincache n00b

Joined: 19 Feb 2006 Posts: 17
|
Posted: Sun Feb 19, 2006 4:45 am Post subject: Same issue |
|
|
Same problem, just did an emerge -u portage to grab the latest version, seemed to work fine glibc was one of the updated pacakges, but the rest of the package list is out of my scroll buffer so I can't paste it.
Any emerge results in about the same thing, failure on expr with the message below:
| Code: |
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/eject-2.1.4/work/eject ...
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
expr: error in regular expression matcher: Value too large for defined data type
configure: error: expected an absolute directory name for --datadir:
!!! ERROR: sys-apps/eject-2.1.4 failed.
!!! Function econf, Line 489, Exitcode 0
!!! econf failed
|
etc etc...
Any ideas? I'm currently scanning the board for related info but nothing else has come up just yet.
Thanks regardless. |
|
| Back to top |
|
 |
embobo Guru

Joined: 19 May 2003 Posts: 311
|
Posted: Sun Feb 19, 2006 4:49 am Post subject: Re: Same issue |
|
|
| bincache wrote: |
Any ideas? I'm currently scanning the board for related info but nothing else has come up just yet.
|
Still investigating. I tentatively think coreutils 5.94 is the problem. Of course, you can't simply emerge the old coreutils since autoconf uses coreutils. You need to restore it from backup. I have an online backup so I copied everything listed in /var/db/pkg/sys-apps/coreutils-5.94/CONTENTS from the backup. |
|
| Back to top |
|
 |
bincache n00b

Joined: 19 Feb 2006 Posts: 17
|
Posted: Sun Feb 19, 2006 4:57 am Post subject: Re: Same issue |
|
|
| embobo wrote: |
Still investigating. I tentatively think coreutils 5.94 is the problem. Of course, you can't simply emerge the old coreutils since autoconf uses coreutils. You need to restore it from backup. I have an online backup so I copied everything listed in /var/db/pkg/sys-apps/coreutils-5.94/CONTENTS from the backup. |
Eh worth a try. I'm logging into my other box and building a bunch of binary packages for the broken system so I can test them and see which fixes what. Like trying to find a needle in a haystack in a dark room, but it's something to keep me busy. :) |
|
| Back to top |
|
 |
Genone Retired Dev


Joined: 14 Mar 2003 Posts: 8690 Location: beyond the rim
|
Posted: Sun Feb 19, 2006 5:05 am Post subject: |
|
|
| For the record: I'm on an ~amd64 system here with coreutils-5.94, bash-3.1_p8 and glibc-2.3.6-r2 and not seeing any of the mentioned problems, maybe that helps in narrowing it down. |
|
| Back to top |
|
 |
bincache n00b

Joined: 19 Feb 2006 Posts: 17
|
Posted: Sun Feb 19, 2006 5:06 am Post subject: |
|
|
Results:
I created a binary package for coreutils-5.93 and coreutils-5.94 as well as glibc
When I reverted glibc the problem persisted, but when I reverted to coreutils-5.93 the problem went away.
Seems to me that your tentitive guess was correct. :)
Thanks for the help! :D
Edit:
~x86 with coreutils-5.94 bash-3.1_p8 glibc-2.3.6-r3 <- Problem persists in this setup
Downgrading to coreutils-5.93 fixed it
Last edited by bincache on Sun Feb 19, 2006 5:11 am; edited 1 time in total |
|
| Back to top |
|
 |
embobo Guru

Joined: 19 May 2003 Posts: 311
|
Posted: Sun Feb 19, 2006 5:09 am Post subject: Re: Same issue |
|
|
| bincache wrote: | Eh worth a try. I'm logging into my other box and building a bunch of binary packages for the broken system so I can test them and see which fixes what. Like trying to find a needle in a haystack in a dark room, but it's something to keep me busy.  |
I now think it is coreutils. A new glibc is always raises my suspicion too. Perhaps there is an interaction there. For now I have gone back to coreutils 5.93 and have emerged a few packages with success.
Making a quickpkg on a coreutils 5.93 system may be another way to fix the problem.
Something to keep you busy...on a Saturday night? Then again, what am I doing? I am a blackish pot myself.  |
|
| Back to top |
|
 |
bincache n00b

Joined: 19 Feb 2006 Posts: 17
|
Posted: Sun Feb 19, 2006 5:12 am Post subject: Re: Same issue |
|
|
| embobo wrote: | | bincache wrote: | | Eh worth a try. I'm logging into my other box and building a bunch of binary packages for the broken system so I can test them and see which fixes what. Like trying to find a needle in a haystack in a dark room, but it's something to keep me busy. :) |
I now think it is coreutils. A new glibc is always raises my suspicion too. Perhaps there is an interaction there. For now I have gone back to coreutils 5.93 and have emerged a few packages with success.
Making a quickpkg on a coreutils 5.93 system may be another way to fix the problem.
Something to keep you busy...on a Saturday night? Then again, what am I doing? I am a blackish pot myself. :D |
I'm stuck sick at home, so what better things are there to do than play with my computer. :P |
|
| Back to top |
|
 |
hbk3131 n00b

Joined: 08 Aug 2005 Posts: 3
|
Posted: Sun Feb 19, 2006 5:28 am Post subject: re: |
|
|
I'm not saying it is definatly a coreutils(package providing expr) problem but 'expr' is returning the wrong values and i atleast was able to copy the /bin/expr from a stage3 tarball ( both amd64 and x86 worked for eaches selected arch) to get a temp fix the problem. I'm downgrading coreutils on a emerge -e world right now so I'll get back to you if it work
[Amd64]
expr a : '\(a\)'
Segfault (should return a)
expr help : '(help)'
4294967295 ( should return 0)
expr help : help
4 (should return 4, This is ok on amd64)
[x86]
expr a : '\(a\)'
(should return a)
expr help : '(help)'
4294967295 ( should return 0)
expr help : help
577921419141185540 (should return 4)
Downgrade of coreutils-5.93 does resolve this issue
~x86 with coreutils-5.94 bash-3.1_p8 glibc-2.3.6-r3 <--- Agreed
~amd64 with coreutils-5.94 bash-3.1_p8 glibc-2.3.6-r3 <---Also problem
Last edited by hbk3131 on Sun Feb 19, 2006 8:47 am; edited 1 time in total |
|
| Back to top |
|
 |
Grooby n00b

Joined: 08 Jun 2005 Posts: 47
|
Posted: Sun Feb 19, 2006 5:31 am Post subject: |
|
|
arg...i am having this problem...but i can't even emerge =coreutils-5.93....any idea?
[edit]
nevermind..i am a retard...
scp expr from my other amd64 box (which for some reason, was able to use the new coreutils and the new glib) to my broken box, reemerge coreutils 5.93, and everything seems ok. Might re-emerge 5.94 again later just to see...
[edit]
ok...so after all that and re-emerge coreutils 5.94, expr broke again. copy it from my other box and continue....now the question is..how do we submit this bug?
Last edited by Grooby on Sun Feb 19, 2006 6:37 am; edited 1 time in total |
|
| Back to top |
|
 |
friedmud Apprentice


Joined: 18 Apr 2002 Posts: 258 Location: Austin, TX USA
|
Posted: Sun Feb 19, 2006 6:28 am Post subject: |
|
|
Just like to note that I am also having this problem...
I had unfortunately put ~x86 into my accept_keywords on my laptop (doing some testing... I know I know it shouldn't be done that way blah blah blah and forgot to take it out before doing an emerge -u world..... doh
This is what I get for not following the rules I suppose...
It's too late to grab a livecd and get this fixed... it'll have to wait for tomorrow (my desktop is AMD64... so I can't just grab it off there).
Friedmud |
|
| Back to top |
|
 |
meebee n00b

Joined: 09 Feb 2006 Posts: 4
|
Posted: Sun Feb 19, 2006 10:50 am Post subject: |
|
|
Copying /bin/expr from an older installation solved the problem for me.
I didn't have to downgrade the complete coreutils package. |
|
| Back to top |
|
 |
chunderbunny Veteran


Joined: 31 May 2004 Posts: 1281 Location: 51°24'27" N, 0°57'15" W
|
Posted: Sun Feb 19, 2006 10:57 am Post subject: |
|
|
| According to bug 123342 this is actually a problem with the new bash. |
|
| Back to top |
|
 |
gruftie Apprentice

Joined: 24 Sep 2002 Posts: 161
|
Posted: Sun Feb 19, 2006 1:26 pm Post subject: |
|
|
| chunderbunny wrote: | | According to bug 123342 this is actually a problem with the new bash. |
can someone please provide me the expr-binary from the amd64-debian package mentioned in comment #5 in the above-named bug? i don't have the dpgk ebuild installed and can't do it, as it dies with the same expr-error.
thanks in advance _________________ --
Notebook: Sony VAIO VGN-AR71S
Intel Core2 Duo T9300@2.5GHz; 4GB RAM; 2x250GB HD; Blu-Ray Recorder; GeForce 8600M GT; Gentoo64 unstable
Server: AMD Athlon64 3500+; 3GB RAM; 1TB storage; Gentoo64 unstable
. |
|
| Back to top |
|
 |
Genone Retired Dev


Joined: 14 Mar 2003 Posts: 8690 Location: beyond the rim
|
Posted: Sun Feb 19, 2006 1:37 pm Post subject: |
|
|
| In case anybody is interested in doing some testing, I've uploaded my working expr binary from coreutils-5.94 install to dev.gentoo.org/~genone/temp/expr, I'd be curious if it works or fails for people who got the problem fixed by downgrading coreutils. |
|
| Back to top |
|
 |
RaZoR1394 Guru


Joined: 09 Jan 2005 Posts: 356
|
Posted: Sun Feb 19, 2006 1:42 pm Post subject: |
|
|
Didn't see this thread... It's the same problem I had. As I see dpgk doesn't emerge but what you could do is emerge deb2targz. It should emerge fine and then you can convert the .deb package to *.tar.gz. If I have time I can upload all the 5.93 coreutils expr binaries to my server. _________________ http://en.wikipedia.org/wiki/Cell_(microprocessor) |
|
| Back to top |
|
 |
gruftie Apprentice

Joined: 24 Sep 2002 Posts: 161
|
Posted: Sun Feb 19, 2006 1:50 pm Post subject: |
|
|
| RaZoR1394 wrote: | | Didn't see this thread... It's the same problem I had. As I see dpgk doesn't emerge but what you could do is emerge deb2targz. It should emerge fine and then you can convert the .deb package to *.tar.gz. If I have time I can upload all the 5.93 coreutils expr binaries to my server. |
this works, thank you  _________________ --
Notebook: Sony VAIO VGN-AR71S
Intel Core2 Duo T9300@2.5GHz; 4GB RAM; 2x250GB HD; Blu-Ray Recorder; GeForce 8600M GT; Gentoo64 unstable
Server: AMD Athlon64 3500+; 3GB RAM; 1TB storage; Gentoo64 unstable
. |
|
| Back to top |
|
 |
Maedhros Bodhisattva


Joined: 14 Apr 2004 Posts: 5511 Location: Durham, UK
|
Posted: Sun Feb 19, 2006 1:53 pm Post subject: |
|
|
I've just managed to get expr to segfault when I rebuilt coreutils with the acl USE flag. Without it, no segfaults. _________________ No-one's more important than the earthworm. |
|
| Back to top |
|
 |
RaZoR1394 Guru


Joined: 09 Jan 2005 Posts: 356
|
|
| Back to top |
|
 |
Genone Retired Dev


Joined: 14 Mar 2003 Posts: 8690 Location: beyond the rim
|
Posted: Sun Feb 19, 2006 1:59 pm Post subject: |
|
|
| Maedhros wrote: | | I've just managed to get expr to segfault when I rebuilt coreutils with the acl USE flag. Without it, no segfaults. |
Now that gets even more weird: Most people who reported problems at bugzilla don't have the acl flag set, I have it set and don't have any problems :-/ |
|
| Back to top |
|
 |
nesl247 Veteran

Joined: 15 Jun 2004 Posts: 1614 Location: Florida
|
Posted: Sun Feb 19, 2006 2:05 pm Post subject: |
|
|
| I don't get any errors with coreutils. Using nxsty's glibc 2.3.90 overlay if it ever comes down to glibc.. |
|
| Back to top |
|
 |
agent_jdh Veteran

Joined: 08 Aug 2002 Posts: 1767 Location: Scotland
|
Posted: Sun Feb 19, 2006 2:27 pm Post subject: |
|
|
I've got this problem here, but it only seems to have appeared for me with coreutils-5.94-patches-1.2.tar.bz2. 5.94 worked fine here with the old patchset 1.1.
I'll try going back to the older patchset (if I can) when I've got a minute to spare.
EDIT - Doh! of course, coreutils won't build now because of the problem, so I can't check right now, but the fact it now won't build when it did 30 minutes ago convinces me even more that it's the 1.2 patchset that's the problem here.
EDIT #2 - Oh well, it isn't patchset 1.2. Downgraded to 1.1 and things are still broken. 5.94 now masked. _________________ Jingle Jangle Jewellery
Last edited by agent_jdh on Sun Feb 19, 2006 2:42 pm; edited 2 times in total |
|
| Back to top |
|
 |
Konsti l33t


Joined: 10 Dec 2002 Posts: 688
|
Posted: Sun Feb 19, 2006 2:28 pm Post subject: |
|
|
The expr replacement worked fine.
That was a bit more eaysy than messing with a stage3 chroot  _________________ konsti@jabber.org |
|
| Back to top |
|
 |
|