From: "Lee Ho" <i@flyduck.com>
To: <linux-kernel@vger.kernel.org>
Cc: "Collins, Tom" <Tom.Collins@Surgient.com>
Subject: Re: Multiple file module build problems
Date: Thu, 1 Mar 2001 02:59:54 +0900 [thread overview]
Message-ID: <021b01c0a1b0$421eba80$2502a8c0@flyduck.flyduck.com> (raw)
It seems that linker tried to build executable file.
When building multiple module source into one module object file,
ld with '-r' option is used.
ld -r -o scharmod.o schar.o procschar.o
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Lee, Ho. Software Engineer, Embedded Linux Dep, LinuxOne
Mail : flyduck@linuxone.co.kr (work), i@flyduck.com (personal)
Homepage : http://flyduck.com, http://linuxkernel.to
Collins, Tom Wrote:
I am trying to build a multiple-file kernel module, and am
having some difficulty. It seems that the linker is trying
to build and executable.
The link command is:
ld -m elf_i386 -o scharmod.o schar.o procschar.o
next reply other threads:[~2001-03-01 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 17:59 Lee Ho [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-28 18:23 Multiple file module build problems Collins, Tom
2001-02-28 17:34 Collins, Tom
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='021b01c0a1b0$421eba80$2502a8c0@flyduck.flyduck.com' \
--to=i@flyduck.com \
--cc=Tom.Collins@Surgient.com \
--cc=linux-kernel@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