linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Richard Danter <richard.danter@ntlworld.com>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Simple module, but won't build
Date: Tue, 04 May 2004 23:46:18 +0200	[thread overview]
Message-ID: <20040504214623.49B32C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 04 May 2004 23:15:08 +0200." <20040504211508.GA2510@mars.ravnborg.org>


In message <20040504211508.GA2510@mars.ravnborg.org> you wrote:
>
> make -C $KERNELSRCDIR SUBDIRS=$PWD modules
>
> This should give you the correct gcc options.
>
> [Speaking of vanilla kernel, not knowing ELDK in this respect].

Same for ELDK. We use a standard Linux kernel,  too  [just  some  bug
fixes and extensions included].

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"It's when they say 2 + 2 = 5 that I begin to argue."    - Eric Pepke

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-04 21:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 18:03 Simple module, but won't build Richard Danter
2004-05-04 19:10 ` Wolfgang Denk
2004-05-04 19:46   ` Richard Danter
2004-05-04 20:19     ` Wolfgang Denk
2004-05-04 21:15     ` Sam Ravnborg
2004-05-04 21:46       ` Wolfgang Denk [this message]
2004-05-04 23:50         ` Next steps Brian Hawley
2004-05-05 12:19           ` Bob White
2004-05-04 19:38 ` Simple module, but won't build Joshua Lamorie
  -- strict thread matches above, loose matches on Subject: below --
2006-08-31 22:55 Steven Kaiser
2006-09-01  6:35 ` Josu Onandia
2006-09-06 19:29 Steven Kaiser

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=20040504214623.49B32C109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=richard.danter@ntlworld.com \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).