public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, davej@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-git build breakage
Date: Tue, 20 Jun 2006 04:50:46 -0400	[thread overview]
Message-ID: <4497B6E6.9050605@garzik.org> (raw)
In-Reply-To: <200606201037.05610.ak@suse.de>

Andi Kleen wrote:
> On Tuesday 20 June 2006 10:17, Andrew Morton wrote:
>> On Tue, 20 Jun 2006 03:49:05 -0400
>> Jeff Garzik <jeff@garzik.org> wrote:
>>
>>> On the latest 'git pull', on x86-64 SMP 'make allmodconfig', I get the 
>>> following build breakage:
>>>
>>> 1) myri10ge: needs iowrite64_copy from -mm
>> Patch has been sent.
>>
>>> 2) forcedeth: git tree conflict, Herbert sent a patch
>>>
>>> 3) pci-gart (ouch!) link: no fix seen yet
>>>
>>> [...]
>>>    LD      init/built-in.o
>>>    LD      .tmp_vmlinux1
>>> arch/x86_64/kernel/built-in.o: In function `pci_iommu_init':
>>> arch/x86_64/kernel/pci-gart.c:619: undefined reference to `agp_amd64_init'
>>> arch/x86_64/kernel/pci-gart.c:619: undefined reference to `agp_bridge'
>>> arch/x86_64/kernel/pci-gart.c:619: undefined reference to `agp_copy_info'
>>> make: *** [.tmp_vmlinux1] Error 1
>> hm.  I could swear we fixed that multiple times, but I don't seem to be
>> able to locate the patch.
>>
>> This one, perhaps?
> 
> Is it new anyways? I don't think either me nor Dave changed anything 
> in this area yet post .17

'make allyesconfig' works on x86-64 in 2.6.17, yes.

	Jeff




  reply	other threads:[~2006-06-20  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20  7:49 2.6.17-git build breakage Jeff Garzik
2006-06-20  8:17 ` Andrew Morton
2006-06-20  8:37   ` Andi Kleen
2006-06-20  8:50     ` Jeff Garzik [this message]
2006-06-21  2:59   ` Linus Torvalds
2006-06-21  3:03     ` Andrew Morton
2006-06-21  4:02     ` Brice Goglin

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=4497B6E6.9050605@garzik.org \
    --to=jeff@garzik.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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