All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 74171] New: Attempting to build recent version of e2fsprogs from git repo gives config.h missing
Date: Wed, 16 Apr 2014 10:27:44 +0000	[thread overview]
Message-ID: <bug-74171-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=74171

            Bug ID: 74171
           Summary: Attempting to build recent version of e2fsprogs from
                    git repo gives config.h missing
           Product: File System
           Version: 2.5
    Kernel Version: 3.13.9-100.fc19.x86_64
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: grgoffe@yahoo.com
        Regression: No

This is my first time attempting to build e2fsprogs from the git repo. I'm
getting a failure with config.h missing. Here's a sample of the error message.
I have a complete build log available if needed.

../../../lib/uuid/unparse.c:35:20: fatal error: config.h: No such file or
directory

This is a fedora 19 x86_64 system.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2014-04-16 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 10:27 bugzilla-daemon [this message]
2014-04-17 14:47 ` [Bug 74171] Attempting to build recent version of e2fsprogs from git repo gives config.h missing bugzilla-daemon
2014-04-17 17:22 ` bugzilla-daemon
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.