https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69988
Bug ID: 69988
Summary: libgo.so: undefined reference to `__unorddf2'
Product: gcc
Version: 5.2.1
URL: https://people.debian.org/~glaubitz/gcc-5_5.2.1-14_pow
erpcspe-20160226-2238.build
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: glaubitz at physik dot fu-berlin.de
CC: doko at debian dot org
Target Milestone: ---
Host: powerpc-linux-gnuspe
Target: powerpc-linux-gnuspe
Build: powerpc-linux-gnuspe
Hello!
I'm currently working on reviving Debian's powerpcspe port. After fixing some
minor issues in Debian's packaging for powerpcspe, I am stumbling over an issue
that I would consider a bug:
/«PKGBUILDDIR»/build/./gcc/gccgo -B/«PKGBUILDDIR»/build/./gcc/ -g -O2
-static-libstdc++ -static-libgcc -Wl,-z,relro -L
../powerpc-linux-gnuspe/libgo -L ../powe
rpc-linux-gnuspe/libgo/.libs -o gofmt
../../src/gotools/../libgo/go/cmd/gofmt/doc.go
../../src/gotools/../libgo/go/cmd/gofmt/gofmt.go ../../src/gotools/../libgo
/go/cmd/gofmt/rewrite.go
../../src/gotools/../libgo/go/cmd/gofmt/simplify.go
../powerpc-linux-gnuspe/libgo/.libs/libgo.so: undefined reference to
`__unorddf2'
collect2: error: ld returned 1 exit status
Makefile:629: recipe for target 'gofmt' failed
make[4]: *** [gofmt] Error 1
make[4]: Leaving directory '/«PKGBUILDDIR»/build/gotools'
Makefile:12509: recipe for target 'all-gotools' failed
make[3]: *** [all-gotools] Error 2
I asssume that unorddf2 is normally present in libgcc, so the linking above
should not fail. But assume the above happens because the unorddf2 symbol might
be undefined since the differentian between "powerpc" and "powerpcspe" is
missing, i.e. the code is compiled as if on a powerpc with an FPU.
But I'm just guessing from experience from seeing similar issues on x86_64 vs.
x32.
PS: I couldn't test anything newer than gcc-5.2.1 yet since the gcc-5.3.x
packages in Debian build-depend on g++-5 itself. gcc-5 has not been built on
powerpcspe yet which is why I wanted to start with an older version first, then
build the current version of the gcc-5 package.
Cheers,
Adrian
