On Wed, Jan 19, 2011 at 11:13:43AM +0100, Fabian Groffen wrote:
> On 19-01-2011 10:51:52 +0100, Karel Zak wrote:
> > Anyway, we have more gcc-isms in our code and I'm really not sure if
> > we need to care about portability in this way. Don't forget that our
> > primary goal is Linux and usability on Linux is more important (for
> > us) than portability.
> >
> > Why do you need to port whole util-linux to non-glibc and non-gcc
> > environment?
>
> Not sure about the original reporter, but at the moment, the big problem
> I have, is that I need libuuid and libblkid on non-Linux, which formerly
> came from e2fsprogs-libs. The rest of util-linux is not of interest.
./configure
make -C shlibs/{uuid,blkid}/src/
make -C shlibs/{uuid,blkid}/src/ install
and note that our build-system already have "if LINUX", so many
Linux-only utils are ignored on non-LInux systems.
Anyway, I don't see a problem to add --disable-{disk-utils,fdisks,...}
for the configure script to disable some groups of commands.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
