From: Bart Veer <bartv@redhat.com>
To: Nick.Barnes@pobox.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] tanh
Date: Wed, 21 Jun 2000 08:23:00 -0000 [thread overview]
Message-ID: <200006211523.QAA27628@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <28987.961597365@raven.ravenbrook.com>
>>>>> "Nick" == Nick Barnes <Nick.Barnes@pobox.com> writes:
Nick> Strange bug when building kernel:
Nick> -I//D/PROGRA~1/REDHAT~1/eCos/packages/language/c/libm/v1_3_1/src/double/portable-api/
Nick> -mcpu=arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes
Nick> -Winline -Wundef -Woverloaded-virtual -g -O2
Nick> -ffunction-sections -fdata-sections -fno-rtti
Nick> -fno-exceptions -fvtable-gc -finit-priority
Nick> -Wp,-MD,src/double/portable-api/s_modf.tmp -o
Nick> src/double/portable-api/language_c_libm_s_modf.o
Nick> //D/PROGRA~1/REDHAT~1/eCos/packages/language/c/libm/v1_3_1/src/double/portable-api/s_modf.c
Nick> make[1]: *** No rule to make target
Nick> `src/double/portable-api/s_tanh.c ', needed by
Nick> `libtarget.a.stamp'. Stop.
Nick> In the output pane there's a "no such character" black box
Nick> between "s_tanh.c" and "'". Cut-and-paste reveals it as a
Nick> newline character.
Nick> Tinkering with foo_build/language/c/libm/v1_3_1/makefile, I
Nick> can make this error go away by adding a space character at
Nick> the end of the line which defines the COMPILE variable.
Nick> This looks to me like a bug in make.
Almost certainly some variation of carriage return/linefeed problems.
Make sure that the relevant drives are mounted in text mode, as per
the documentation and the problems section of the FAQ at
http://sourceware.cygnus.com/ecos/
You may want to check the ecos-discuss archives at
http://sourceware.cygnus.com/ml/ecos-discuss/ for the last month or
so, looking for any related messages discussing build problems. I
believe the current recommendation is to use cygwin v1.1.2, which is
supposed to solve some of the problems. Also I believe more recent
versions of make are more tolerant of such things, but have not yet
been ported to cygwin.
Unfortunately the underlying problem is that certain operating systems
still need two characters to mark a single end-of-line in text files.
Bart Veer // eCos net maintainer
next prev parent reply other threads:[~2000-06-21 8:23 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 ` [ECOS] tanh Nick Barnes
2000-06-21 8:00 ` 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 [this message]
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=200006211523.QAA27628@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=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).