Re: Linking

Re: Linking

[Keith Owens]

On Mon, 18 Jun 2001 09:29:51 +0530, 
"Anil Kumar" <anilk@subexgroup.com> wrote:
>How do i link the kernel functions such as test_ans_set functions with my
>applications.

You don't.  The kernel use the kernel functions, user space
applications use glibc functions, the two do not mix.

Linking

[Anil Kumar]

How do i link the kernel functions such as test_ans_set functions with my
applications.
thanks,
anil

Linking

[Viswesh S]

[-- Attachment #1: Type: text/plain, Size: 3708 bytes --]

Hi,
I am quite new to grub2 anf I find some issue in make of grub2
I modify the hello module by adding a new file a.c, with a function test() in it.
I call the function test from hello entry point - grub_cmd_hello()
When I do a make, I get the error that 
test in hello is not defined
make: *** [moddep.lst] Error 1

I have modified the conf/common.mk accordingly as shown below.
# For hello.mod.
hello_mod_SOURCES = hello/hello.c hello/a.c
CLEANFILES += hello.mod mod-hello.o mod-hello.c pre-hello.o hello_mod-hello_hello.o hello_mod-hello_a.o und-hello.lst
ifneq ($(hello_mod_EXPORTS),no)
CLEANFILES += def-hello.lst
DEFSYMFILES += def-hello.lst
endif
MOSTLYCLEANFILES += hello_mod-hello_hello.d  hello_mod-hello_a.d
UNDSYMFILES += und-hello.lst
hello.mod: pre-hello.o mod-hello.o
        -rm -f $@
        $(TARGET_CC) $(hello_mod_LDFLAGS) $(TARGET_LDFLAGS) -Wl,-r,-d -o $@ $^
        $(STRIP) --strip-unneeded -K grub_mod_init -K grub_mod_fini -R .note -R .comment $@
pre-hello.o: $(hello_mod_DEPENDENCIES) hello_mod-hello_hello.o hello_mod-hello_a.o
        -rm -f $@
        $(TARGET_CC) $(hello_mod_LDFLAGS) $(TARGET_LDFLAGS) -Wl,-r,-d -o $@ hello_mod-hello_hello.o
mod-hello.o: mod-hello.c
        $(TARGET_CC) $(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -c -o $@ $<
mod-hello.c: moddep.lst genmodsrc.sh
        sh $(srcdir)/genmodsrc.sh 'hello' $< > $@ || (rm -f $@; exit 1)
ifneq ($(hello_mod_EXPORTS),no)
def-hello.lst: pre-hello.o
        $(NM) -g --defined-only -P -p $< | sed 's/^\([^ ]*\).*/\1 hello/' > $@
endif
und-hello.lst: pre-hello.o
        echo 'hello' > $@
        $(NM) -u -P -p $< | cut -f1 -d' ' >> $@
hello_mod-hello_hello.o: hello/hello.c $(hello/hello.c_DEPENDENCIES)
        $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS)  $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -MD -c -o $@ $<
-include hello_mod-hello_hello.d
hello_mod-hello_a.o: hello/a.c $(hello/a.c_DEPENDENCIES)
        $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS)  $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -MD -c -o $@ $<
-include hello_mod-hello_a.d

CLEANFILES += cmd-hello_mod-hello_hello.lst fs-hello_mod-hello_hello.lst
COMMANDFILES += cmd-hello_mod-hello_hello.lst
FSFILES += fs-hello_mod-hello_hello.lst
cmd-hello_mod-hello_hello.lst: hello/hello.c $(hello/hello.c_DEPENDENCIES) gencmdlist.sh
        set -e;           $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh $(srcdir)/gencmdlist.sh hello > $@ || (rm -f $@; exit 1)
cmd-hello_mod-hello_a.lst: hello/a.c $(hello/a.c_DEPENDENCIES) gencmdlist.sh
        set -e;           $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh $(srcdir)/gencmdlist.sh hello > $@ || (rm -f $@; exit 1)

fs-hello_mod-hello_hello.lst: hello/hello.c $(hello/hello.c_DEPENDENCIES) genfslist.sh
        set -e;           $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh $(srcdir)/genfslist.sh hello > $@ || (rm -f $@; exit 1)
fs-hello_mod-hello_a.lst: hello/a.c $(hello/a.c_DEPENDENCIES) genfslist.sh
        set -e;           $(TARGET_CC) -Ihello -I$(srcdir)/hello $(TARGET_CPPFLAGS) $(TARGET_CFLAGS) $(hello_mod_CFLAGS) -E $<    | sh $(srcdir)/genfslist.sh hello > $@ || (rm -f $@; exit 1)

Could anyone let me know whether I need to do anything more.
Viswesh


      Explore your hobbies and interests. Go to http://in.promos.yahoo.com/groups/

[-- Attachment #2: Type: text/html, Size: 6046 bytes --]

Re: Linking

[Pavel Roskin]

Quoting Viswesh S <viswesh_vichu@yahoo.com>:

> I have modified the conf/common.mk accordingly as shown below.

It's a generated file.  Please modify conf/common.rmk instead and run  
autogen.sh.

-- 
Regards,
Pavel Roskin

Re: Linking

[Viswesh S]

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

Hi Pavel,
Could you please attach the modified file ?
Viswesh



----- Original Message ----
From: Pavel Roskin <proski@gnu.org>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 11:05:49 AM
Subject: Re: Linking

Quoting Viswesh S <viswesh_vichu@yahoo.com>:

> I have modified the conf/common.mk accordingly as shown below.

It's a generated file.  Please modify conf/common.rmk instead and run  
autogen.sh.

-- 
Regards,
Pavel Roskin


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



      Explore your hobbies and interests. Go to http://in.promos.yahoo.com/groups/

[-- Attachment #2: Type: text/html, Size: 1524 bytes --]

Re: Linking

[Pavel Roskin]

Quoting Viswesh S <viswesh_vichu@yahoo.com>:

> Hi Pavel,
> Could you please attach the modified file ?
> Viswesh

No, I'm just giving you an idea what you may be doing wrong.

-- 
Regards,
Pavel Roskin

Re: Linking

[Viswesh S]

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

Hi,
So if I add a module or add a new command,which are the files which I should modify in general and which all gets generated automatically.
Is this somewhere documented ?
Why is it that hello command is put in a separate directory, while lspci is put inside the commands directory.
Is there a specific reason for this.
Viswesh



----- Original Message ----
From: Pavel Roskin <proski@gnu.org>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 11:59:21 AM
Subject: Re: Linking

Quoting Viswesh S <viswesh_vichu@yahoo.com>:

> Hi Pavel,
> Could you please attach the modified file ?
> Viswesh

No, I'm just giving you an idea what you may be doing wrong.

-- 
Regards,
Pavel Roskin


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



      Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/

[-- Attachment #2: Type: text/html, Size: 1846 bytes --]

Re: Linking

[Viswesh S]

[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]

The reason for hello to be put in a directory because it is a module and not a simple command.Understood myself



----- Original Message ----
From: Viswesh S <viswesh_vichu@yahoo.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Sent: Friday, 25 July, 2008 3:44:48 PM
Subject: Re: Linking


Hi,
 
So if I add a module or add a new command,which are the files which I should modify in general and which all gets generated automatically.
 
Is this somewhere documented ?
 
Why is it that hello command is put in a separate directory, while lspci is put inside the commands directory.
 
Is there a specific reason for this.
 
 
Viswesh



----- Original Message ----
From: Pavel Roskin <proski@gnu.org>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 11:59:21 AM
Subject: Re: Linking

Quoting Viswesh S <viswesh_vichu@yahoo.com>:

> Hi Pavel,
> Could you please attach the modified file ?
> Viswesh

No, I'm just giving you an idea what you may be doing wrong.

-- 
Regards,
Pavel Roskin


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

________________________________
Bring your gang together. Do your thing. Find your favourite Yahoo! Group.


      Forgot the famous last words? Access your message archive online at http://in.webmessenger.yahoo.com/

[-- Attachment #2: Type: text/html, Size: 2726 bytes --]

Re: Linking

[Colin D Bennett]

On Fri, 25 Jul 2008 03:22:57 -0700 (PDT)
Viswesh S <viswesh_vichu@yahoo.com> wrote:

> The reason for hello to be put in a directory because it is a module
> and not a simple command.Understood myself

Actually, no.  Every C source file in the 'commands' directory is
currently a module itself.

I think the reason that 'hello.mod' is separated out is to make it
easier to see that there is only one source file as part of 'hello.mod'.

Regards,
Colin


> ----- Original Message ----
> From: Viswesh S <viswesh_vichu@yahoo.com>
> To: The development of GRUB 2 <grub-devel@gnu.org>
> Sent: Friday, 25 July, 2008 3:44:48 PM
> Subject: Re: Linking
> 
> 
> Hi,
>  
> So if I add a module or add a new command,which are the files which I
> should modify in general and which all gets generated automatically. 
> Is this somewhere documented ?
>  
> Why is it that hello command is put in a separate directory, while
> lspci is put inside the commands directory. 
> Is there a specific reason for this.
>  
>  
> Viswesh
> 
> 
> 
> ----- Original Message ----
> From: Pavel Roskin <proski@gnu.org>
> To: grub-devel@gnu.org
> Sent: Friday, 25 July, 2008 11:59:21 AM
> Subject: Re: Linking
> 
> Quoting Viswesh S <viswesh_vichu@yahoo.com>:
> 
> > Hi Pavel,
> > Could you please attach the modified file ?
> > Viswesh
> 
> No, I'm just giving you an idea what you may be doing wrong.
> 

Re: Linking

[Viswesh S]

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

Suppose I am adding a new command,so should I create a new file for that command and modify only the command,rmk accordingly?
All the other files get autogenerated by autogen.sh ?
Is this sufficient ?
Viswesh



----- Original Message ----
From: Colin D Bennett <colin@gibibit.com>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 7:31:28 PM
Subject: Re: Linking

On Fri, 25 Jul 2008 03:22:57 -0700 (PDT)
Viswesh S <viswesh_vichu@yahoo.com> wrote:

> The reason for hello to be put in a directory because it is a module
> and not a simple command.Understood myself

Actually, no.  Every C source file in the 'commands' directory is
currently a module itself.

I think the reason that 'hello.mod' is separated out is to make it
easier to see that there is only one source file as part of 'hello.mod'.

Regards,
Colin


> ----- Original Message ----
> From: Viswesh S <viswesh_vichu@yahoo.com>
> To: The development of GRUB 2 <grub-devel@gnu.org>
> Sent: Friday, 25 July, 2008 3:44:48 PM
> Subject: Re: Linking
> 
> 
> Hi,
>  
> So if I add a module or add a new command,which are the files which I
> should modify in general and which all gets generated automatically. 
> Is this somewhere documented ?
>  
> Why is it that hello command is put in a separate directory, while
> lspci is put inside the commands directory. 
> Is there a specific reason for this.
>  
>  
> Viswesh
> 
> 
> 
> ----- Original Message ----
> From: Pavel Roskin <proski@gnu.org>
> To: grub-devel@gnu.org
> Sent: Friday, 25 July, 2008 11:59:21 AM
> Subject: Re: Linking
> 
> Quoting Viswesh S <viswesh_vichu@yahoo.com>:
> 
> > Hi Pavel,
> > Could you please attach the modified file ?
> > Viswesh
> 
> No, I'm just giving you an idea what you may be doing wrong.
> 


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



      Share files, take polls, and make new friends - all under one roof. Go to http://in.promos.yahoo.com/groups/

[-- Attachment #2: Type: text/html, Size: 3546 bytes --]

Re: Linking

[Colin D Bennett]

On Fri, 25 Jul 2008 07:33:41 -0700 (PDT)
Viswesh S <viswesh_vichu@yahoo.com> wrote:

> Suppose I am adding a new command,so should I create a new file for
> that command and modify only the command,rmk accordingly? All the
> other files get autogenerated by autogen.sh ? Is this sufficient ?
> Viswesh

Yes.  Actually when you run 'make', the conf/*.mk files are regenerated
from the conf/*.rmk files if necessary, so you don't need to re-run
autogen.sh after changing .rmk files.

I was puzzled with the conf/* files at first too, and though I had to
change both, and after looking at the .mk files, I was saddened.
However, now that I know to change only the .rmk files, life is happy
and the build system is actually easy to work with.

Regards,
Colin


> ----- Original Message ----
> From: Colin D Bennett <colin@gibibit.com>
> To: grub-devel@gnu.org
> Sent: Friday, 25 July, 2008 7:31:28 PM
> Subject: Re: Linking
> 
> On Fri, 25 Jul 2008 03:22:57 -0700 (PDT)
> Viswesh S <viswesh_vichu@yahoo.com> wrote:
> 
> > The reason for hello to be put in a directory because it is a module
> > and not a simple command.Understood myself
> 
> Actually, no.  Every C source file in the 'commands' directory is
> currently a module itself.
> 
> I think the reason that 'hello.mod' is separated out is to make it
> easier to see that there is only one source file as part of
> 'hello.mod'.
> 
> Regards,
> Colin
> 
> 
> > ----- Original Message ----
> > From: Viswesh S <viswesh_vichu@yahoo.com>
> > To: The development of GRUB 2 <grub-devel@gnu.org>
> > Sent: Friday, 25 July, 2008 3:44:48 PM
> > Subject: Re: Linking
> > 
> > 
> > Hi,
> >  
> > So if I add a module or add a new command,which are the files which
> > I should modify in general and which all gets generated
> > automatically. Is this somewhere documented ?
> >  
> > Why is it that hello command is put in a separate directory, while
> > lspci is put inside the commands directory. 
> > Is there a specific reason for this.
> >  
> >  
> > Viswesh
> > 
> > 
> > 
> > ----- Original Message ----
> > From: Pavel Roskin <proski@gnu.org>
> > To: grub-devel@gnu.org
> > Sent: Friday, 25 July, 2008 11:59:21 AM
> > Subject: Re: Linking
> > 
> > Quoting Viswesh S <viswesh_vichu@yahoo.com>:
> > 
> > > Hi Pavel,
> > > Could you please attach the modified file ?
> > > Viswesh
> > 
> > No, I'm just giving you an idea what you may be doing wrong.
> > 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
> 
> 
> 
>       Share files, take polls, and make new friends - all under one
> roof. Go to http://in.promos.yahoo.com/groups/