From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: Mess over open(
Date: Tue, 20 Jul 2004 10:30:23 +0100 [thread overview]
Message-ID: <200407201030.23540.dg@cowlark.com> (raw)
In-Reply-To: <20040720021951.99294.qmail@web51303.mail.yahoo.com>
On Tuesday 20 July 2004 03:19, you wrote:
> Although the open( call seems to be used everywhere
> (in around 70 source code files), it isn't defined
> anywhere. How can ELKS get past booting if a call
> isn't defined?
It might be a syscall entry point, or something else equally as weird; these
tend to be defined in horrific bits of autogenerated assembly or other
bizarre things. I'd suggest running nm on the object files and making sure
that it *really* isn't defined... apart from anything else, the linker should
bail.
(Not that I'm saying you're wrong, but I've spent so much time trying to find
weird symbols in the Linux kernel source that I know not to jump to
conclusions!)
--
+- David Given --McQ-+ "I told you to make one longer than another, and
| dg@cowlark.com | instead you have made one shorter than the other --
| (dg@tao-group.com) | the opposite." --- Sir Boyle Roche
+- www.cowlark.com --+
next prev parent reply other threads:[~2004-07-20 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 2:19 Mess over open( Tommy McCabe
2004-07-20 9:30 ` David Given [this message]
2004-07-20 15:28 ` Eduardo Pereira Habkost
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=200407201030.23540.dg@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@vger.kernel.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