From: Milind <milind@gslab.com>
To: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Cc: Theodore Tso <tytso@mit.edu>
Subject: CFLAGS not taken while linking mkfs.xfs?
Date: Wed, 20 May 2009 17:30:27 +0530 [thread overview]
Message-ID: <1242820827.3457.21.camel@alhena> (raw)
My CFLAGS are
-Wl,--dynamic-linker,/home/beehive/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/ld-linux-x86-64.so.2,--rpath,/home/beehive/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/
when I cross compile xfsprogs and do ldd on mkfs/mkfs.xfs I see
following thing
linux-vdso.so.1 => (0x00007fff8e5fe000)
libuuid.so.1
=> /home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/libuuid.so.1 (0x00007f4386030000)
librt.so.1
=> /home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/librt.so.1 (0x00007f4385e15000)
libpthread.so.0
=> /home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/libpthread.so.0 (0x00007f4385bfa000)
libc.so.6
=> /home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/libc.so.6 (0x00007f43858b1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4386236000)
shouldn't mkfs.xfs be dependant
on /home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/ld-linux-x86-64.so.2
rather than
/lib64/ld-linux-x86-64.so.2 (0x00007f4386236000)?
When do following changes it works.
ifdef LTCOMMAND
$(LTCOMMAND) : $(SUBDIRS) $(OBJECTS) $(LTDEPENDENCIES)
- $(LTLINK) -o $@ $(LDFLAGS) $(OBJECTS) $(LDLIBS)
+ $(LTLINK) -o $@ $(CFLAGSS) $(LDFLAGS) $(OBJECTS) $(LDLIBS)
endif
linking of mkfs.xfs happes as follows with above change
libtool: link:
gcc
-Wl,--dynamic-linker,/home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/ld-linux-x86-64.so.2,
--rpath,/home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib -o
mkfs.xfs maxtrres.o proto.o xfs_mkfs.o ../libxfs/.libs/libxfs.a
-luuid ../libdisk/.libs/libdisk.a -lrt -lpthread
above problem is seen for other binaries too. Like xfs_io, xfs_copy.
-Miline
reply other threads:[~2009-05-20 12:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1242820827.3457.21.camel@alhena \
--to=milind@gslab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).