Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35048 - [gcc-go] creates wrong executables by default
Attached to Project:
Arch Linux
Opened by Jamp (jamp) - Wednesday, 01 May 2013, 12:00 GMT
Last edited by Allan McRae (Allan) - Saturday, 01 June 2013, 00:02 GMT
Opened by Jamp (jamp) - Wednesday, 01 May 2013, 12:00 GMT
Last edited by Allan McRae (Allan) - Saturday, 01 June 2013, 00:02 GMT
|
DetailsDescription:
gccgo creates wrong executables by default Additional info: * package version(s) * config and/or log files etc. gcc-4.8.0-[1-3] Steps to reproduce: compile a simple program. E.g. take the following code taken from then golang.ord home page and create a file named "hello.go" with it --------------------------------------------snip package main import "fmt" func main() { fmt.Println("Hello, 世界") } --------------------------------------------snip then $ gccgo -g hello.go -o go_hello $ ./go_hello Hello, 世界 $ gccgo hello.go -o sgo_hello # i.e. compile without the -g flag $ ./sgo_hello no debug info in ELF executable errno -1 fatal error: no debug info in ELF executable $ strip go_hello # the same happens if we strip the previous, working, executable $ ./go_hello no debug info in ELF executable errno -1 fatal error: no debug info in ELF executable |
This task depends upon
gcc-4.8-20130210 - good
gcc-4.8-20130217 - bad