public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Jie Zhang <jie.zhang@analog.com>
To: insight@sourceware.org
Subject: Build CVS insight on x86_64
Date: Wed, 14 Jan 2009 11:00:00 -0000	[thread overview]
Message-ID: <496DC50C.1080802@analog.com> (raw)

Does anyone succeed in building CVS insight on x86_64? I tried a native 
build today on Debian unstable AMD64. But it failed. The error is:

gcc -pipe -shared -o libitk3.3.so itk_cmds.o itk_option.o 
itk_archetype.o itk_util.o itkStubInit.o -lX11 
-L/home/jie/sources/insight/build/tcl/unix -ltclstub8.4 
-L/home/jie/sources/insight/build/tk/unix -ltkstub8.4 
-L/home/jie/sources/insight/build/itcl/itcl -litclstub3.3
/usr/bin/ld: itk_cmds.o: relocation R_X86_64_32 against `a local symbol' 
can not be used when making a shared object; recompile with -fPIC
itk_cmds.o: could not read symbols: Bad value
collect2: ld returned 1 exit status

But it on i386 host is OK. But the insight 6.8 release on x86_64 is also OK.


Jie

             reply	other threads:[~2009-01-14 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 11:00 Jie Zhang [this message]
2009-02-26 22:10 ` Kevin Buettner
2009-02-28  7:22   ` Keith Seitz
2009-03-02 21:51     ` Kevin Buettner

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=496DC50C.1080802@analog.com \
    --to=jie.zhang@analog.com \
    --cc=insight@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).