I am having problems compiling output from Glade (using the default settings, except for unselecting gettext support). Running autogen.sh provides the output below. Here are the two final lines, and the suspected errors. Commenting out these lines don't help (obviously). ./configure: line 3988: syntax error near unexpected token `PACKAGE,' ./configure: line 3988: `PKG_CHECK_MODULES(PACKAGE, $pkg_modules)' I am running SuSE 8.2 with latest installs. Any suggestions? Here's the output jason@bambam:~/Projects/cerealblog> autogen.sh **Warning**: I am going to run `configure' with no arguments. If you wish to pass any to it, please specify them on the `./autogen.sh' command line. processing . Running aclocal ... Running autoheader... WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot' WARNING: and `config.h.top', to define templates for `config.h.in' WARNING: is deprecated and discouraged. WARNING: Using the third argument of `AC_DEFINE' and WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without WARNING: `acconfig.h': WARNING: AC_DEFINE([NEED_MAIN], 1, WARNING: [Define if a function `main' is needed.]) WARNING: More sophisticated templates can also be produced, see the WARNING: documentation. Running automake --gnu ... configure.in: installing `./install-sh' configure.in: installing `./mkinstalldirs' configure.in: installing `./missing' Makefile.am: installing `./COPYING' Makefile.am: installing `./INSTALL' src/Makefile.am: installing `./depcomp' Running autoconf ... Running ./configure --enable-maintainer-mode ... checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... 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 ANSI C... none needed checking dependency style of gcc... gcc3 checking for strerror in -lcposix... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes ./configure: line 3988: syntax error near unexpected token `PACKAGE,' ./configure: line 3988: `PKG_CHECK_MODULES(PACKAGE, $pkg_modules)' -- Jason Lotito - www.phpcomplete.com
Jason Lotito
checking for ANSI C header files... yes ./configure: line 3988: syntax error near unexpected token `PACKAGE,' ./configure: line 3988: `PKG_CHECK_MODULES(PACKAGE, $pkg_modules)'
There either seems to be a bug in glade's configure.in or some construct doesn't work anymore with current automake. The PKG_CHECK_MODULES call should have been turned into shell script code by autoconf. For any further help I definitely need info you should have provided (at least in part) in the first place: - version of SuSE Linux you're trying to get this to work - version of GLADE - tarball or .src.rpm and from where you fetched it. - for problems with autoconf the relevant part of config.log. How else is anybody here supposed to check for themselves, given that working crystal balls are a very rare thing? Philipp -- Philipp Thomas work: pthomas@suse.de Development, SuSE Linux AG private: philipp.thomas@t-link.de
On Monday 02 June 2003 5:30 pm, Philipp Thomas wrote:
Jason Lotito
[Mon, 02 Jun 2003 00:41:47 -0400]: checking for ANSI C header files... yes ./configure: line 3988: syntax error near unexpected token `PACKAGE,' ./configure: line 3988: `PKG_CHECK_MODULES(PACKAGE, $pkg_modules)'
For any further help I definitely need info you should have provided (at least in part) in the first place:
- version of SuSE Linux you're trying to get this to work - version of GLADE - tarball or .src.rpm and from where you fetched it.
As I mentioned in my previous email, SuSE 8.2 with the latest installs. Glade 2.0 from the glade website, the default install. Thought I was clear enough about this, "in the first place."
- for problems with autoconf the relevant part of config.log.
Not sure which part is relevant, or else I could probably solve the problem
myself. But since you asked for it...
-- START FILE --
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.57. Invocation command line was
$ ./configure --enable-maintainer-mode
## --------- ##
## Platform. ##
## --------- ##
hostname = bambam
uname -m = i686
uname -r = 2.4.20-4GB-athlon
uname -s = Linux
uname -v = #1 Mon Mar 17 17:56:47 UTC 2003
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = i686
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /usr/X11R6/bin
PATH: /bin
PATH: /usr/games
PATH: /opt/gnome2/bin
PATH: /opt/gnome/bin
PATH: /opt/kde3/bin
PATH: /usr/lib/java/bin
PATH: /opt/gnome/bin
PATH: .
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1268: checking for a BSD-compatible install
configure:1322: result: /usr/bin/install -c
configure:1333: checking whether build environment is sane
configure:1376: result: yes
configure:1409: checking for gawk
configure:1425: found /usr/bin/gawk
configure:1435: result: gawk
configure:1445: checking whether make sets $(MAKE)
configure:1465: result: yes
configure:1622: checking whether to enable maintainer-specific portions of
Makefiles
configure:1631: result: yes
configure:1667: checking for style of include used by make
configure:1695: result: GNU
configure:1766: checking for gcc
configure:1782: found /usr/bin/gcc
configure:1792: result: gcc
configure:2036: checking for C compiler version
configure:2039: gcc --version &5
gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:2042: $? = 0
configure:2044: gcc -v &5
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib
--enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj
--with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux
Thread model: posix
gcc version 3.3 20030226 (prerelease) (SuSE Linux)
configure:2047: $? = 0
configure:2049: gcc -V &5
gcc: `-V' option must have argument
configure:2052: $? = 1
configure:2076: checking for C compiler default output
configure:2079: gcc conftest.c >&5
configure:2082: $? = 0
configure:2128: result: a.out
configure:2133: checking whether the C compiler works
configure:2139: ./a.out
configure:2142: $? = 0
configure:2159: result: yes
configure:2166: checking whether we are cross compiling
configure:2168: result: no
configure:2171: checking for suffix of executables
configure:2173: gcc -o conftest conftest.c >&5
configure:2176: $? = 0
configure:2201: result:
configure:2207: checking for suffix of object files
configure:2229: gcc -c conftest.c >&5
configure:2232: $? = 0
configure:2254: result: o
configure:2258: checking whether we are using the GNU C compiler
configure:2283: gcc -c conftest.c >&5
configure:2286: $? = 0
configure:2289: test -s conftest.o
configure:2292: $? = 0
configure:2305: result: yes
configure:2311: checking whether gcc accepts -g
configure:2333: gcc -c -g conftest.c >&5
configure:2336: $? = 0
configure:2339: test -s conftest.o
configure:2342: $? = 0
configure:2353: result: yes
configure:2370: checking for gcc option to accept ANSI C
configure:2431: gcc -c -g -O2 conftest.c >&5
configure:2434: $? = 0
configure:2437: test -s conftest.o
configure:2440: $? = 0
configure:2458: result: none needed
configure:2476: gcc -c -g -O2 conftest.c >&5
conftest.c:2: error: parse error before "me"
configure:2479: $? = 1
configure: failed program was:
| #ifndef __cplusplus
| choke me
| #endif
configure:2590: checking dependency style of gcc
configure:2652: result: gcc3
configure:2671: checking for strerror in -lcposix
configure:2702: gcc -o conftest -g -O2 conftest.c -lcposix >&5
/usr/lib/gcc-lib/i486-suse-linux/3.3/../../../../i486-suse-linux/bin/ld:
cannot find -lcposix
collect2: ld returned 1 exit status
configure:2705: $? = 1
configure: failed program was:
| #line 2678 "configure"
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "cerealblog"
| #define VERSION "0.1"
| /* end confdefs.h. */
|
| /* Override any gcc2 internal prototype to avoid an error. */
| #ifdef __cplusplus
| extern "C"
| #endif
| /* We use char because int might match the return type of a gcc2
| builtin and then its argument prototype would still apply. */
| char strerror ();
| int
| main ()
| {
| strerror ();
| ;
| return 0;
| }
configure:2723: result: no
configure:2777: checking for gcc
configure:2803: result: gcc
configure:3047: checking for C compiler version
configure:3050: gcc --version &5
gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3053: $? = 0
configure:3055: gcc -v &5
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib
--enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj
--with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux
Thread model: posix
gcc version 3.3 20030226 (prerelease) (SuSE Linux)
configure:3058: $? = 0
configure:3060: gcc -V &5
gcc: `-V' option must have argument
configure:3063: $? = 1
configure:3066: checking whether we are using the GNU C compiler
configure:3113: result: yes
configure:3119: checking whether gcc accepts -g
configure:3161: result: yes
configure:3178: checking for gcc option to accept ANSI C
configure:3266: result: none needed
configure:3284: gcc -c -g -O2 conftest.c >&5
conftest.c:2: error: parse error before "me"
configure:3287: $? = 1
configure: failed program was:
| #ifndef __cplusplus
| choke me
| #endif
configure:3398: checking dependency style of gcc
configure:3460: result: gcc3
configure:3480: checking for gcc option to accept ANSI C
configure:3544: gcc -c -g -O2 conftest.c >&5
configure:3547: $? = 0
configure:3550: test -s conftest.o
configure:3553: $? = 0
configure:3568: result: none needed
configure:3584: checking how to run the C preprocessor
configure:3620: gcc -E conftest.c
configure:3626: $? = 0
configure:3658: gcc -E conftest.c
configure:3659:28: ac_nonexistent.h: No such file or directory
configure:3664: $? = 1
configure: failed program was:
| #line 3649 "configure"
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "cerealblog"
| #define VERSION "0.1"
| /* end confdefs.h. */
| #include
How else is anybody here supposed to check for themselves, given that working crystal balls are a very rare thing?
They could start by reading the original email. Then they could then ask for what information wasn't provided, minus the sarcasm. Jason
Please, I *do* read the list, so sending me an additional copy of the mail via private mail is unnecessary. * Jason Lotito (jason@devnetwork.net) [20030603 05:23]:
As I mentioned in my previous email, SuSE 8.2 with the latest installs.
That part I missed, sorry.
Glade 2.0 from the glade website, the default install. Thought I was clear enough about this, "in the first place."
Glade 2.0 wasn't mentioned anywhere, and not everyone knows the glade URL
- for problems with autoconf the relevant part of config.log.
Not sure which part is relevant,
In this particular case it's not relevant, I should have made that more clear.
They could start by reading the original email.
Yes, I already wrote above that I didn't catch the SuSE 8.2 part.
Then they could then ask for what information wasn't provided, minus the sarcasm.
I normally read the list in my free time and like to help where I can, but
I do *not* like to query information that could have been provided in the
first place (like GLADE 2.0 and the URL) as this needs an extra mail.
If you'd have to do that information hunting as part of your job like I do,
I'm sure you'd also appreciate more precise reports :)
All that apart, I'll have a look at the glade 2.0 package when time
permits.
Philipp
--
Philipp Thomas
* Philipp Thomas (pthomas@suse.de) [20030603 13:52]:
All that apart, I'll have a look at the glade 2.0 package when time permits.
OK, I just checked and everything built OK. Note that I didn't call autogen
but just issued an 'autoconf --force --install' in the top source directory.
Philipp
--
Philipp Thomas
On Tuesday 03 June 2003 1:25 pm, Philipp Thomas wrote:
* Philipp Thomas (pthomas@suse.de) [20030603 13:52]:
All that apart, I'll have a look at the glade 2.0 package when time permits.
OK, I just checked and everything built OK. Note that I didn't call autogen but just issued an 'autoconf --force --install' in the top source directory.
Okay, doing a bit more research, I came upon this: http://lists.copyleft.no/pipermail/conglomerate-devel/2002-September/000114.... Basically, I was having the same problem: -- EMAIL --
Below are the results of the tests you tried, and the result of running the autogen script. It appears to not find the definition of the PKG_CHECK_MODULES macro.
As far as I can make out, PKG_CHECK_MODULES is defined in pkg.m4, which has been installed from the pkg-config module (of GARNOME) into /home/david/garnome/share/aclocal
"Try running "aclocal -I /home/david/garnome/share/aclocal" in the Conglomerate top dir. Failing that, copy or move the macros to /usr/share/aclocal. Aclocal can be a bit stupid sometimes - by default, it looks only in the directory in which it was installed, and if you specify more paths, you need to make sure you don't have the same macro in several of the paths it's searching, or it will report a duplicate macro and terminate (do nothing). When aclocal seems to be happy, try the autogen again. The point of this exercise is to get the missing macro into the generated "$(topdir)/aclocal.m4", so the other tools can find it." -- END EMAIL -- Basically, I just ran: jason@bambam:~/Projects/cerealblog> autogen.sh jason@bambam:~/Projects/cerealblog> aclocal -I /usr/local/share/aclocal/ jason@bambam:~/Projects/cerealblog> autoconf jason@bambam:~/Projects/cerealblog> ./configure And everything worked. Thanks to Philipp for trying to help, it's much appreciated. -- Jason Lotito - www.phpcomplete.com
Jason Lotito
Okay, doing a bit more research, I came upon this: http://lists.copyleft.no/pipermail/conglomerate-devel/2002-September/000114....
Basically, I was having the same problem:
Basically, I just ran:
jason@bambam:~/Projects/cerealblog> autogen.sh
You don't need autogen, it's that simple. As I wrote, a simple call to autoreconf did the trick. autogen.sh basically does the same as autoreconf and autoreconf is better at it.
jason@bambam:~/Projects/cerealblog> aclocal -I /usr/local/share/aclocal/
*If* your gnome2 macros actually are there, it's OK. Note that if you have installed gnome2 from our distribution, all necessary macros can be found in /opt/gnome2/share/aclocal/gnome2-macros Philipp
participants (3)
-
Jason Lotito
-
Philipp Thomas
-
Philipp Thomas