Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15667] New: Missing files pc_x86_64_bios_defconfig
Date: Sun, 25 Jun 2023 22:23:25 +0000	[thread overview]
Message-ID: <bug-15667-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15667

            Bug ID: 15667
           Summary: Missing files pc_x86_64_bios_defconfig
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Outdated package
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: educarbnog2@yahoo.com.br
                CC: buildroot@uclibc.org
  Target Milestone: ---

Dear

I'm using Buildroot for a project using the pc_x86_64_bios_defconfig card, but
when copying the project it ends up generating an error in the compilation,
because two files are not present. They are libelf.h and gelf.h. My doubt is
where can I find these files and how to insert them in Buildroot?

I'm using Linux Ubuntu 22.04.2 LTS

Yours sincerely

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-06-25 22:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 22:23 bugzilla [this message]
2023-06-26  4:31 ` [Buildroot] [Bug 15667] Missing files pc_x86_64_bios_defconfig bugzilla
2024-06-15 15:11 ` bugzilla

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-15667-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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