Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-10 Thread Andreas Jochens
Hello, On 05-Sep-08 12:28, Petr Salinger wrote: Andreas J., I am just curious, are these patches also sufficient for ppc64 ? Basically yes, the are sufficient to build the package on ppc64. However, there is still a FTBFS problem with libmotif-dev on ppc64 so that lesstif2-dev has to be used

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-10 Thread Andreas Tille
On Fri, 9 Sep 2005, Andreas Jochens wrote: Basically yes, the are sufficient to build the package on ppc64. However, there is still a FTBFS problem with libmotif-dev on ppc64 so that lesstif2-dev has to be used instead. Please note that I observed a partly unusable user interface on i386

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-08 Thread Andreas Tille
On Wed, 7 Sep 2005, Andreas Jochens wrote: I get the following error on i386/unstable: make[3]: Entering directory `/arb-0.0.20050526/GDE/CORE' rm -f functions.h ../../MAKEBIN/aisc_mkpt -C *.c functions.h arb_replace -l 'DummyRepaint*=DummyRepaint();' functions.h arb_replace: error while

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-08 Thread Petr Salinger
arb_replace: error while loading shared libraries: libARBDB.so: cannot open shared object file: No such file or directory Ahh, thanks for this hint. This kind of bugs occure if you don't compile packages in a clean chroot. I had installed a former version of arb on the box I builded

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-08 Thread Andreas Tille
On Thu, 8 Sep 2005, Petr Salinger wrote: This can be also fixed with following in debian/rules. --- debian/rules~ 2005-08-31 07:18:37.0 + +++ debian/rules2005-09-08 08:05:21.0 + @@ -28,11 +28,13 @@ export ARBHOME=`pwd` ; \ export LC_ALL=C ; \

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-08 Thread Andreas Jochens
On 05-Sep-08 14:43, Andreas Tille wrote: Another question to Andreas: If I exclude amd86 from this architecture list the bug you reported is not really solved but it will not occure any more because it is circumvented. What would you prefer: [ ] Close the bug [ ] Reduce severity to

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-07 Thread Andreas Jochens
Package: arb Version: 0.0.20050526-1 Severity: serious When building 'arb' on amd64/unstable, I get the following error: GLwDrawA.c:651: warning: unused parameter 'params' GLwDrawA.c:651: warning: unused parameter 'numParams' GLwDrawA.c:344: warning: missing initializer GLwDrawA.c:344: warning:

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-07 Thread Andreas Tille
On Wed, 7 Sep 2005, Andreas Jochens wrote: When building 'arb' on amd64/unstable, I get the following error: Thanks for trying to build arb in amd64. I just want to warn you that upstream told me that on any 64Bit architecture arb is broken and will lead to errors. This is one reason for

Bug#327059: arb: FTBFS (amd64): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC

2005-09-07 Thread Andreas Jochens
Hello, thank you for your reply to my report. On 05-Sep-07 21:47, Andreas Tille wrote: On Wed, 7 Sep 2005, Andreas Jochens wrote: When this is fixed there are still other problems which prevent the package to build sucessfully. At least one of those other problems also appears on i386.