-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[package] automake/1.16.4: Automake can't use autoconf packages and gives version error #9222
Comments
update: still getting the same error |
Are you sure you are using |
@ericLemanissier |
@WilliamBehrens I had the same error as you, when using |
My exact command is: |
Is there a config.log file in folder C:\Users\wbehrens.conan\data\automake\1.16.3__\build\3475bd55b91ae904ac96fde0f106a136ab951a5e you could send ? |
It just can't seem to find it at all, even though I checked the autoconf recipe and it is being added to the path |
I also tried making msys2 add autoconf via pacman with the "msys2:additional_packages=autoconf" and it installed and ran but still wasn't detected |
Also see #9048 |
I am not able to build |
See issue #9048 specifically my comment here: Seems to be a problem when you build it via |
@paulharris I noticed something similar conan-io/conan#11975 were 'tools.microsoft.bash:subsystem' from msys2 is not used by Autotools in it's test_package. Might this be releated? |
I guess this could be closed now? |
this is still the case when testing that. directly works fine, but not if automake is build in the process for another module. |
@prince-chrismc or someone else: This is part of
And this is part of the explicit build from
Notice these two lines which are missing for implicit building:
and Don't know whether this makes a difference ... but I need some point to start searching. The recipe itself seems to be fine, as the explicit build is working. Error message:
|
Is there is! When an reference is the root of the graph changes a few nuance behaviors, for example in 1.x the root can override depencies. Looking at your command the host profiles are different. Can you please try again with the same host profiles in case there was a typo? Post the full logs too please 🙏 Looking at the recipe conan-center-index/recipes/automake/all/conanfile.py Lines 47 to 48 in 90e2487
There's some weird legacy code stuff. Which I am not sure about. So I am not sure it's pulldown the dependencies like it should |
@prince-chrismc I found a way to easily reproduce this (clear your local cache, before ... I have seen cases when it worked if the cache was not empty ...):
Strangely this one is working, although it also requires on automake:
Default profile:
Fails with the same error message:
|
Full log of failing libuuid run
|
@prince-chrismc But this runs directly into the next problem with m4 within libtool:
full-log
|
Doing the same for libtool here is not helping. |
when running
while when running
Why is that happening and is it related to the problem? |
Another observation: Shouldnt't these two commands be equivalent?
The first one is failing with the same error mentioned in this issue the second one is successful. |
Also ran into the same error today. On macOS this happened to me: Autoconf build successfully but automake wouldn't find it. After some digging I found that all the resulting binaries of autoconf did not have the execution flag set so while in the path, they wouldn't be found as executables. First time such a thing happened to me. |
Package and Environment Details (include every applicable attribute)
Conan profile (output of
conan profile show default
orconan profile show <profile>
if custom profile is in use)Steps to reproduce (Include if Applicable)
conan create path\to\automake\ automake/1.16.4@ -pr:b=path\to\profile --build all
Logs (Include/Attach if Applicable)
Click to expand log
The text was updated successfully, but these errors were encountered: