automake-bin

Jim McNamara jmcnamara10001@proton.me
Thu Oct 10 00:07:43 GMT 2024


Hi Brian-

I had tried autoreconf -i.

 I will keep thinking about it.

I am in a bit of a loop trying to troubleshoot it.

thanks,
jim




Sent with Proton Mail secure email.

On Wednesday, October 9th, 2024 at 7:05 PM, Brian Inglis via Cygwin <cygwin@cygwin.com> wrote:

> On 2024-10-09 15:20, Jim McNamara via Cygwin wrote:
> 
> > Hi-
> > 
> > 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.
> > 
> > jim
> > 
> > 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


More information about the Cygwin mailing list