Configure Syntax Error Near Unexpected Token
Contents |
Support Search GitHub This repository Watch 36 Star 255 Fork 71 brianb/mdbtools Code Issues 28 Pull requests configure line syntax error near unexpected token 8 Projects 0 Pulse Graphs New issue ./configure: line 11613: syntax syntax error near unexpected token c error near unexpected token `GLIB,' ./configure: line 11613: `PKG_CHECK_MODULES(GLIB, glib-2.0, ,' #48 Closed leipzig opened this syntax error near unexpected token do Issue Mar 13, 2014 · 5 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 4 participants leipzig commented Mar 13, 2014
Syntax Error Near Unexpected Token Fi
centos6 checking whether /usr/bin/ld -m elf_x86_64 accepts --as-needed... yes ./configure: line 11613: syntax error near unexpected token `GLIB,' ./configure: line 11613: `PKG_CHECK_MODULES(GLIB, glib-2.0, ,' the offending lines: PKG_CHECK_MODULES(GLIB, glib-2.0, , as_fn_error $? " glib 2.0 is required by MDB Tools (runtime and devel). It can be downloaded at www.gtk.org. " "$LINENO" 5) amirkdv commented Mar syntax error near unexpected token else 24, 2014 Same issue here on Ubuntu 12:04 dpkg -l | grep glib # ii libglib2.0-0 2.32.1-0ubuntu2 GLib library of C routines git clone https://github.com/brianb/mdbtools cd mdbtools autoreconf -i -f ./configure # 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... no # checking for mawk... mawk # checking whether make sets $(MAKE)... yes # checking whether to enable maintainer-specific portions of Makefiles... yes # checking whether make supports nested variables... yes # 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
Support Search GitHub This repository Watch 14 Star 89 Fork 38 vcftools/vcftools Code Issues 15 Pull requests 4 Projects 0 Pulse Graphs New issue configure error #16 Closed Griffan opened this Issue Aug syntax error near unexpected token javascript 21, 2015 · 11 comments Projects None yet Labels None yet Milestone No milestone
Syntax Error Near Unexpected Token Then
Assignees No one assigned 8 participants Griffan commented Aug 21, 2015 ./configure: line 4634: syntax error near unexpected token `ZLIB,' auton1 commented
Bash Syntax Error Near Unexpected Token
Aug 21, 2015 Can you be a bit more detailed with regard to the issue? wookietreiber commented Aug 21, 2015 Did you generate this configure script? If so, which autoconf version do you have? Would https://github.com/brianb/mdbtools/issues/48 you please paste the failing version of the generated configure script to some pastebin, gist or other service? Griffan commented Aug 21, 2015 I use git clone to download code, then use the autogen.sh, then use configure --prefix=/my/install/dir. After a while, it stopped with this information prompted. autoconf (GNU Autoconf) 2.69 snap of the configure file: ... 4616 pmdir_relative_path=\
4617 $PERL -MConfig \
4618 -wle '($_ = $Config{installsitelib})
4619 =~ s!^\Q$Config{siteprefix}/!!; https://github.com/vcftools/vcftools/issues/16 \
4620 print' 4621 4622 4623 # Check whether --with-pmdir was given. 4624 if test "${with_pmdir+set}" = set; then : 4625 withval=$with_pmdir; PMDIR=${withval} 4626 else 4627 PMDIR='${prefix}'/"$pmdir_relative_path" 4628 fi 4629 4630 4631 4632 4633 # Checks for libraries. 4634 PKG_CHECK_MODULES(ZLIB, zlib) 4635 4636 # Checks for header files. 4637 4638 4639 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for grep that handles long lines and -e" >&5 4640 $as_echo_n "checking for grep that handles long lines and -e... " >&6; } 4641 if ${ac_cv_path_GREP+:} false; then : 4642 $as_echo_n "(cached) " >&6 4643 else ... wookietreiber commented Aug 22, 2015 Ok, I see where the problem is: The pkg-config check has not been translated from your configure.ac to configure, it has just been copied. I suppose that is because you either don't have pkg-config installed or it is installed incorrectly so that autoconf can not translate that line of the script. You need to correctly install pkg-config. The real problem here is, that the autoconf stage during ./autogen.sh does not complain that there is no pkg-config. It just copies PKG_CHECK_MODULES lines instead of translating them. Griffan commented Aug 24, 2015 problem solved! Thanks! Griffan closed this Aug 24, 2015 KhagayN commented Mar 30, 2016 i installed pkg-config use Homebrew but, the error still appears wo
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn http://stackoverflow.com/questions/16147491/configure-make-install-failed more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community https://lists.gnupg.org/pipermail/gnupg-devel/2015-February/029460.html Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ./configure && make install failed up vote 6 down vote syntax error favorite Good Morning While i'm installing RabbitMQ libraries, I found a problem: autoreconf -i && ./configure && make && sudo make install But ./configure stop at this position: checking for gcc option to accept ISO C99... -std=gnu99 ./configure: line 11104: syntax error near unexpected token `0.17' ./configure: line 11104: `PKG_PROG_PKG_CONFIG(0.17)' linux rabbitmq configure autotools pkg-config share|improve this question edited May 15 '14 at 13:01 umläute 10.9k2252 asked Apr syntax error near 22 '13 at 12:47 Osin Toumani 3491310 4 Bah, I totally disagree that this is off-topic... linux package configuration is extremely non-trivial and not at all a user-level exercise. This is precisely related to "software tools commonly used by programmers." –Bryce Schober Dec 3 '13 at 18:25 add a comment| 1 Answer 1 active oldest votes up vote 8 down vote your autotools project uses pkg-config, but it seems that you either don't have that installed at all or you are lacking the "pkg-config <-> autotools" glue (pkg.m4), which provides the PKG_PROG_PKG_CONFIG macro. if this is true, then the autoreconf -i should have complained when recreating configure (though probably only as a non-fatal warning) -> check your build-logs. you should be able to fix this by installing pkg-config NOTE: generally, if you get an error it's good to break down the problem into sub-problems. since you are really calling four different tasks (autoreconf, ./configure and make and sudo make install), you might want to execute them one by one and see where it actually fails (in your case: the 2nd tasks), and what the prior steps indicated (the autoreconf-call). share|improve this answer answered Apr 22 '13 at 14:14 umläute 10.9k2252 ad
9178: syntax error near unexpected token `LIBGNUTLS, ' Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] I'm getting this while building the latest GnuPG for Android using gnupg 2.1.1: checking for NTBTLS - version >= 0.1.0... no ./configure: line 9178: syntax error near unexpected token `LIBGNUTLS,' ./configure: line 9178: ` PKG_CHECK_MODULES(LIBGNUTLS, gnutls >= $NEED_GNUTLS_VERSION,' make: *** [gnupg/Makefile] Error 2 I'm not really sure the exact trigger for this, but on one Debian/stable machine, I get this problem reliably, while on another Debian/stable machine, I do not. But I think I can see the cause, at line 858 in configure.ac: if test x"$try_gnutls" = xyes ; then PKG_CHECK_MODULES([LIBGNUTLS], [gnutls >= $NEED_GNUTLS_VERSION], [have_gnutls=yes], [have_gnutls=no]) fi Which looks like this in ./configure: if test x"$try_gnutls" = xyes ; then PKG_CHECK_MODULES(LIBGNUTLS, gnutls >= $NEED_GNUTLS_VERSION, have_gnutls=yes, have_gnutls=no) fi Here, PKG_CHECK_MODULES() is being included as a sh function rather than an autoconf macro. As far as I know, it is not valid sh syntax to have a function call with parens spanning multiple lines. I attached the config.log and log of the build itself. The generic ./configure script is too big to attach for this list's strict, tiny 40kb limit, so it is here: https://gist.github.com/eighthave/4212cd6d369c92e4fa7b .hc -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9F0FE587374BBE81 -------------- next part -------------- A non-text attachment was scrubbed... Name: build.log.bz2 Type: application/x-bzip Size: 4857 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log.bz2 Type: application/x-bzip Size: 10151 bytes Desc: not available URL: Previous message: [PATCH] Add macro to test for pthreads. Next message: ./configure: line 9178: syntax error near unexpected token `LIBGNUTLS, ' Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the Gnupg-devel mailing list