public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001074] New: libm.cdl: CYGPKG_LIBM_CFLAGS_ADD fix
Date: Thu, 11 Nov 2010 19:30:00 -0000	[thread overview]
Message-ID: <bug-1001074-104@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001074

           Summary: libm.cdl: CYGPKG_LIBM_CFLAGS_ADD fix
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: Patches and contributions
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: sergei.gavrikov@gmail.com
                CC: ecos-patches@ecos.sourceware.org
             Class: Advice Request


Created an attachment (id=1014)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1014)
libm.cdl patch

Due to a typo CYGPKG_LIBM_CFLAGS_ADD is not set as it was conceived.

By a chance it was catched in a thread:
http://ecos.sourceware.org/ml/ecos-discuss/2010-11/msg00021.html

More on parentheses around CDL's 'if-then-else':

egrep -r -A1 -I --include=*.cdl " \. (\\\\|\()" \
        $ECOS_REPOSITORY | less

A patch is attached.

NOTE: The libm tests were re-tested on eCos linux synthetic target, but,
perhaps, it needs more efforts for testing.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-11-11 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 19:30 bugzilla-daemon [this message]
2010-11-11 19:37 ` [Bug 1001074] " bugzilla-daemon
2010-11-11 20:33 ` bugzilla-daemon

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-1001074-104@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.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 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).