Your message dated Mon, 12 May 2008 00:05:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#480708: bin-prot: FTBFS: Not using -fPIC to create 
shared library.
has caused the Debian Bug report #480708,
regarding bin-prot: FTBFS: Not using -fPIC to create shared library.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
480708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480708
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bin-prot
Version: 1.0.5-3
Severity: serious

Hi,

Your package is failing to build with the following error:
ocamlmklib    -I +camlp4     \
                                -o bin_prot_stubs  common_stubs.o read_stubs.o 
write_stubs.o   \

/usr/bin/ld: write_stubs.o: relocation R_X86_64_32 against `a local symbol' can 
not be used when making a shared object; recompile with -fPIC
write_stubs.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[3]: *** [dllbin_prot_stubs.so] Error 2

To make a shared library, the files need to be compiled using -fPIC.
Please see section 10.2 of the policy.


Kurt




--- End Message ---
--- Begin Message ---
On Sun, May 11, 2008 at 07:34:48PM +0200, Kurt Roeckx wrote:
> Package: bin-prot
> Version: 1.0.5-3
> Severity: serious
> 
> Hi,
> 
> Your package is failing to build with the following error:
> ocamlmklib    -I +camlp4     \
>                                 -o bin_prot_stubs  common_stubs.o 
> read_stubs.o write_stubs.o   \
> 
> /usr/bin/ld: write_stubs.o: relocation R_X86_64_32 against `a local symbol' 
> can not be used when making a shared object; recompile with -fPIC

This was fixed tight ahead in 1.0.5-4, uploaded to delayed-1 2 days ago.
I discover only now that it has ended up in BROKEN on the delayed queue,
don't know why. I'm re-uploading right now straight away in the
archive ...

Cheers.

-- 
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
[EMAIL PROTECTED],cs.unibo.it,debian.org}  -<%>-  http://upsilon.cc/zack/
(15:56:48)  Zack: e la demo dema ?    /\    All one has to do is hit the
(15:57:15)  Bac: no, la demo scema    \/    right keys at the right time

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to