syntax error near unexpected token `PKG_CHECK_MODULES(GTK,
Howdy, I ocassionally try out classpath's configury mechanism, and it always breaks down on me, so I must be doing something really 'special' to it. Since I'm only interested in building the java part of classpath, and not the associated native parts, I was wondering how to configure it to do that. I've tried ../classpath/configure --with-jikes --disable-gtk-peer --disable-jni but that tried to execute that PKG_CHECK_MODULES thing, whatever it is. It's not part of autotools, so autoreconf did not put it in there :( Is there a way to do what I'd like to do, or do I have to write my own build-script [1]? Or could we just include the m4 code classpath depends on in the tree, given that these files are not generated? They apparently need to be dug out from the web somewhere, where search engines do not dare to go :) cheers, dalibor topic [1] build.xml would seem like the obvious choice for PKG_CHECK_MODULES challenged users like me :) ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: syntax error near unexpected token `PKG_CHECK_MODULES(GTK,
Dalibor Topic wrote: Howdy, I ocassionally try out classpath's configury mechanism, and it always breaks down on me, so I must be doing something really 'special' to it. I've tried the autogen.sh script too, preparing to reach for the brown paper bag ... but nope, that still breaks in the same way. Something tells me that the PKG_* stuff is in pkg.m4, but for some reason it does not get picked up aut either autoreconf, nor autogen.sh cheers, dalibor topic ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: syntax error near unexpected token `PKG_CHECK_MODULES(GTK,
Dalibor Topic wrote:
Dalibor Topic wrote:
Howdy,
I ocassionally try out classpath's configury mechanism, and it always
breaks down on me, so I must be doing something really 'special' to it.
I've tried the autogen.sh script too, preparing to reach for the brown
paper bag ...
but nope, that still breaks in the same way.
Something tells me that the PKG_* stuff is in pkg.m4, but for some
reason it does not get picked up aut either autoreconf, nor autogen.sh
The reason is that they are not being told where to look for the
thrid-party m4 files. No idea if that's something particular to my setup
(am 1.8.3, ac 2.59, libtool 1.5.6), but an
${ACLOCAL} -I .
in autogen.sh fixes it, as far as I can tell.
Adding a AC_CONFIG_MACRO_DIR([.]) in configure.ac doesn't seem to work
though. I haven't tried moving the m4 files into their own subdirectory,
though.
cheers,
dalibor topic
___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
Re: syntax error near unexpected token `PKG_CHECK_MODULES(GTK,
On Mon, 2004-04-19 at 06:26, Dalibor Topic wrote:
Dalibor Topic wrote:
Dalibor Topic wrote:
Howdy,
I ocassionally try out classpath's configury mechanism, and it always
breaks down on me, so I must be doing something really 'special' to it.
I've tried the autogen.sh script too, preparing to reach for the brown
paper bag ...
but nope, that still breaks in the same way.
Something tells me that the PKG_* stuff is in pkg.m4, but for some
reason it does not get picked up aut either autoreconf, nor autogen.sh
The reason is that they are not being told where to look for the
thrid-party m4 files. No idea if that's something particular to my setup
(am 1.8.3, ac 2.59, libtool 1.5.6), but an
${ACLOCAL} -I .
in autogen.sh fixes it, as far as I can tell.
Adding a AC_CONFIG_MACRO_DIR([.]) in configure.ac doesn't seem to work
though. I haven't tried moving the m4 files into their own subdirectory,
though.
cheers,
dalibor topic
For some reason, yet unknown, Michael put this macro in pkg.m4 instead
of adding it to acinclude.m4 which is where all our local macros go.
Why it would be there, and augogen.sh would not have the appropriate
arguments to pick it up, is beyond me. It isn't a standard file name, I
checked the 1.7.8 autoconf manual. It needs to be moved to
acinclude.m4.
As to the configure options you need, it's supposed to be just
--disable-jni for what you want. However, the link between this option
and the gtk-peer option may be broken, you may need to specify both.
Brian
signature.asc
Description: This is a digitally signed message part
___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
Re: syntax error near unexpected token `PKG_CHECK_MODULES(GTK,
Am Montag, 19. April 2004 14:24 schrieb C. Brian Jones:
On Mon, 2004-04-19 at 06:26, Dalibor Topic wrote:
Dalibor Topic wrote:
Dalibor Topic wrote:
Howdy,
I ocassionally try out classpath's configury mechanism, and it
always breaks down on me, so I must be doing something really
'special' to it.
I've tried the autogen.sh script too, preparing to reach for the
brown paper bag ...
but nope, that still breaks in the same way.
Something tells me that the PKG_* stuff is in pkg.m4, but for
some reason it does not get picked up aut either autoreconf, nor
autogen.sh
The reason is that they are not being told where to look for the
thrid-party m4 files. No idea if that's something particular to my
setup (am 1.8.3, ac 2.59, libtool 1.5.6), but an
${ACLOCAL} -I .
in autogen.sh fixes it, as far as I can tell.
Adding a AC_CONFIG_MACRO_DIR([.]) in configure.ac doesn't seem to
work though. I haven't tried moving the m4 files into their own
subdirectory, though.
cheers,
dalibor topic
For some reason, yet unknown, Michael put this macro in pkg.m4
instead of adding it to acinclude.m4 which is where all our local
macros go. Why it would be there, and augogen.sh would not have the
appropriate arguments to pick it up, is beyond me. It isn't a
standard file name, I checked the 1.7.8 autoconf manual. It needs to
be moved to
acinclude.m4.
This error only occurs on systems where pkk-config is not installed (or
pkg.m4 is not reachable). The code is in pkg.m4 because this is the
file we copied over from pkg-config. I would like to not put its
content into acinclude.m4. This makes maintaining (e.g. updating) it
harder. Instead we should just add -I . to autogen.sh. This adds the
code to aclocal.m4 and this is all we need.
As to the configure options you need, it's supposed to be just
--disable-jni for what you want. However, the link between this
option and the gtk-peer option may be broken, you may need to specify
both.
I will look into this.
Michael
___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
