LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)
-   -   BFLS config error with libxcb (https://www.linuxquestions.org/questions/linux-from-scratch-13/bfls-config-error-with-libxcb-4175499878/)

NumenX 03-29-2014 07:41 AM

BFLS config error with libxcb
 
I've succesfully built LFS 7.4 twice, and LFS 7.5 Systemd. With the 7.5 Systemd edition I decided to go take it to the next level and attempt BLFS :-) All the issues I encoutered during all builds up until now, I managed to solve on my own by doeing a LOT of browsing and reading, but with the libxcb package I'm kinda lost. When I run the config it gives me the following:
Quote:

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: copying file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
autoreconf: Leaving directory `.'
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: \

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for \-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for a Python interpreter with version >= 2.6... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for \-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for CHECK... yes
checking build system type... Invalid configuration `\': machine `\' not recognized
configure: error: /bin/sh build-aux/config.sub \ failed

I've already checked the info pages and the bug page of libxcb but I couldn't find nothing relevant to this error.
And right now, to be honest, my mind is fuzzing a bit, and I feel a little lost :-)

NumenX 03-29-2014 09:26 AM

OK, found it...really dumb and stupid but I'll share it anyway....
When I started building the X-bunch, for some reason the XORG_PREFIX didn't last (maybe it's supposed to, I don't know...), so at that time I figured that to make life easier on myself, I renamed bash files to file.bak, and copy-pasted the setup for the X variables to my /etc/profile so that way they would be set upon login....unfortunatly, I didn't remove the "\" character from the paste....hence the error.
I do wonder why this is the first time this error came up..


All times are GMT -5. The time now is 05:07 PM.