Hi Jim,
That AI is probably hallucinating ancient advice for legacy versions, like your
other instructions below were.
If you told us the name or source of your package, we could be more helpful.
If cygport, or autoconf and automake, are installed, you have a version of
aclocal, that may be used by autoreconf as required.
You should always use Cygwin packaged versions of build tool packages, as they
have the customizations required to build using non-ELF PE format supporting
utilities and use Cygwin shared libraries and Windows system DLLs.
Otherwise you will have to redo all the effort put into building Msys2 (or the
Cygwin tool base) just to get to the point where you have tools that will work
with Cygwin.
Or you can use a BSD or Linux VM and their toolchains if you don't need Windows
support.
Normally current modern autotools packages include configure.ac which is used as
a template by autoreconf (-f -i -v most often) running autoconf to customize a
./configure script, which when run detects system characteristics, then runs
automake which uses those with the template Makefile.am(s) to customize
Makefile(s), allowing you to run make.
Have a look at what cygport cygautoreconf does with autoreconf:
https://cygwin.com/git/?p=cygwin-apps/cygport.git;a=blob;f=cygclass/autotools.cygclass#l203
https://cygwin.com/git/?p=cygwin-apps/cygport.git;a=blob;f=cygclass/autotools.cygclass#l549
or if cygport installed:
${VISUAL:-${EDITOR:-less}} '+/\/cygautoreconf$' \
/usr/share/cygport/cygclass/autotools.cygclass
and
/^\s*autoreconf\s
For background see the docs in:
$ info autoconf autoreconf
$ info automake aclocal
Similarly with cmake, ninja, and other build toolchains: see the cygport
cygclass doc entries and scripts, and the relevant man pages.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
On 2024-10-09 18:52, Jim McNamara via Cygwin wrote:
I harnessed the power of AI, and it advised to do edits to like makefile.am and
one other file I can pull the name to tomorrow after I get some sleep since I
dont have automake-bin. Also, as a strategy i could install automake from gnu
and gain access to that tool which is probably the route i will go because
running anything without the command aclocal and going to refresh it.
This is all abstraction to me other than I am jumping though some hoops to get
it on there.
On Wednesday, October 9th, 2024 at 8:07 PM, Jim McNamara via Cygwin wrote:
I had tried autoreconf -i.
I will keep thinking about it.
I am in a bit of a loop trying to troubleshoot it.
On Wednesday, October 9th, 2024 at 7:05 PM, Brian Inglis via Cygwin wrote:
On 2024-10-09 15:20, Jim McNamara via Cygwin wrote:
which package does cygwin have for automake-bin. I need aclocal because the
software i am installing has a newer automake, autoconf, and libtool than what
is available than the dir that resides in ./configure dir. It instructed me to
do this:
thanks for any help guys.
Steps to Resolve the Issue
Install automake-bin:
Run the Cygwin setup executable (setup-x86_64.exe for 64-bit).
Search for automake-bin.
Make sure it is selected for installation.
Reinstall automake:
To ensure compatibility, you might also want to reinstall the automake package
alongside automake-bin.
Verify Installation:
After installation, check if aclocal is now available:
bash
Copy code
aclocal --version
Regenerate Build Files:
Once aclocal is installed, you can run the necessary commands to regenerate
your project’s build files:
bash
Copy code
aclocal
autoconf
automake --add-missing
Continue the Build Process:
After regenerating the files, proceed with configuring and building your
project:
bash
Copy code
./configure --prefix=/usr/
make
By ensuring that both automake and automake-bin are installed, you should be
able to resolve the version issues and successfully run aclocal. If you
continue to face problems, please let me know!
Those must be really old instructions!
Check on the Cygwin Time Machine for automake-bin.
Repology.org has no hits for automake-bin, mostly just automake, including
Cygwin, and a couple of instances of automake-common and automake-vanilla.
That could also just be a reference to BSD or similar ports package names.
Normally on Cygwin package builds, you run autoreconf to update the package
autotools scripts and macros, and use or apply Cygwin adaptations to macros for
tool variants.
It is normally easier to install cygport and create a cygport script with
minimal variable definitions to automagically build and check a package using
autotools.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
