From: Marc Lehmann <schmorp@schmorp.de>
To: xfs@oss.sgi.com
Subject: Re: git xfsprogs don't build
Date: Sun, 6 Mar 2011 01:00:33 +0100 [thread overview]
Message-ID: <20110306000033.GA14083@schmorp.de> (raw)
In-Reply-To: <20110305005253.GA11865@infradead.org>
On Fri, Mar 04, 2011 at 07:52:53PM -0500, Christoph Hellwig <hch@infradead.org> wrote:
> On Fri, Mar 04, 2011 at 05:36:08PM +0100, Marc Lehmann wrote:
> > That almost certainly means somebody tried to build a shared object or
> > library with some object file compiled without -fPIC.
>
> That function indeed doesn't exist in non-debug builds. But by default
> we do not build xfsprogs that way.
-fPIC isn't a function, it tells gcc to not generate text relocations -
these are not supported on linux amd64.
> For now make sure to not have
> -DNDEBUG in your CFLAGS, I'll make sure we get a proper fix commited.
Well, I didn't have -DNDEBUG in my CFLAGS, but libxfs/Makefile and
libxlog/Makefile apparently had them. After removing them, I indeed do not
get the linker issue on amd64, but similar errors as on ia32:
http://ue.tst.eu/1b84c67209430c03b238b48eae7da108.txt
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-03-05 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:36 git xfsprogs don't build Marc Lehmann
2011-03-05 0:52 ` Christoph Hellwig
2011-03-06 0:00 ` Marc Lehmann [this message]
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=20110306000033.GA14083@schmorp.de \
--to=schmorp@schmorp.de \
--cc=xfs@oss.sgi.com \
/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