[lfs-support] Step 5.11 Tcl-8.6.1 (7.5 stable) building errors

Ken Moffat zarniwhoop at ntlworld.com
Mon May 19 10:06:04 PDT 2014


On Mon, May 19, 2014 at 05:33:28AM -0400, Marcos Menendez wrote:
> Hello,
> 
> I'm trying to install LFS based on 7.5 stable on a CentOS 6.5 x86_64.
> 
> 
> Actually I'm facing problems in step 5.11 Tcl-8.6.1
> 
> My question is if I have to unset the variables used from the previous step for GCC-4.8.2 pass 2 before building tcl.
> It is not clear to me, as per the book, if I have to unset them or not:
> 
> CC=$LFS_TGT-gcc
> AR=$LFS_TGT-ar
> RANLIB=$LFS_TGT-ranlib
> CXX=$LFS_TGT-g++
> 
> 
> If I keep using them I have the following errors under config.log:
> 
[snip]

 You should not have set them in the previous step (i.e. they should
not be part of the lfs user's environment).  If you look at the gcc
instructions, each of these assignments is on a line with '\' as its
last character (i.e. '\' is a continuation) before gcc's configure
script is invoked.

 So, the book sets these only during that run of the configure
script.

 I doubt that setting them in the lfs user's environment did
anything wrong during the build of gcc, so if you unset them now you
are probably ok to go.  Except -
> 
> If I unset them and build, I have errors again:
> 
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> conftest.c:2:3: error: unknown type name 'choke'
> conftest.c:2:3: error: expected '=', ',', ';', 'asm' or '__attribute__' at end of input
> conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory
> conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory
> collect2: error: ld returned 1 exit status
> | /* Override any gcc2 internal prototype to avoid an error. */
> collect2: error: ld returned 1 exit status
> conftest.c:62:23: fatal error: net/errno.h: No such file or directory
> conftest.c:28:23: fatal error: net/errno.h: No such file or directory
> conftest.c:62:18: fatal error: zlib.h: No such file or directory
> conftest.c:28:18: fatal error: zlib.h: No such file or directory
> configure:6515: gcc -c -pipe -fvisibility=hidden -Werror conftest.c >&5
> conftest.c:40:15: error: storage size of 'buf' isn't known
> conftest.c:41:19: error: 'open64' undeclared (first use in this function)
> conftest.c:42:19: error: 'open64' undeclared (first use in this function)
> conftest.c:41:1: error: unknown type name '__int64'
> conftest.c:41:18: error: '__int64' undeclared (first use in this function)
> conftest.c:41:27: error: expected ',' or ';' before numeric constant
> conftest.c:42:21: error: duplicate case value
> conftest.c:42:13: error: previously used here
> conftest.c:45:2: error: unknown type name 'not'
> conftest.c:45:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'endian'
> configure:10518: checking for strerror
> configure:11035: checking for gai_strerror
> conftest.c:77:11: error: too few arguments to function 'gethostbyaddr_r'
> conftest.c:99:23: fatal error: sys/modem.h: No such file or directory
> conftest.c:65:23: fatal error: sys/modem.h: No such file or directory
> conftest.c:74:17: error: 'struct tm' has no member named 'tm_tzadj'
> conftest.c:108:1: error: unknown type name 'choke'
> conftest.c:116:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int'
> | /* Override any gcc2 internal prototype to avoid an error. */
> conftest.c:116:23: fatal error: sys/filio.h: No such file or directory
> conftest.c:82:23: fatal error: sys/filio.h: No such file or directory
> ac_cv_func_gai_strerror=yes
> ac_cv_func_strerror=yes
> 
> 
> The 'make' itself doesn't show any of these errors at the end but only when I search on the config.log file.
> 

 If (with the variables unset) configure ran successfully (i.e. it
created the Makefile), and make also ran successfully (no errors
reported, or alternatively status 0 when make completes [ echo $? or
perhaps 'make || echo "failed" ' ] then you do not have a problem.

 I think you don't fully appreciate what configure scripts do.  Each
one is different in detail, but they are all concerned with creating
Makefiles which will run in the current environment.  They test for
a lot of things which identify specific operating systems or which
show that a particular package is available.  If sys/filio.h
existed, it would need to be included to make certain things
available.  And you would probably be running on a BSD system, or
one with BSD ancestry such as OSX (or Solaris - I'm not sure how
much BSD is in that, but this file definitely gets mentioned).

 So, don't go looking for errors in config.log unless configure
fails to work.

ĸen
-- 
das eine Mal als Tragödie, dieses Mal als Farce



More information about the lfs-support mailing list