From: "François Bissey" <f.r.bissey@massey.ac.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sage-singular
Date: Tue, 13 Apr 2010 07:22:30 +1200 [thread overview]
Message-ID: <201004130722.30717.f.r.bissey@massey.ac.nz> (raw)
In-Reply-To: <1271087445.7325.2@ledaig>
> François,
>
> Singular -- good. I do get -fPIC compile issues here on my amd64:
>
> g++ -shared -o libsingular.so \
> libsingular-tesths.o iparith.o mpsr_Tok.o claptmpl.o \
> grammar.o scanner.o attrib.o eigenval_ip.o extra.o fehelp.o
> feOpt.o ipassign.o ipconv.o ipid.o iplib.o ipprint.o ipshell.o lists.o
> sdb.o fglm.o interpolation.o silink.o subexpr.o janet.o wrapper.o
> libparse.o sing_win.o gms.o pcv.o maps_ip.o walk.o walk_ip.o cntrlc.o
> misc.o calcSVD.o slInit_Dynamic.o -lkernel -L../kernel -L../factory
> -L../libfac
> -L/var/tmp/portage/sci-mathematics/sage-singular-3.1.0.4.20100214/work/sing
> ular-3-1-0-4-20100214/src/build/opt/sage/local/lib64 -lsingfac -lsingcf
> -lntl -lreadline -lgmp -lomalloc
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/../../../../x86_64-pc-linux-gnu/bin/
> ld: libsingular-tesths.o: relocation R_X86_64_32 against `a local symbol'
> can not be used when making a shared object; recompile with -fPIC
>
> I've tinkered with this in the past and the following allowed building
> to proceed.
>
> sed -e "s:@CFLAGS@:@CFLAGS@ -fPIC:" -e
> "s:@CXXFLAGS@:@CXXFLAGS@ -fPIC:" \
> -i */Makefile.in || die "failed to fix CFLAGS in
> Makefile.in files"
> sed -e "s:@CFLAGS@:@CFLAGS@ -fPIC:" -e
> "s:@CXXFLAGS@:@CXXFLAGS@ -fPIC:" \
> -i factory/GNUmakefile.in || die "failed to fix CFLAGS
> in GNUmakefile.in"
> sed -e "s:{libdir} \${LIBSINGULAR_LIBS}:{libdir} -Wl,-soname
> \${LIBSINGULAR_LIBS}:" \
> -i Singular/Makefile.in || die "failed to fix LDFLAGS
> in Makefile.in"
>
> but this may not be the best way to fix things. I did notice that Sage
> builds Singular with -fPIC for all architectures.
>
Hi Steve,
indeed you would! -fPIC is mandatory on amd64 I think.
I was concerned that we shouldn't build the binaries or the static libraries
with -fPIC. That being said it looks like all those static libraries are
useless.
Francois
next prev parent reply other threads:[~2010-04-12 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 15:50 [gentoo-science] sage-singular Steven Trogdon
2010-04-12 19:22 ` François Bissey [this message]
2010-04-12 20:22 ` Steven Trogdon
2010-04-12 20:33 ` François Bissey
2010-04-12 21:51 ` François Bissey
2010-04-12 22:59 ` Steven Trogdon
2010-04-13 1:14 ` François Bissey
2010-04-13 4:56 ` Steven Trogdon
2010-04-13 5:05 ` François Bissey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004130722.30717.f.r.bissey@massey.ac.nz \
--to=f.r.bissey@massey.ac.nz \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox