public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Hiroki Kaminaga <kaminaga@sm.sony.co.jp>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: build error on Linux-2.6.15-rc4-omap1
Date: Tue, 3 Jan 2006 11:04:07 -0800	[thread overview]
Message-ID: <20060103190406.GP6034@atomide.com> (raw)
In-Reply-To: <20051221.112803.112628154.kaminaga@sm.sony.co.jp>

* Hiroki Kaminaga <kaminaga@sm.sony.co.jp> [051220 18:34]:
> > > make[2]: *** No rule to make target `arch/arm/mach-omap1/pm.o', needed by `arch/arm/mach-omap1/built-in.o'.  Stop.
> > > make[1]: *** [arch/arm/mach-omap1] Error 2
> > >..
> > > I'm currently doing work-around by making symbolic link from plat-omap/pm.c.
> > > 
> > > Anyone have same build error?
> > 
> > Yes, I now remember I just worked around it and forgot to send a patch 
> > here.  I assume pm.c is being moved from plat-omap to mach-omap1 (and a 
> > future version is destined for mach-omap2), so a patch to move the 
> > current file to mach-omap1 is needed?

Yes, the pm.c is working for omap1 but not for omap2. And they will be
somewhat different.
 
> I'm assuming pm.c (and sleep.S) is same file, and I'm using symbolic link
> to work around, so patch just for moving is not necessary. (at least for me...)
> I hope it'll be fixed in rc6 (or later) in omap big patch.

Hmmm, this should be fixed in the current git tree. At least omap1 with
CONFIG_PM builds fine for me.

Regards,

Tony

  reply	other threads:[~2006-01-03 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21  1:25 build error on Linux-2.6.15-rc4-omap1 Hiroki Kaminaga
2005-12-21  2:06 ` Todd Poynor
2005-12-21  2:28   ` Hiroki Kaminaga
2006-01-03 19:04     ` Tony Lindgren [this message]
2006-01-11  4:12   ` Hiroki Kaminaga

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=20060103190406.GP6034@atomide.com \
    --to=tony@atomide.com \
    --cc=kaminaga@sm.sony.co.jp \
    --cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox