Karel Zak wrote: > On Tue, Sep 02, 2008 at 04:37:03PM +0200, Robert Schwebel wrote: >> -Wl,/home/rsc/svn/oselas/bsp/pengutronix/OSELAS.BSP-Pengutronix-AllYes-trunk/platform-phyCORE-PXA270/sysroot-target/usr/lib >> -o mount mount-mount.o mount-fstab.o mount-mount_mntent.o >> mount-getusername.o mount-lomount.o mount-sundries.o mount-xmalloc.o >> mount-realpath.o mount-fsprobe.o mount-fsprobe_blkid.o mount-env.o >> mount-linux_version.o mount-blkdev.o mount-setproctitle.o -lblkid >> /home/rsc/svn/oselas/bsp/pengutronix/OSELAS.BSP-Pengutronix-AllYes-trunk/platform-phyCORE-PXA270/sysroot-target/usr/lib/libblkid.a(probe.o): >> In function `set_uuid': >> /home/rsc/svn/oselas/bsp/pengutronix/OSELAS.BSP-Pengutronix-AllYes-trunk/platform-phyCORE-PXA270/build-target/e2fsprogs-1.41.1/lib/blkid/probe.c:130: >> undefined reference to `uuid_is_null' >> ----------8<---------- I just hit this too. My scenario is different to Robert's but quite non-standard nonetheless. To cut a long story short: - native build - only static libs from e2fsprogs - non-standard --prefix util-linux-ng-2.13.1 works fine ie: -lblkid -luuid is passed on the link line and everything is sweet. > You needn't to specify all possible dependencies on gcc command > line... see my previous e-mail. It works. The -lblkid is enough if > your linker is able to evaluate dependencies and found all .so libs. True. But it feels kinda wrong relying on the linker like this. As has been proven, it doesn't work in all scenarios eg: non-standard prefix. I'm happy to work around the issue by using the provided env vars. But I just wanted to voice my concerns. Regards Greg -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
