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.

Sign up for GitHub

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

Jump to bottom

Ensure full compiler version version displayed in RPM name for recent gcc versions #111

Closed
tswilliams opened this issue Apr 4, 2018 · 1 comment
Closed

Ensure full compiler version version displayed in RPM name for recent gcc versions #111

tswilliams opened this issue Apr 4, 2018 · 1 comment
Assignees
@tswilliams
Labels
bug
Milestone
v2.6.1 release

Comments

@tswilliams
Copy link
Collaborator

Originally pointed out by Jeroen Hegeman - https://svnweb.cern.ch/trac/cactus/ticket/2315#comment:15 ...

In modern versions of gcc - e.g. gcc7 - only the compiler's major version is printed when the -dumpversion flag is used; for these recent versions of gcc, the -dumpfullversion flag can be used to print the full version string. i.e. major.minor.patch. The full output can be obtained from all gcc versions using the command gcc -dumpfullversion -dumpversion

The makefiles should be updated so that a 3-tuple of version numbers is included in the uHAL RPM names when using any version of gcc (or e.g. clang).
@tswilliams tswilliams self-assigned this Apr 4, 2018
@tswilliams tswilliams added the bug label Apr 4, 2018
@tswilliams tswilliams added this to the v2.6.1 release milestone Apr 4, 2018
tswilliams added a commit that referenced this issue Apr 4, 2018
@tswilliams
uHAL : Ensure that compiler minor and patch version numbers included …
fda1267 
…in RPM names when using recent versions of gcc; refs #111
tswilliams added a commit that referenced this issue Apr 4, 2018
@tswilliams
extern : Include compiler version numer in release fields of boost an…
ba0d87f 
…d pugixml RPMs; refs #111
@tswilliams tswilliams mentioned this issue Apr 5, 2018
Merged
@tswilliams
Copy link
Collaborator Author

All done. Closing.

jhegeman pushed a commit to jhegeman/ipbus-software that referenced this issue Dec 6, 2021
@tswilliams
Merge pull request ipbus#111 from ipbus/bug/null-range-warning-vivado…
5da4906 
…2018.3

Resolve 'null range' critical warning in Vivado 2018.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tswilliams tswilliams

Labels
bug
Projects
None yet
Milestone
v2.6.1 release
Development

No branches or pull requests
1 participant
@tswilliams