Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 1029 by [email protected]: ENV variable should not be used in Makefile http://code.google.com/p/ibus/issues/detail?id=1029 What version of the product are you using? On what operating system? OS (Linux distributions, UNIX or ...): NetBSD-5.0.2 Architecture (i386, x86_64): i386 IBus version: 1.3.7 Input method name and version: ibus-anthy-1.2.1, ibus-pinyin 1.3.10,...? Python version: 2.6.5 dbus version: 1.2.4.6 dbus-python version: 0.83.1 gtk version (if bug is about gtk applications): qt version (if bug is about qt applications): What steps will reproduce the problem? 1. env command is detected in configure script and set to ENV in Makefile. 2. posix shell will be do contents of file pointed by $ENV at startup. 3. if ENV environment variable is exported before do 'make', ALL invoke of shell will be failed, because $ENV point to binary file. What is the expected output? What do you see instead? Default .profile on NetBSD-5.0.2 contains following: export ENV=$HOME/.shrc If a user's login shell is /bin/sh, or /bin/ksh, he will fail to build ibus. variable name `ENV' should not be used, use ENV_PROG, SETENV, or something instead. Please provide any additional information below. I've conform that ENV is used in current release of ibus, ibus-anthy and ibus-pinyin, other ibus engines may be using it. -- You received this message because you are subscribed to the Google Groups "ibus-devel" group. iBus project web page: http://code.google.com/p/ibus/ iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
