public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-bugs@sources.redhat.com
Subject: [Bug 1000207] problem compiling latest snapshot on freebsd 5.4
Date: Fri, 24 Feb 2006 10:15:00 -0000 [thread overview]
Message-ID: <20060224084944.5A5F1DC8054@snape.ecoscentric.com> (raw)
http://bugzilla.ecoscentric.com/show_bug.cgi?id=1000207
andrew.lunn@ascom.ch changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
------- Additional Comments From andrew.lunn@ascom.ch 2006-02-24 08:49 -------
See the discussion thread:
http://ecos.sourceware.org/ml/ecos-discuss/2006-02/msg00274.html
At the end i propose a "shot in the dark" patch which works for David, but
required verifying by a C++ programmer if this is the real solution.
> Index: eCosSocket.h
> > ===================================================================
> > RCS file: /cvs/ecos/ecos/host/tools/Utils/common/eCosSocket.h,v
> > retrieving revision 1.2
> > diff -u -r1.2 eCosSocket.h
> > --- eCosSocket.h 19 Sep 2000 05:53:51 -0000 1.2
> > +++ eCosSocket.h 23 Feb 2006 18:09:34 -0000
> > @@ -75,6 +75,7 @@
> >
> > class CeCosSocket {
> > public:
> > + friend class CeCosSerial;
> > static const String GetHostByName(LPCTSTR pszHost);
> >
> > // These functions must be called before any other operation is carried
+out:
--
Configure bugmail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
next reply other threads:[~2006-02-24 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 10:15 bugzilla-daemon [this message]
2006-02-24 11:32 bugzilla-daemon
2006-03-01 9:20 bugzilla-daemon
2006-03-29 4:15 bugzilla-daemon
2006-03-29 9:05 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=20060224084944.5A5F1DC8054@snape.ecoscentric.com \
--to=bugzilla-daemon@ecoscentric.com \
--cc=ecos-bugs@sources.redhat.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).