public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1002026] uSTL does not build
Date: Mon, 10 Nov 2014 08:36:00 -0000	[thread overview]
Message-ID: <bug-1002026-13-2gRkZPz8J4@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1002026-13@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002026

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |john@dallaway.org.uk
           Assignee|unassigned@bugs.ecos.source |john@dallaway.org.uk
                   |ware.org                    |

--- Comment #2 from John Dallaway <john@dallaway.org.uk> ---
Hi Ilija

By inspection, it looks like we need to #include "strmsize.h" from mostream.h
(as for mistream.h). If you #include "strmsize.h", does that resolve the build
problem?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-11-10  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-09 21:16 [Bug 1002026] New: " bugzilla-daemon
2014-11-09 21:18 ` [Bug 1002026] " bugzilla-daemon
2014-11-10  8:36 ` bugzilla-daemon [this message]
2014-11-10 11:39 ` bugzilla-daemon
2014-11-17 11:57 ` bugzilla-daemon
2014-11-29 12:51 ` bugzilla-daemon
2014-12-01  0:02 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2014-11-09 21:16 [Bug 1002026] New: " bugzilla-daemon
2014-11-10  8:36 ` [Bug 1002026] " 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-1002026-13-2gRkZPz8J4@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@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).