From: Jeff Mahoney <jeffm@suse.com>
To: Sachin Durge <sachindurge@hotmail.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: HELP !!!!!!!! Cant compile the application including reiserfs .h files
Date: Thu, 16 Sep 2004 13:02:20 -0400 [thread overview]
Message-ID: <4149C71C.5010205@suse.com> (raw)
In-Reply-To: <BAY16-DAV81DdQcp0Tk00000c52@hotmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sachin Durge wrote:
| Hi ALL
| I want write a application which will read the reiserfs files even
| when the file system is not mounted directly from the Hard disk
| I tried to include the headerfiles
| reiserfs_fs_sb.h
| reiserfs_fs_i.h
| reiserfs_fs.h
| I get lots of error and warning messages
| Can any one tell me how should i proceed ......................
|
| Thanks & Regards
| Sachin
| Sachin Durge wrote:
| | Hi All
| | I am new to this list
| | I am writting a user application .
| | In my application i have included
| |
| | reiserfs_fs.h
| | reiserfs_fs_sb.h
| | reiserfs_fs_i.h
| |
| | It is giving lots of errors
| | Any one has any clue
|
| Including kernel headers in userspace programs is unsupported. There are
| examples of userspace headers available in reiserfsprogs.
|
| -Jeff
|
Asking again doesn't change the answer.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBScccLPWxlyuTD7IRAtkXAJ9azNAxZ4JvhCMB6VcqMQyBoUjQ8wCgkWan
/JPZF6wYudZwpfaVEnKSRyw=
=zEwY
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-09-16 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 14:40 HELP !!!!!!!! Cant compile the application including reiserfs .h files Sachin Durge
2004-09-16 17:02 ` Jeff Mahoney [this message]
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=4149C71C.5010205@suse.com \
--to=jeffm@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=sachindurge@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.