Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

m4 problem in autoreconf #134

Open
VictorEijkhout opened this issue Mar 18, 2024 · 5 comments
Open

m4 problem in autoreconf #134

VictorEijkhout opened this issue Mar 18, 2024 · 5 comments

Comments

@VictorEijkhout
Copy link

configure.ac:452: error: m4_defn: undefined macro: LT_PACKAGE_VERSION
m4/libtool.m4:40: LT_PREREQ is expanded from...
configure.ac:452: the top level
autom4te: error: /work/00434/eijkhout/m4/installation-m4-1.4.19-milan-gcc13/bin/m4 failed with exit status: 1
aclocal: error: /work/00434/eijkhout/autoconf/installation-autoconf-2.72-milan-gcc13/bin/autom4te failed with exit status: 1
autoreconf: error: aclocal failed with exit status: 1

I have compiler m4/autoconf/automake/libtool from source since my system did not have the latest versions you requested. Did I miss something in the setup? The Gnu pages seem to indicate that configure/make on each of these should be enough.

@wkliao
Copy link
Member

wkliao commented Mar 18, 2024

If building PnetCDF using its official releases, you do not need to run autoreconf.
Running command configure is sufficient.
Running autoreconf is only required when building from a clone of GitHub repo.

@VictorEijkhout
Copy link
Author

Right. I'm now able to build the official release.

But I'm still wondering (just a little) where this problem with installing from a git clone comes from.

@wkliao
Copy link
Member

wkliao commented Mar 19, 2024

Maybe your libtool version is older than 2.4.6.
Please check with command "libtool --version".

@VictorEijkhout
Copy link
Author

libtool --version
libtool (GNU libtool) 2.4.7
Written by Gordon Matzigkeit, 1996

Copyright (C) 2014 Free Software Foundation, Inc

Besides, it says the macro is undefined. I tried setting it as an environment variable but that didn't help.

@wkliao
Copy link
Member

wkliao commented Mar 19, 2024

I tested it with libtool 2.4.6 only. Maybe there is a conflict when using 2.4.7.
Could you give 2.4.6 a try?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants