From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 74171] Attempting to build recent version of e2fsprogs from git repo gives config.h missing
Date: Thu, 17 Apr 2014 17:22:27 +0000 [thread overview]
Message-ID: <bug-74171-13602-KRlv1xQcV5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-74171-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=74171
--- Comment #2 from George R. Goffe <grgoffe@yahoo.com> ---
Theodore,
Thanks for your response and the time you spent formulating it.
I have found the problem.
By the way, I did read INSTALL and followed it's directives.
The problem is that when I build software I run make distclean then configure
then make clean depend then make then make install.
The make clean in this case removes the config.h file, hence the failures. My
thoughts about make clean are that this removes build products, object files,
etc.
I've seen other software that has this problem as well and have no-oped the
make clean in my build scripts.
My question to you is, "Should the config.h file and whatever configure
generates be part of the clean target or should it be part of make distclean"?
Regards,
George...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-04-17 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 10:27 [Bug 74171] New: Attempting to build recent version of e2fsprogs from git repo gives config.h missing bugzilla-daemon
2014-04-17 14:47 ` [Bug 74171] " bugzilla-daemon
2014-04-17 17:22 ` bugzilla-daemon [this message]
2014-04-17 18:40 ` bugzilla-daemon
2014-04-17 21:31 ` bugzilla-daemon
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=bug-74171-13602-KRlv1xQcV5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 NNTP newsgroup(s).