Bug#383779: [Pkg-jed-sl-modules] Bug#383779: FTBFS on amd64: not creating PIC code?
package slang-slirp tags 383779 confirmed thanks * Kurt Roeckx <[EMAIL PROTECTED]> [2006-08-20 13:32]: > found 383779 1.9.0-1-3 > thanks > > It's still failing to build with the same error. Indeed. I thought that #383777 and #383779 were related to each other and closed both of them in slang-slirp_1.9.0-1-2. I will investigate the problem. -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: [Pkg-jed-sl-modules] Bug#383779: FTBFS on amd64: not creating PIC code?
Processing commands for [EMAIL PROTECTED]: > package slang-slirp Ignoring bugs not assigned to: slang-slirp > tags 383779 confirmed Bug#383779: FTBFS on amd64: not creating PIC code? There were no tags set. Tags added: confirmed > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383779: FTBFS on amd64: not creating PIC code?
found 383779 1.9.0-1-3 thanks It's still failing to build with the same error. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383779: FTBFS on amd64: not creating PIC code?
Package: slang-slirp Version: 1.9.0-1-1 Severity: serious slang-slirp doesn't build on amd64, probably because you're not building PIC code (see policy for more information on this requirement). | Testing examples/vec ... | /usr/bin/ld: fvec.o: relocation R_X86_64_32S against `a local symbol' | can not be used when making a shared object; recompile with -fPIC | fvec.o: could not read symbols: Bad value | collect2: ld returned 1 exit status http://buildd.debian.org/fetch.php?&pkg=slang-slirp&ver=1.9.0-1-1&arch=amd64&stamp=1155677704&file=log&as=raw -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
