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.

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

GLOB_OPTIONS mixes CFLAGS and CXXFLAGS which could be exclusively different [CORE3605] #3959

Closed
firebird-issue-importer opened this issue Sep 22, 2011 · 4 comments

Comments

@firebird-issue-importer

Submitted by: Mariusz Zynel (mariusz)

CFLAGS and CXXFLAGS are two different variables for two different compilers. Some options could be the same for both like -xO (optimization level) or -m64 (memory model) but there are switches exlusively different like -xstrconst (string literals treatment) or -Xa (conformance model)
which are cc options but not CC. So, it is a mistake to "Use configure's CFLAGS as global options for all compilers and linkers" as it is stated in make.defaults.

Commits: f8f918d

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Sep 22, 2011

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 12, 2011

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

Fix Version: 2.5.2 [ 10450 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 23, 2013

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 13, 2015

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants