From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000596]: Package m4 fails to build
Date: Mon, 12 Feb 2007 05:49:38 -0800 [thread overview]
Message-ID: <fbcba279b9d2444d54fa2fa01f8a5cb8@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=596
======================================================================
Reported By: crafterm
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 596
Category: Other
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
======================================================================
Date Submitted: 12-11-2005 13:10 PST
Last Modified: 02-12-2007 05:49 PST
======================================================================
Summary: Package m4 fails to build
Description:
/home/crafterm/workspace/new/buildroot/build_i386/staging_dir/bin/i386-linux-uclibc-gcc
-c -DHAVE_CONFIG_H -I.. -I. -I./../lib -Os -pipe m4.c
In file included from
/home/crafterm/workspace/new/buildroot/build_i386/staging_dir/i386-linux-uclibc/sys-include/signal.h:324,
from
/home/crafterm/workspace/new/buildroot/build_i386/staging_dir/i386-linux-uclibc/sys-include/sys/signal.h:1,
from m4.c:22:
/home/crafterm/workspace/new/buildroot/build_i386/staging_dir/i386-linux-uclibc/sys-include/bits/sigstack.h:55:
error: two types specified in one empty declaration
make[2]: *** [m4.o] Error 1
make[2]: Leaving directory
`/home/crafterm/workspace/new/buildroot/build_i386/m4-1.4/src'
make[1]: *** [all] Error 1
make[1]: Leaving directory
`/home/crafterm/workspace/new/buildroot/build_i386/m4-1.4'
make: ***
[/home/crafterm/workspace/new/buildroot/build_i386/m4-1.4/src/m4] Error 2
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
12-11-05 13:10 crafterm New Issue
12-11-05 13:10 crafterm Status new => assigned
12-11-05 13:10 crafterm Assigned To => uClibc
12-29-05 03:22 vapier Status assigned => closed
12-29-05 03:22 vapier Resolution open => unable to
reproduce
02-12-07 05:49 vapier Status closed => assigned
02-12-07 05:49 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fbcba279b9d2444d54fa2fa01f8a5cb8@bugs.busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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