From: Nick Barnes <Nick.Barnes@pobox.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] tanh
Date: Wed, 21 Jun 2000 07:22:00 -0000 [thread overview]
Message-ID: <28987.961597365@raven.ravenbrook.com> (raw)
In-Reply-To: <200006211302.OAA25708@sheesh.cygnus.co.uk>
Strange bug when building kernel:
-I//D/PROGRA~1/REDHAT~1/eCos/packages/language/c/libm/v1_3_1/src/double/portable-api/ -mcpu=arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -Wp,-MD,src/double/portable-api/s_modf.tmp -o src/double/portable-api/language_c_libm_s_modf.o //D/PROGRA~1/REDHAT~1/eCos/packages/language/c/libm/v1_3_1/src/double/portable-api/s_modf.c
make[1]: *** No rule to make target `src/double/portable-api/s_tanh.c
', needed by `libtarget.a.stamp'. Stop.
In the output pane there's a "no such character" black box between
"s_tanh.c" and "'". Cut-and-paste reveals it as a newline character.
Tinkering with foo_build/language/c/libm/v1_3_1/makefile, I can make
this error go away by adding a space character at the end of the line
which defines the COMPILE variable.
This looks to me like a bug in make.
Nick Barnes
--
FreeBSD 2.2.8-RELEASE: up 22 days, 22:44
next prev parent reply other threads:[~2000-06-21 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-21 5:34 [ECOS] pkgconf/hal.h missing Nick Barnes
2000-06-21 6:02 ` Bart Veer
2000-06-21 7:22 ` Nick Barnes [this message]
2000-06-21 8:00 ` [ECOS] tanh Hugo 'NOx' Tyson
2000-06-21 8:16 ` Nick Barnes
2001-09-05 0:10 ` Hugo 'NOx' Tyson
2000-06-21 8:23 ` Bart Veer
2000-06-21 6:52 ` [ECOS] pkgconf/hal.h missing John Dallaway
2000-06-21 7:05 ` Nick Barnes
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=28987.961597365@raven.ravenbrook.com \
--to=nick.barnes@pobox.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).