linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org,
	Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: 2.6.0-test2-mm1 and the mysterious dissapearing penguin..
Date: Tue, 29 Jul 2003 21:03:40 +0200	[thread overview]
Message-ID: <20030729190340.GA5791@mars.ravnborg.org> (raw)
In-Reply-To: <200307281759.h6SHx75k004260@turing-police.cc.vt.edu>

On Mon, Jul 28, 2003 at 01:59:07PM -0400, Valdis.Kletnieks@vt.edu wrote:
>   LD      arch/i386/kernel/built-in.o
> ./scripts/pnmtologo -t mono -n logo_linux_mono -o drivers/video/logo/logo_linux_mono.c drivers/video/logo/logo_linux_mono.pbm
>   CC      drivers/video/logo/logo_linux_mono.o
> ./scripts/pnmtologo -t vga16 -n logo_linux_vga16 -o drivers/video/logo/logo_linux_vga16.c drivers/video/logo/logo_linux_vga16.ppm
>   CC      drivers/video/logo/logo_linux_vga16.o
> ./scripts/pnmtologo -t clut224 -n logo_linux_clut224 -o drivers/video/logo/logo_linux_clut224.c drivers/video/logo/logo_linux_clut224.ppm
>   CC      drivers/video/logo/logo_linux_clut224.o
>   LD      drivers/video/logo/built-in.o
>   LD      drivers/video/built-in.o
>   LD      drivers/built-in.o
>   GEN     .version
>   CHK     include/linux/compile.h
> 
> Looks like a dependency issue?  Why would they get build THIS time and apparently
> not the first time around?

When building the logo stuff there is some dependencies missing in the
Makefile which causes what you see.
Kai G. has a fix pending in his tree for this, so expect that
bit to be sovled pretty soon.

	Sam

      reply	other threads:[~2003-07-29 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 17:59 2.6.0-test2-mm1 and the mysterious dissapearing penguin Valdis.Kletnieks
2003-07-29 19:03 ` Sam Ravnborg [this message]

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=20030729190340.GA5791@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --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;
as well as URLs for NNTP newsgroup(s).