Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
While doing "emerge -e system" in an amd64 stage2 chroot jail. This might have something to do with my et_EE locale. >>> Unpacking bc-1.06.tar.gz to /var/tmp/portage/bc-1.06-r6/work * Applying bc-1.06-info-fix.diff ... [ ok ] * Applying bc-1.06-readline42.diff ... [ ok ] * Applying bc-1.06-longopts.patch ... [ ok ] * Applying bc-1.06-static-save.patch ... [ ok ] /usr/portage/sys-devel/bc/bc-1.06-r6.ebuild: line 35: flex: command not found /usr/portage/sys-devel/bc/bc-1.06-r6.ebuild: line 36: flex: command not found /usr/portage/sys-devel/bc/bc-1.06-r6.ebuild: line 37: flex: command not found /usr/portage/sys-devel/bc/bc-1.06-r6.ebuild: line 38: [: : integer expression expected >>> Source unpacked. ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu --with-readline creating cache ./config.cache checking for a BSD compatible install... /bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal... found checking for working autoconf... missing checking for working automake... found checking for working autoheader... missing checking for working makeinfo... found checking for gcc... x86_64-pc-linux-gnu-gcc checking whether the C compiler (x86_64-pc-linux-gnu-gcc -O0 -pipe ) works... yes checking whether the C compiler (x86_64-pc-linux-gnu-gcc -O0 -pipe ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E checking for minix/config.h... no checking for flex... no checking for lex... no ./configure: line 1186: flex: command not found checking for flex... lex checking for yywrap in -ll... no checking lex output file root... ./configure: line 1274: lex: command not found configure: error: cannot find output from lex; giving up
Created an attachment (id=78794) [edit] config.log
Yes, this again seems to be a locale issue. "flex" is not in $PATH. Its binary is in "/--prefix/usr/bin/" in the chroot. Even re-emerging flex (2.5.4a-r6) installs them there. Some non-flex files also exist there. I will try to figure out, where those came from.
I'd strongly suggest that you should stop using this weird locale for compiling of whatever stuff.
> I'd strongly suggest that you should stop using this weird locale for compiling > of whatever stuff. if you dont have anything useful to contribute, dont bother J: could you try the masked version of flex please (2.5.31) ?
(In reply to comment #4) > J: could you try the masked version of flex please (2.5.31) ? > Emerged without trouble and installed itself properly, not using "--prefix" as a prefix. :)
added patch to flex-2.5.4a-r6 and unmasked 2.5.31 thanks for the bug report
