Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 376591 - app-shells/bash-4.2_p10 should depend on yacc
Summary: app-shells/bash-4.2_p10 should depend on yacc
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
: 376517 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-07-27 09:58 UTC by Bertrand Jacquin
Modified: 2011-08-11 02:23 UTC (History)
3 users (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 Bertrand Jacquin 2011-07-27 09:58:20 UTC
config.status: creating Makefile
config.status: creating builtins/Makefile
config.status: creating lib/readline/Makefile
config.status: creating lib/glob/Makefile
config.status: creating lib/intl/Makefile
config.status: creating lib/malloc/Makefile
config.status: creating lib/sh/Makefile
config.status: creating lib/termcap/Makefile
config.status: creating lib/tilde/Makefile
config.status: creating doc/Makefile
config.status: creating support/Makefile
config.status: creating po/Makefile.in
config.status: creating examples/loadables/Makefile
config.status: creating examples/loadables/perl/Makefile
config.status: creating config.h
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
config.status: executing default commands
make -j6 
yacc -d ./parse.y
make: yacc: Command not found
make: *** [y.tab.c] Error 127
emake failed
 * ERROR: app-shells/bash-4.2_p10 failed (compile phase):
 *   make failed

Reproducible: Always
Comment 1 Tomáš "tpruzina" Pružina (amd64 [ex]AT) 2011-07-27 11:25:54 UTC
I am pretty sure this is some kind of mistake, could you post emerge --info (or make.conf)?
This looks like you have some non standard "features" in make.conf, there is no word about yacc in portage ebuild. And it compiles fine here without it (amd64).
Comment 2 Bertrand Jacquin 2011-07-27 11:38:57 UTC
Here is it :

# emerge --info
Portage 2.1.10.7 (hardened/linux/amd64, gcc-4.5.2, glibc-2.13-r4, 3.0.0-gentoo x86_64)
=================================================================
System uname: Linux-3.0.0-gentoo-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q9650_@_3.00GHz-with-gentoo-2.0.3
Timestamp of tree: Tue, 26 Jul 2011 17:45:01 +0000
app-shells/bash:          4.2_p10
dev-lang/python:          2.7.2-r2, 3.2-r2
dev-util/cmake:           2.8.5
dev-util/pkgconfig:       0.26
sys-apps/baselayout:      2.0.3
sys-apps/openrc:          0.8.3-r1
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.11.1-r1
sys-devel/binutils:       2.21.1
sys-devel/gcc:            4.5.2
sys-devel/gcc-config:     1.4.1-r1
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r1
sys-kernel/linux-headers: 2.6.38 (virtual/os-headers)
sys-libs/glibc:           2.13-r4
Repositories: gentoo meleeweb
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=core2 -O2 -pipe -fomit-frame-pointer -mtune=core2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.3/ext-active/ /etc/php/cgi-php5.3/ext-active/ /etc/php/cli-php5.3/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=core2 -O2 -pipe -fomit-frame-pointer -mtune=core2"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests binpkg-logs buildsyspkg collision-protect distlocks ebuild-locks fixlafiles fixpackages news nodoc noinfo noman parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS=""
GENTOO_MIRRORS=" 	http://mirror.meleeweb.net/pub/linux/gentoo/ 	http://ftp.free.fr/mirrors/ftp.gentoo.org"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j6"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_EXTRA_OPTS="--checksum"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/opt/meleeweb/portage"
SYNC="rsync://rsync.melee/gentoo-portage"
USE="amd64 bash-completion bzip2 caps cli cracklib crypt cxx hardened iconv ipv6 justify mmx mmxext modules mudflap multilib ncurses nptl nptlonly openmp pam pcre readline session sse sse2 ssl sysfs urandom vim-syntax zlib" ALSA_CARDS="intel8x0 usb-audio" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" QEMU_SOFTMMU_TARGETS="i386 x86_64 arm m68k mips mipsel" QEMU_USER_TARGETS="i386 x86_64 arm armeb m68k mips mipsel" USERLAND="GNU" VIDEO_CARDS="dummy" 
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS
Comment 3 Tomáš "tpruzina" Pružina (amd64 [ex]AT) 2011-07-27 13:48:10 UTC
(In reply to comment #1)
> I am pretty sure this is some kind of mistake, could you post emerge --info (or
> make.conf)?
> This looks like you have some non standard "features" in make.conf, there is no
> word about yacc in portage ebuild. And it compiles fine here without it
> (amd64).

Hm, mea culpa, dunno, this may be related to hardened perhaps?
I thought that gentoo uses bison as replacement for yacc.
Comment 4 Tomáš "tpruzina" Pružina (amd64 [ex]AT) 2011-07-27 13:58:45 UTC
Sry for spam, but aren't you missing bison? (which is dependency of gcc and is in stage3 as far I know).
Comment 5 Bertrand Jacquin 2011-07-27 14:52:23 UTC
(In reply to comment #4)
> Sry for spam, but aren't you missing bison? (which is dependency of gcc and is
> in stage3 as far I know).

This is a fresh install with USE=hardened and adapted profile, neither yacc or bison was installed
Comment 6 Pacho Ramos gentoo-dev 2011-07-28 09:47:42 UTC
*** Bug 376517 has been marked as a duplicate of this bug. ***
Comment 7 Michael Palimaka (kensington) gentoo-dev 2011-07-28 11:42:07 UTC
(In reply to comment #4)
> Sry for spam, but aren't you missing bison? (which is dependency of gcc and is
> in stage3 as far I know).
bison is only a build-time dependency of gcc. emerging gcc and then removing bison is indeed a valid configuration.

(In reply to comment #6)
> *** Bug 376517 has been marked as a duplicate of this bug. ***
For the record that bug was filed before this one. :)
Comment 8 meyerm 2011-08-10 23:46:19 UTC
This just happened to me with a default amd64-profile. No hardened. Freshly unpacked stage3 and portage-snapshot (and synced before updating of course).
Comment 9 meyerm 2011-08-10 23:58:03 UTC
Just encountered a very strange behavior. To fulfill the dependency on this minimal system I simply emerged yacc and let portage updating the system. Afterwards bash was no longer able to parse bash scripts. This means of course no more portage or anything was working. After replacing yacc with the bison package and recompiling bash with that (I replaced temporarily the bash executable with a working copy of another system) the system continued to work.