From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: lyman@alum.mit.edu, util-linux@vger.kernel.org
Subject: Re: May I help you to fix the source code for util-linux?
Date: Wed, 5 Jul 2023 19:57:43 -0500 [thread overview]
Message-ID: <fbe542bf-954c-90e9-4c7f-5e2a2aa3f786@gmail.com> (raw)
In-Reply-To: <CAGLH8RSpmqZJOvcO+1so1zz4q9cs5GyEtGL9oZ8as0tAemCo8g@mail.gmail.com>
On 7/5/23 19:23, Lyman Opie wrote:
> Dear friends who have worked on the util-linux source code,
>
> Thank you for the util-linux package.
>
> I'm an M.I.T. graduate, who has been compiling linux source code for
> almost as long it has existed. A problem has crept into the
> util-linux source code:
>
> When I run its "configure" script, it eventually fails, reporting
> error: C++ preprocessor "/lib/cpp" fails sanity check
>
> The lack of sanity is not in cpp, but in the configure script, which
> calls cpp with a command line tens of thousands of characters long,
> which consists almost entirely of thousands of repetitions of the
> command-line arguments "-D _GNU_SOURCE".
>
> I am looking into a way to fix this, but perhaps someone who is
> already familiar with the source code can tell me immediately how this
> might be fixed?
>
> If someone has a chance to email me, I'd be pleased to hear from you.
> I thank you kindly for reading.
Wow. A problem with no information in which to help. What is your host
distribution? What is the command line? What version of util-linux? What hardware?
On my linuxfromscratch system on x86_64 I run:
tar -xf util-linux-2.39.1.tar.xz
cd util-linux-2.39.1
./configure
It runs perfectly in slightly under 7 seconds. You are doing something wrong or
have a really unusual system, but you give far too little information to let others help.
-- Bruce
prev parent reply other threads:[~2023-07-06 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 0:23 May I help you to fix the source code for util-linux? Lyman Opie
2023-07-06 0:57 ` Bruce Dubbs [this message]
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=fbe542bf-954c-90e9-4c7f-5e2a2aa3f786@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=lyman@alum.mit.edu \
--cc=util-linux@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).