[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building portions of coreutils

From: NightStrike
Subject: Re: Building portions of coreutils
Date: Sat, 2 Feb 2008 16:11:05 -0500

On 2/2/08, Eric Blake <address@hidden> wrote:
> Hash: SHA1
> According to NightStrike on 2/2/2008 9:17 AM:
> |
> | That would work, but that requires configure to complete for the
> | entire set of utils.  I was hoping for something like "--disable-all
> | --enable-ls" or some such thing passed to configure to only run the
> | configure tests for the pieces of coreutils that I want to build.
> | That way, the configure tests that fail won't affect me.
> Which configure tests are failing?  The problem is that it's extremely
> difficult to pick which subset of configure tests are relevant to a
> particular binary, since the same workarounds are shared among so many
> binaries.  But without details, we can't help investigate workarounds.
> Meanwhile, you can prime the cache before running configure by setting
> appropriate variables, or even post-edit the resulting config.h to better
> match the true characteristics of your platform.

checking for BEOS mounted file system support functions... no
checking whether it is possible to resort to fread on /etc/mnttab... no
configure: error: could not determine how to read list of mounted file systems

There's a message in the mailing list archive from several years ago
where someone else encountered this.  I don't have the link offhand,
but someone replied asking for a wya to do it in windows, and some
sample code.  The thread ended there, though, so I imagine there's
been no more progress.  If you know of a way to at least bypass the
configure test, that'd be a good start.

> |
> | To be even more precise, I want to see how many of the core utils I
> | can get to natively compile for x86_64-pc-mingw32 using the new
> | compiler I just built.
> Mingw has notoriously been a difficult porting platform, thanks to its
> lack of standards compliance.  Even worse is the fact that 64-bit support
> for mingw is so new.  I wish you luck in your efforts.

Thanks :)  I agree that mingw is a very hard platform to work with.
My intent is to just get enough programs working to be able to
configure and build the toolchain (binutils, gcc, and gdb).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]