On Fri, Jan 9, 2009 at 5:33 AM, Phil Oleson <o...@nixil.net> wrote:
> I did run into a linking issue with the build of...errr kdebase,
> kdebase-runtime, or kdebase-workspace.. I cant remember now.. but the
> issue was with hspell.  I had to rebuild it with this patch:
>
> --- Makefile.orig       2009-01-04 05:20:09.000000000 +0000
> +++ Makefile    2009-01-04 05:20:01.000000000 +0000
> @@ -16,6 +16,7 @@
>  USE_PERL5_BUILD=       yes
>  USE_GMAKE=     yes
>  GNU_CONFIGURE= yes
> +CFLAGS+=       -fPIC
>
>  MAN1=          hspell.1
>  MAN3=          hspell.3
>
The problem appears to be manifested in kdelibs4, but only on amd64
and not i386.  I received the same linker error in my amd64 tinderbox,
but not in my i386 tinderbox.  The specific error states:

/opt/c++  -fPIC -pipe -g -Woverloaded-virtual -fvisibility=hidden
-fvisibility-inlines-hidden -g -O2 -fno-reorder-blocks
-fno-schedule-insns -fno-inline  -rpath=/usr/lib:/usr/local/lib -lc
-shared -Wl,-soname,kspell_hspell.so -o ../../../lib/kspell_hspell.so
CMakeFiles/kspell_hspell.dir/kspell_hspell_automoc.o
CMakeFiles/kspell_hspell.dir/kspell_hspellclient.o
CMakeFiles/kspell_hspell.dir/kspell_hspelldict.o -L/usr/local/lib/qt4
-L/work/a/ports/x11/kdelibs4/work/kdelibs-4.1.85/build/lib
-L/usr/local/lib /usr/local/lib/qt4/libQtCore.so -lpthread
../../../lib/libkdecore.so.7.0.0 /usr/local/lib/libhspell.a -lz
/usr/local/lib/qt4/libQtDBus.so /usr/local/lib/qt4/libQtCore.so
-lpthread 
-Wl,-rpath,/usr/local/lib/qt4:/work/a/ports/x11/kdelibs4/work/kdelibs-4.1.85/build/lib
/usr/bin/ld: /usr/local/lib/libhspell.a(gimatria.o): relocation
R_X86_64_32S can not be used when making a shared object; recompile
with -fPIC
/usr/local/lib/libhspell.a: could not read symbols: Bad value

Does this help determine if there is a possible fix on the kdelibs end
or is it something that has to be changed in hspell?

Matt
_______________________________________________
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Reply via email to