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

cmd/go: pass arguments for linking with 8l,6l,5l using environment variable #2996

Closed
cookieo9 opened this issue Feb 12, 2012 · 6 comments
Closed

cmd/go: pass arguments for linking with 8l,6l,5l using environment variable #2996

cookieo9 opened this issue Feb 12, 2012 · 6 comments
Labels
FrozenDueToAge
Milestone
Go1

Comments

@cookieo9
Copy link
Contributor 

There currently exists a method of passing flags to the go compilers (8g,6g,5g) by using
the environment variable GCFLAGS. There should be a similar one for flags to the linker
(8l,6l,5l).
@alberts
Copy link
Contributor

alberts commented Feb 12, 2012

Comment 1:

This is useful for getting gcov/lcov to work. You need GCFLAGS=--coverage and
LDFLAGS=-lgcov.

@rsc
Copy link
Contributor

rsc commented Feb 14, 2012

Comment 2:

I don't think $GLDFLAGS is the right name.
What did it used to be?  Also it is possible
that these should be command-line arguments
instead of environment variables.  I will look
into this.

Labels changed: added priority-go1, go1-must, removed priority-triage.

Status changed to Accepted.

@cookieo9
Copy link
Contributor Author

Comment 3:

I just chose the name GLDFLAGS because it was analagous (in my mind) to the change from
CFLAGS to GCFLAGS. LDFLAGS is probably more suitable since they are flags for ld, but
that might interact with arguments users want to set for linking with GCC.
Should I close my CL (http://golang.org/cl/5652074/)?

@cookieo9
Copy link
Contributor Author

Comment 4:

I just chose the name GLDFLAGS because it was analagous (in my mind) to the change from
CFLAGS to GCFLAGS. LDFLAGS is probably more suitable since they are flags for ld, but
that might interact with arguments users want to set for linking with GCC.
Should I close my CL? http://golang.org/cl/5652074/

@robpike
Copy link
Contributor

robpike commented Feb 26, 2012

Comment 5:

Owner changed to builder@golang.org.

@rsc
Copy link
Contributor

rsc commented Mar 1, 2012

Comment 6:

This issue was closed by revision b03a5f6.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1
Development

No branches or pull requests
5 participants
@rsc @cookieo9 @alberts @robpike @gopherbot