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

Bug#335199: marked as done (cupsys: FTBFS: Not using -fPIC to make shared lib.)



Your message dated Mon, 05 Jun 2006 11:04:37 +0900
with message-id <20060605020248.CAD4122310F@mail.topstudio.co.jp>
and subject line CUPS 1.2.1 is uploaded into unstable, so it fixes fixed-in-experimental bugs and some others
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: cupsys
Version: 1.1.99.b1.r4748-1
Severity: serious
Tags: experimental

Hi,

Your package is failing to build on amd64 with the following
error:
Linking libcups.so.2...
/usr/bin/ld: array.o: relocation R_X86_64_PC32 against `cupsArrayCurrent' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value

The build log does not show the actual commands used to compile,
but it probably didn't use -fPIC to make array.o and the other .o
files.  To make a shared library you need to be using -fPIC.  For
a static library you shouldn't be using it.


Kurt



--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Version: 1.2.1-1
Tags: fixed
thanks

Now we uploaded CUPS 1.2.1 to unstable.
fixed-in-experimental bugs can be closed.

About #349341, I noticed I needed to modify the order of control file.
It's already fixed and will provide a correct dependency.

Thanks,
- -- 
Kenshi Muto
kmuto@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAkSDkSgACgkQQKW+7XLQPLHByQCg3bF/mPIwNaPhi6L1zCCA+pt+
yJ4AoKvTNyFgE0WmEtVfpbiZP/mPaBi1
=cnm4
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: