From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Ignore earlier dumb question, but here is another
Date: Mon, 08 Jan 2001 15:10:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010108175535.00aefc20@larwe.com> (raw)
I think I'm on crack. It took about three hours for my messages to get back
to me via the list and when they did, I immediately had a memory jolt that
told me the correct switch to use. I've recompiled eCos with -fpack-struct
and all is seemingly well. However I worry that the OS might not have been
tested in this configuration. Any known caveats?
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
next reply other threads:[~2001-01-08 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 15:10 Lewin A.R.W. Edwards [this message]
2001-01-08 16:28 ` Gary Thomas
2001-01-08 16:37 ` Lewin A.R.W. Edwards
2001-01-09 5:53 ` Gary Thomas
2001-01-08 16:29 ` Gary Thomas
2001-01-09 0:21 ` Jesper Skov
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=4.3.2.7.2.20010108175535.00aefc20@larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@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).