[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Pkg-fonts-devel] Bug#676010: marked as done (grcompiler: FTBFS: gdlpp-cpp1.o: could not read symbols: Bad value)



Your message dated Sun, 17 Jun 2012 22:49:40 +0200
with message-id <20120617204940.GA27948@xanadu.blop.info>
and subject line not reproducible in a more recent rebuild, closing...
has caused the Debian Bug report #676010,
regarding grcompiler: FTBFS: gdlpp-cpp1.o: could not read symbols: Bad value
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 owner@bugs.debian.org
immediately.)


-- 
676010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676010
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: grcompiler
Version: 4.2~pre5-2
Severity: serious
Tags: wheezy sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /usr/bin/ld: gdlpp-cpp1.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
> gdlpp-cpp1.o: could not read symbols: Bad value
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/grcompiler_4.2~pre5-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



--- End Message ---
--- Begin Message ---
Those bugs are no longer reproducible in another rebuild in the same
conditions. Thus, closing them.

Lucas


--- End Message ---

Reply to: