Hi,
George Danchev wrote:
> $ dpkg-checkbuilddeps # to check you have all build-dependencies installed
> $ dpkg-buildpackage
Ok. The messages from remnant root-owned result files tell me
that this is indeed 2.30.3-2.
dpkg-source: error: cannot write brasero_2.30.3-2.dsc: Permission denied
After a long build process i run into a problem with the local
installation of libburn:
libtool: relink: gcc -shared .libs/burn-libburn.o
.libs/burn-libburn-common.o -L/home/thomas/brasero-2.30.3/debian/tmp//usr/lib
-L/usr/lib -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -L/usr/local/lib
-L/home/thomas/brasero-2.30.3/debian/tmp//usr/local/lib -lburn -lisofs
-lbrasero-burn -pthread -pthread -Wl,-soname -Wl,libbrasero-libburn.so -o
.libs/libbrasero-libburn.so
/usr/bin/ld: /usr/lib/libburn.a(async.o): relocation R_X86_64_32 against
`.rodata.str1.8' can not be used when making a shared object; recompile with
-fPIC
/usr/lib/libburn.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
libtool: install: error: relink `libbrasero-libburn.la' with the above
command before installing it
It is compiled and installed from my upstream release source.
It works fine with the upstream release of libisoburn and xorriso.
libburn.so.4 => /usr/local/lib/libburn.so.4 (0x00007f55f4768000)
Why does Brasero want libburn.a ? Aren't static libs out of fashion ?
Shall i try something like
apt-get install libburn
?
Do i have to clean up beforehand ? How ?
I will try further tomorrow.
> Yeah, someone uses a naughty mailer :)
Ja, ja. Just make fun of old people and their IT equipment ...
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
