| View previous topic :: View next topic |
| Author |
Message |
Carlos
Guru
Joined: 07 Aug 2002
Posts: 458
Location: Providence, RI
|
 Posted: Thu Mar 27, 2003 3:45 am Post subject: ./configure run twice by vim ebuild |
 |
|
EDIT: changed title from ' "nls" in USE but vim compiled without multibyte '
The topic pretty much says it all; "nls" is in USE but for some reason when I emerge vim "--enable-multibyte" is set to 'no'. Curiously enough, looking at the output from emerge, it seems like configure is being run twice; the first time through it looks correct, but the second time it seems like the USE vars aren't getting used.
| Code: | >>> Source unpacked.
X
creating cache auto/config.cache
checking whether make sets ${MAKE}... yes
*snip*
checking --enable-multibyte argument... yes
*snip*
updating cache auto/config.cache
creating auto/config.status
creating auto/config.mk
creating auto/config.h
Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src && make first
make[1]: Entering directory `/var/tmp/portage/vim-6.1-r21/work/vim61/src'
if test ! -f configure.save; then mv configure configure.save; fi
autoconf
sed -e 's+\./config.log+auto/config.log+' configure > auto/configure
chmod 755 auto/configure
mv -f configure.save configure
rm -f auto/config.status auto/config.cache
GUI_INC_LOC="" GUI_LIB_LOC="" \
CC="gcc" CPPFLAGS="" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
\
LDFLAGS="-rdynamic -L/usr/local/lib" srcdir="." \
./configure \
\
\
\
\
\
\
creating cache auto/config.cache
checking whether make sets ${MAKE}... yes
*snip: here, it's disabled*
checking --enable-multibyte argument... no
*snip - but note below that GTK and Motif are being checked even though the vanilla vim ebuild isn't supposed to*
checking whether or not to look for GTK... yes
checking whether or not to look for GNOME... no
checking whether or not to look for Motif... yes
checking whether or not to look for Athena... yes
*snip, again*
updating cache auto/config.cache
creating auto/config.status
creating auto/config.mk
creating auto/config.h
make[1]: Leaving directory `/var/tmp/portage/vim-6.1-r21/work/vim61/src'
make[1]: Entering directory `/var/tmp/portage/vim-6.1-r21/work/vim61/src'
mkdir objects |
This happened first with vim-6.1-r21, but now it happens when I emerge older versions too. I've taken a look at vim.eclass and some other files but I haven't dealt with ebuilds much so I really don't have an idea why this is happening.
_________________
Man must shape his tools lest they shape him. |
|
| Back to top |
|
 |
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Sat Mar 29, 2003 1:48 pm Post subject: |
|
|
I reported a (I think) related bug here.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
