From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 71] New: ./wchar.h:41:12: error: empty filename in #include
Date: Sun, 25 Jan 2009 05:58:41 +0000 (UTC) [thread overview]
Message-ID: <bug-71-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=71
Host: Gentoo AMD64
Target: ARM
Summary: ./wchar.h:41:12: error: empty filename in #include
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: paul.jones at iwtech.com.au
CC: buildroot at uclibc.org
Estimated Hours: 0.0
# Work around problem of missing syslimits.h
if [ ! -f
/home/paul.jones/dev/buildroot-2009.02-rc2/project_build_arm/uclibc/root/usr/lib/gcc/arm-linux-uclibc/4.3.2/include-fixed/syslimits.h
]; then \
echo "warning: working around missing syslimits.h"; \
cp -f
/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/staging_dir/lib/gcc/arm-linux-uclibc/4.3.2/include-fixed/syslimits.h
\
/home/paul.jones/dev/buildroot-2009.02-rc2/project_build_arm/uclibc/root/usr/lib/gcc/arm-linux-uclibc/4.3.2/include-fixed/;
\
fi
# Make sure we have 'cc'.
if [ ! -e
/home/paul.jones/dev/buildroot-2009.02-rc2/project_build_arm/uclibc/root/usr/bin/cc
]; then \
ln -snf gcc
/home/paul.jones/dev/buildroot-2009.02-rc2/project_build_arm/uclibc/root/usr/bin/cc;
\
fi
# These are in /lib, so...
#rm -rf
/home/paul.jones/dev/buildroot-2009.02-rc2/project_build_arm/uclibc/root/usr/lib/libgcc_s*.so*
touch -c
/home/paul.jones/dev/buildroot-2009.02-rc2/project_build_arm/uclibc/root/usr/bin/gcc
/usr/bin/make -j1 -C
/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9
make[1]: Entering directory
`/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9'
Making all in lib
make[2]: Entering directory
`/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9/lib'
/usr/bin/make all-am
make[3]: Entering directory
`/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9/lib'
/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc
-Os
-I/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/staging_dir/usr/include
-I/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/staging_dir/include
--sysroot=/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/staging_dir/
-isysroot /home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/staging_dir
-mtune=arm920t -I. -g -O2 -c allocsa.c
In file included from ./stdint.h:87,
from
///home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/staging_dir/usr/include/stdlib.h:860,
from ./stdlib.h:44,
from allocsa.h:24,
from allocsa.c:22:
./wchar.h:41:12: error: empty filename in #include
make[3]: *** [allocsa.o] Error 1
make[3]: Leaving directory
`/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9'
make: ***
[/home/paul.jones/dev/buildroot-2009.02-rc2/build_arm/coreutils-6.9/src/vdir]
Error 2
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-01-25 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 5:58 bugzilla at busybox.net [this message]
2009-02-14 17:44 ` [Buildroot] [Bug 71] ./wchar.h:41:12: error: empty filename in #include bugzilla at busybox.net
2009-02-14 17:47 ` bugzilla at busybox.net
2009-03-02 19:55 ` bugzilla at busybox.net
2009-03-04 0:58 ` bugzilla at busybox.net
2009-03-04 0:59 ` bugzilla at busybox.net
2009-03-04 1:01 ` bugzilla at busybox.net
2009-03-04 10:38 ` bugzilla at busybox.net
2009-03-04 11:01 ` bugzilla at busybox.net
2009-03-04 11:15 ` bugzilla at busybox.net
2009-03-11 10:32 ` bugzilla at busybox.net
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-71-163@https.bugs.busybox.net/ \
--to=bugzilla@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