Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

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

Closed by  Allan McRae (Allan)
Saturday, 01 June 2013, 00:02 GMT
Reason for closing:  Upstream
Comment by Allan McRae (Allan) - Wednesday, 01 May 2013, 13:34 GMT Comment by Allan McRae (Allan) - Tuesday, 07 May 2013, 05:28 GMT
Bisecting:
gcc-4.8-20130210 - good
gcc-4.8-20130217 - bad
Comment by Allan McRae (Allan) - Tuesday, 07 May 2013, 11:01 GMT Comment by Allan McRae (Allan) - Tuesday, 07 May 2013, 11:06 GMT Comment by Allan McRae (Allan) - Saturday, 01 June 2013, 00:02 GMT
Closing as upstream issue given it is reported there and a simple workaround is available.

Loading...