From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14311] Cannot compile dahdi (part of Asterisk) for x86 (P1mmx).
Date: Tue, 02 Nov 2021 20:22:31 +0000 [thread overview]
Message-ID: <bug-14311-163-A9QLE3mg8F@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14311-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14311
--- Comment #3 from ingineru_de_sistem@yahoo.com ---
Hello/Salut,
I am using this one here
~/buildroot$ git log | head
commit bcde80febd2f0455ba5c34f8aa870fc8133749ae
Author: James Hilliard <james.hilliard1@gmail.com>
Date: Mon Oct 25 02:04:46 2021 -0600
The buildroot config was attached before .
One small patch had to be done due to a missing file:
diff --git a/package/m4/m4.mk b/package/m4/m4.mk
index 3a12092971..849e7f4a54 100644
--- a/package/m4/m4.mk
+++ b/package/m4/m4.mk
@@ -4,7 +4,7 @@
#
################################################################################
-M4_VERSION = 1.4.19
+M4_VERSION = 1.4.18
M4_SOURCE = m4-$(M4_VERSION).tar.xz
And another patch due to the first error (took dahdi from the "next" branch
instead of the usual)
Also the kernel config previously attached is old, please disregard.
Thanks / Merci
--
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
next prev parent reply other threads:[~2021-11-02 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 18:30 [Buildroot] [Bug 14311] New: Cannot compile dahdi (part of Asterisk) for x86 (P1mmx) bugzilla
2021-11-01 23:03 ` [Buildroot] [Bug 14311] " bugzilla
2021-11-02 19:45 ` bugzilla
2021-11-02 20:22 ` bugzilla [this message]
2021-11-04 23:18 ` bugzilla
2021-11-10 12:04 ` bugzilla
2021-11-12 2:47 ` 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-14311-163-A9QLE3mg8F@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 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.