Thanks Theodore,
It worked.
I have one question regarding building libuuid.so
$/usr/bin/ldd lib/libuuid.so.1.2 shows
linux-vdso.so.1 => (0x00007fff075fe000)
libc.so.6=> /home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/libc.so.6 (0x00007faafef52000)
/lib64/ld-linux-x86-64.so.2 (0x00007faaff4a3000)
my CFLAGS are
CFLAGS=-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/
libuuid.so is supposed to have dependancy
on /home/miline/toolchain/x86_64-unknown-linux-gnu/glibc-2.7/lib/ld-linux-x86-64.so.2 (third entry in ldd output) right? And not on /lib64/ld-linux-x86-64.so.2
I tried modifying as follows but didn't really work. Any comments?
lib/uuid/Makefile:321
- @(cd elfshared; $(CC) --shared -o $(ELF_LIB) $(LDFLAGS) \
+ @(cd elfshared; $(CC) --shared -o $(ELF_LIB) $(CFLAGS) $(LDFLAGS) \
-Wl,-soname,$(ELF_SONAME) $(OBJS) $(ELF_OTHER_LIBS))
I have seen this problem in xfsprogs package too, should post the fix
in new thread.
-Miline
On Wed, 2009-05-20 at 06:50 -0400, Theodore Tso wrote:
> On Wed, May 20, 2009 at 11:13:30AM +0530, Milind wrote:
> > I am building xfsprogs to add it to my toolchain and want xfsprogs to
> > refer to my toolchain's libuuid. So I need libuuid.so in my toolchain.
> > But building e2fsprogs from sources doesn't build libuuid as .so (builds
> > as .a). Could you please give some pointers on building libuuid as .so?
>
> Add to the configure script --enable-elf-shared (I assume this is on a
> Linux system, right?). There are a number of configure options. Run
> configure --help to see them....
>
> > Do I have to change Makefiles? How do you do it for ubuntu/debian
> > packages that you maintain?
>
> The debian packages are built using the standard debian packaging
> framework, which means a number of support programs, one of which
> eventually runs "make -f debian/rules" with various makefile targets.
> Take a look at it, but be warned it's rather complicated.
>
> The debian packages ultimately end up building e2fsprogs three times,
> with different sets of configure options. One is the standard build,
> one is for the restricted-size build for boot floppies (which arguably
> we don't need any more since we these days CD-ROM's have plenty of
> space, and Debian doesn't support boot floppies any more) and one is
> for the static build for e2fsck.static (although the utility of that
> one is somewhat dubious given that even the shell is with shared
> library, so if the filesystem is corrupted enough that shared libaries
> don't work, it's rescue CD-ROM time; the main use for e2fsck.static is
> for emergency use when someone running an older version of Debian
> needs a newer e2fsck to fix a filesystem corruption).
>
> - Ted
>
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
