GOFLAGS support in dpkg-buildflags, and using it
Bug #1318610 reported by
Matthias Klose
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpkg (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| Trusty |
New
|
Undecided
|
Unassigned | ||
| Utopic |
Won't Fix
|
Undecided
|
Unassigned | ||
| gccgo-go (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
| Trusty |
New
|
Undecided
|
Unassigned | ||
| Utopic |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
gccgo-go currently has:
# dpkg has not explicit GOFLAGS; however GCJFLAGS fits OK
export GOFLAGS=$(GCJFLAGS)
please don't work around this and using a value . A way to properly address this:
- find out the subset of values which work with both gc and gccgo.
- follow-up to Debian #744326, or a file a new report to support GOFLAGS
with this new value
| Changed in gccgo-go (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Matthias Klose (doko) wrote | #1 |
| Changed in gccgo-go (Ubuntu): | |
| status: | Triaged → Invalid |
| Changed in dpkg (Ubuntu Utopic): | |
| status: | New → Won't Fix |
| Changed in gccgo-go (Ubuntu Utopic): | |
| status: | New → Won't Fix |
To post a comment you must log in.
gccgo-go is removed in vivid, superseded by gccgo-5