| Summary: | gnome-session-2.10.0-r2 ebuild fails during ./configure process | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Eldon Balzer <ebalzer> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | ||
| Priority: | High | ||
| Version: | 2005.0 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | The config.log of the failed build attempt | ||
|
Description
Eldon Balzer
2005-07-21 14:06:34 UTC
Created attachment 64012 [details]
The config.log of the failed build attempt
This is the config.log file from a result os using the following command:
'USE="-esd" emerge -v gnome-session'. The same results happen if I leave the
esd USE field enabled.
I have gone through the config.log and the console output. and have found the
following error is what is causing it to fail:
./configure: line 20694: syntax error near unexpected token `echo'
./configure: line 20694: `echo "$as_me:$LINENO: checking whether ESounD support
is requested" >&5'
Here's what the code looks like:
20694 PKG_PROG_PKG_CONFIG()
20695
20696
20697 echo "$as_me:$LINENO: checking whether ESounD support is requested" >&5
20698 echo $ECHO_N "checking whether ESounD support is requested... $ECHO_C" >&6
20699 # Check whether --enable-esd or --disable-esd was given.
20700 if test "${enable_esd+set}" = set; then
20701 enableval="$enable_esd"
20702 enable_esd=$enableval
20703 else
20704 enable_esd=yes
20705 fi;
20706 echo "$as_me:$LINENO: result: $enable_esd" >&5
20707 echo "${ECHO_T}$enable_esd" >&6
*IF* I comment out lines 20697 and 20698 the ./configure process finishes
normally! I'm not a programmer... so I'm not sure how to resolve this issue or
how to file a patch (though I've applied patches before).
I had searched the bugzilla site here but could not find any other matches. I went to forums.gentoo.org and found one person with a similar issue to mine... but with a different error -- see bug 99559. I used some advise found in this forum posting to resolve my problem. Here's what I did: 1. Started emerge using 'emerge -v gnome-session' 2. Waiting until just prior to ./configure to be run and then hit CTRL+Z (to stop/pause the process. 3. Went and edited the configure file in /var/tmp/portage/gnome-session-2.10.0-r2/work/gnome-session-2.10.0-r2/ and commented out lines 20697 and 20698. 4. Typed 'fg' to continue the emerge. 5. Gnome-session is now emerged and installed! Thank you for reporting this issue. The information given on comment #2 was very helpful. However, this bug has already been reported, so please follow the discussion on bug #99580. *** This bug has been marked as a duplicate of 99580 *** |
