Summary: | gnome-base/libbonobo-2.20.3 depends on byacc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aurélien Francillon <aurelien.francillon> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | gnome-base:libbonobo-2.20.3:20080229-130939.log |
Description
Aurélien Francillon
2008-02-29 07:08:44 UTC
do you have any implementation of yacc installed on your machine (yacc, bison, byacc ?). (In reply to comment #1) > do you have any implementation of yacc installed on your machine (yacc, bison, > byacc ?). > yes dev-util/yacc-1.9.1-r3 is present ... qlist dev-util/yacc /usr/bin/yacc /usr/share/doc/yacc-1.9.1-r3/NEW_FEATURES.gz /usr/share/doc/yacc-1.9.1-r3/README.gz /usr/share/doc/yacc-1.9.1-r3/ACKNOWLEDGEMENTS.gz /usr/share/doc/yacc-1.9.1-r3/README.Linux.gz /usr/share/doc/yacc-1.9.1-r3/00README-Legal-Rules-Regs.gz /usr/share/doc/yacc-1.9.1-r3/NO_WARRANTY.gz /usr/share/doc/yacc-1.9.1-r3/NOTES.gz /usr/share/man/man1/yacc.1.gz but looks like libbonobo wants byacc Could you attach the build.log ? Thanks Created attachment 144942 [details]
gnome-base:libbonobo-2.20.3:20080229-130939.log
strange line in logs:
checking for bison... byacc -d
checks byacc but no failure nor ok ...
the configure scripts related part :
for ac_prog in 'bison -y' byacc
do
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
{ echo "$as_me:$LINENO: checking for $ac_word" >&5
echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; }
if test "${ac_cv_prog_YACC+set}" = set; then
echo $ECHO_N "(cached) $ECHO_C" >&6
else
if test -n "$YACC"; then
ac_cv_prog_YACC="$YACC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
ac_cv_prog_YACC="$ac_prog"
echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
YACC=$ac_cv_prog_YACC
if test -n "$YACC"; then
{ echo "$as_me:$LINENO: result: $YACC" >&5
echo "${ECHO_T}$YACC" >&6; }
else
{ echo "$as_me:$LINENO: result: no" >&5
echo "${ECHO_T}no" >&6; }
fi
test -n "$YACC" && break
done
test -n "$YACC" || YACC="yacc"
well after some time lost on this i eventually found that i had YACC environement variable set to "byacc -d" which makes autoconf bypassing it's tests... I don't really know ho did i ended up with this variable set ... So i mark the bug as invalid but portage should probably warn about it, possibly in emerge --info ... thanks to Remi and Gilles and sorry for wasting your time ... Aurelien |