Configure Syntax Error Near Unexpected Token Pkg_check_modules
After installing it configure runs without any errors. You signed in with another tab or window. Make sure it is *** in your path, or set the PKG_CONFIG environment variable *** to the full path to pkg-config.]) ]) share|improve this answer answered Apr 9 '14 at 21:14 share|improve this answer answered Feb 2 at 21:04 Sean Martin 111 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign Source
yes # checking for fcntl.h... The confgure.ac file looks like: AC_PREREQ(2.61) AC_INIT(autoconf_test, 1.0, [email protected]) PKG_CHECK_MODULES(libusbmuxd, libusbmuxd >= 0.1.4) I can then execute autoconf from the command line and it does produce a configure script. I find my pkg.m4 here /usr/share/aclocal. I have a crude workaround for the time being. https://github.com/brianb/mdbtools/issues/48
Configure Line Syntax Error Near Unexpected Token
This is true for me. printf %s\n # checking for archiver @FILE support... @ # checking for strip... Clair added a comment - 25/Aug/14 18:04 port Hide Permalink Timothy St.
yes # checking whether -lc should be explicitly linked in... Skip to content Ignore Learn more Please note that GitHub no longer supports old versions of Firefox. Terms Privacy Security Status Help You can't perform that action at this time. Pkg_prog_pkg_config Syntax Error yes # checking for iconv declaration... # extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); # checking whether the target supports symbol aliases...
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 Pkg_check_modules Example Missing .pc files?2pkg-config: PKG_PROG_PKG_CONFIG: command not found5Adding /usr/local/bin (homebrew) to QtCreator search path for pkg-config on Mac OSX2Query pkg-config variable through autotools4Installing pkg-config files to proper path on CentOS with automake0Package 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. https://github.com/vcftools/vcftools/issues/16 no # checking for a readline compatible library... # configure: error: conditional "ENABLE_SK" was never defined. # Usually this means the macro was only invoked conditionally.
The real problem here is, that the autoconf stage during ./autogen.sh does not complain that there is no pkg-config. Install Pkg-config o # checking whether we are using the GNU C compiler... cfblaeb commented May 27, 2016 Exact same error. You signed out in another tab or window.
- func_convert_file_noop # checking for /usr/bin/ld option to reload object files... -r # checking for objdump...
- Thanks! –prameshvari Nov 21 '14 at 12:14 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign
- x86_64-unknown-linux-gnu # checking host system type...
- Name: config.log.bz2 Type: application/x-bzip Size: 10151 bytes Desc: not available URL: Previous message: [PATCH] Add macro to test for pthreads.
- Anyone knows the font style here?
- yes # checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B # checking the name lister (/usr/bin/nm -B) interface...
- Anyway, the error message I quoted shows that there is an "unexpected token before LOG4CPLUS." Looking at the macro usage "LOG4CPLUS" is shown before "log4cplus".
- Skip to content Ignore Learn more Please note that GitHub no longer supports old versions of Firefox.
- insom commented Mar 31, 2016 Hi @roottox / @justincm, I had this but it was because I was missing pkg-config - can you check if you have all the deps installed?
There is NO WARRANTY, to the extent permitted by law. http://stackoverflow.com/questions/8578181/using-the-pkg-config-macro-pkg-check-modules-failing xor-gate closed this May 3, 2016 sguillia commented Jul 13, 2016 Hello, I've still got the same problem. Configure Line Syntax Error Near Unexpected Token yes # checking fcntl.h presence... Pkg_check_modules Not Found Let's draw some Atari ST bombs!
does anyone have any idea what's going on here? this contact form Reload to refresh your session. You need to correctly install pkg-config. no # checking how to associate runtime and link libraries... Syntax Error Near Unexpected Token `lasso,'
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. Can you find this file somewhere in /usr/share/aclocal or a similar directory? –ptomato Dec 20 '11 at 21:48 3 Use 'aclocal --print' to determine the directory in which to look yes # checking limits.h presence... http://iembra.org/syntax-error/configure-line-syntax-error-near-unexpected-token.php Next message: ./configure: line 9178: syntax error near unexpected token `LIBGNUTLS, ' Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the
I have a very simple configure.ac file which I am using to just learn how autoconf & pkg-config work together. Pkg_check_modules Cmake Also, it appears that Jie and I have automake 1.14-1. Terms Privacy Security Status Help You can't perform that action at this time.
Or is it still an issue?
Once he commits those we can resolve this. Hide Permalink Benjamin Hindman added a comment - 25/Aug/14 17:21 Timothy St. Clair added a comment - 27/Aug/14 18:13 Benjamin Hindman Were you able to resolve? Syntax Error Near Unexpected Token Glib none needed # checking for style of include used by make...
I am asking because autoconf-2.61 does not work with PKG_CHECK_MODULES. Syntax error near unexpected token1syntax error near unexpected token `if'0Why am I getting a syntax near unexpected token newline error?1Why: syntax error near unexpected token `fi'1Bash : Syntax Error Near Unexpected Reload to refresh your session. Check This Out gcc # checking whether the C compiler works...
yes # checking for unistd.h... (cached) yes # checking wordexp.h usability...