From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: problems compiling NTFS on GRUB2
Date: Fri, 13 Aug 2004 12:25:07 +0200 [thread overview]
Message-ID: <87vffnmj24.fsf@marco.marco-g.com> (raw)
In-Reply-To: <BAY22-F22R881Np7vXe0003b030@hotmail.com> (lode leroy's message of "Fri, 13 Aug 2004 08:59:05 +0200")
"lode leroy" <lode_leroy@hotmail.com> writes:
>>How do you compile and link fs/ntfs.c
>
> I modified i386-pc.mk :%s/minix/ntfs/g
Ok. But I assume you have to add something in order to link it to the
library?
>>Can you show a backtrace of the crash?
>
> see attached mkimg.log
>
> I noticed that there are some external unresolved link symbols...
> ie. libntfs uses fprintf, calloc, mbrtowc, memcpy etc...
Oh, that sucks.
> I suppose these will need to be defined in ntfs.o
> and libntfs.a is compiled for linux, it will need to be compiled
> for grub2. How do I do this? I suppose --no-stdlib
> and make equivalents for <stdlib.h>, <ctype.h> etc....
Well, in GRUB we have functions like grub_memcpy, etc.
But the best way to implement NTFS is by writing it yourself. It is
on my todo already, or do you want to do this? I don't think it is
easy and clean to use libntfs. Another thing to consider is its size.
--
Marco
next prev parent reply other threads:[~2004-08-13 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 6:59 problems compiling NTFS on GRUB2 lode leroy
2004-08-13 10:25 ` Marco Gerards [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 9:22 lode leroy
2004-08-16 9:44 ` Marco Gerards
2004-08-16 10:35 ` Yoshinori K. Okuji
2004-08-12 12:43 lode leroy
2004-08-12 13:02 ` Marco Gerards
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=87vffnmj24.fsf@marco.marco-g.com \
--to=metgerards@student.han.nl \
--cc=grub-devel@gnu.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 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.