-
Notifications
You must be signed in to change notification settings - Fork 45
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
Enhancement: Update rpm spec files with autogen options #206
Comments
The spec file from
The
So, whatever the system macros are set to ... that's what will be getting used. It's basically going to pass the macro value for all configure options it can. If you have a dist tarball, you can override this by doing like:
Edit: Honestly, there really isn't a connection between the
Instead of
The Spec file in the resulting tarball builds based on the macro values of the build host instead of having hard coded values. |
If you look at my CentOS8 PR, you can see that I'm appending the %configure macro. This came about yesterday while trying to figure out why the build worked perfectly in a manual install, but failed in CircleCI. It would be fairly easy to add the autgen switches too. The question is whether overloading the same switches results in an error, or if configure works like gcc and uses the last switch value. |
Looks like it uses the last one passed ... at least with the
Edit: Changed second |
@jcsiadal is there anything still outstanding in this issue? |
No, but since you determined that all is good with configure, it's an easy fix (much appreciated). I'll own this because I believe that any option I pass to autogen needs to be reflected in all generated components. |
Autogen.sh command line options should update the configure parameters in the specfiles. When using the CI system, identical options need to be configured for both the autogen.sh and RPM spec.in file.
It would be useful for the configure script in the generated specfile to include the parameters passed to the initial autogen script. It also seems logical that autogen should pre-configure all source files.
The text was updated successfully, but these errors were encountered: