public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Ben Collins <bcollins@debian.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: Linux 2.4.21-pre2
Date: Fri, 20 Dec 2002 15:48:08 +0100	[thread overview]
Message-ID: <20021220144808.GF27658@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.50L.0212181721340.18764-100000@freak.distro.conectiva>

On Wed, Dec 18, 2002 at 05:22:50PM -0200, Marcelo Tosatti wrote:

>...
> Summary of changes from v2.4.21-pre1 to v2.4.21-pre2
> ============================================
>...
> Ben Collins <bcollins@debian.org>:
>   o Linux1394 Firewire
>...

The changes to drivers/ieee1394/Makefile broke the compilation at least 
when compiling the ieee1394 code statically into the kernel:

1. Nothing gets built in drivers/ieee1394.

2. The final linking fails with the following error:

<--  snip  -->

...
        -o vmlinux
ld: cannot open drivers/ieee1394/ieee1394drv.o: No such file or directory
make: *** [vmlinux] Error 1

<--  snip  -->


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2002-12-20 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18 19:22 Linux 2.4.21-pre2 Marcelo Tosatti
2002-12-18 23:31 ` Christoph Hellwig
2002-12-19  1:16   ` Alan Cox
2002-12-18 23:33 ` Eyal Lebedinsky
2002-12-18 23:49 ` Linux 2.4.21-pre2 - unresolved Eyal Lebedinsky
2002-12-20 14:48 ` Adrian Bunk [this message]
2002-12-20 14:57   ` Linux 2.4.21-pre2 Christoph Hellwig
2002-12-20 15:50   ` Ben Collins
  -- strict thread matches above, loose matches on Subject: below --
2002-12-19  6:49 Mikael Starvik

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=20021220144808.GF27658@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=marcelo@conectiva.com.br \
    /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