From: Jeff Garzik <jeff@garzik.org>
To: Paul Fulghum <paulkf@microgate.com>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
khc@pm.waw.pl, linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@osdl.org>
Subject: Re: [PATCH] Re: linux-2.6.19-rc5-g088406bc build #120 failed
Date: Mon, 13 Nov 2006 10:14:56 -0500 [thread overview]
Message-ID: <45588BF0.3000100@garzik.org> (raw)
In-Reply-To: <45588895.7010501@microgate.com>
Paul Fulghum wrote:
> Jeff Garzik wrote:
>> Toralf Förster wrote:
>>
>>> Hello,
>>>
>>> the build with the attached .config failed, make ends with:
>>> ... UPD include/linux/compile.h
>>> CC init/version.o
>>> LD init/built-in.o
>>> LD .tmp_vmlinux1
>>> drivers/built-in.o: In function `hdlcdev_open':
>>> synclink.c:(.text+0x650d5): undefined reference to `hdlc_open'
>>> synclink.c:(.text+0x6510d): undefined reference to `hdlc_open'
>>> ...
>>> synclink_cs.c:(.text+0x7aece): undefined reference to `hdlc_ioctl'
>>> drivers/built-in.o: In function `hdlcdev_init':
>>> synclink_cs.c:(.text+0x7b336): undefined reference to `alloc_hdlcdev'
>>> drivers/built-in.o: In function `hdlcdev_exit':
>>> synclink_cs.c:(.text+0x7b434): undefined reference to
>>> `unregister_hdlc_device'
>>> make: *** [.tmp_vmlinux1] Error 1
>>
>>
>> Does this patch work for you?
>>
>> Jeff
>
> No, this patch is not acceptable.
>
> This has been beaten to death in previous threads.
> The problem is a mismatch in your kernel config between
> generic hdlc (M) and synclink (Y).
>
> synclink drivers can *optionally* support generic hdlc.
> You *must* be able to build synclink driver without generic hdlc.
> Because of this you *can't* just put in the generic hdlc dependency.
>
> Several alternative patches were posted (3 or 4 months) ago.
> No particular patch won the approval of all kernel developers,
> so nothing was done.
The existing build breakage is unacceptable too. It's this bogosity
#ifdef CONFIG_HDLC_MODULE
#define CONFIG_HDLC 1
#endif
which directly causes the build breakage.
Unless someone fixes it The Right Way, my patch seems like the best we
can do. People who complain "you must be able to build without hdlc"
should step up and make it so. Currently, it is not so.
Jeff
next prev parent reply other threads:[~2006-11-13 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 8:43 linux-2.6.19-rc5-g088406bc build #120 failed Toralf Förster
2006-11-13 14:49 ` [PATCH] " Jeff Garzik
2006-11-13 15:00 ` Paul Fulghum
2006-11-13 15:14 ` Jeff Garzik [this message]
2006-11-13 15:37 ` Paul Fulghum
2006-11-13 18:33 ` Krzysztof Halasa
2006-11-13 18:54 ` Paul Fulghum
2006-11-13 20:49 ` Krzysztof Halasa
2006-11-13 21:40 ` Paul Fulghum
2006-11-13 23:05 ` Krzysztof Halasa
2006-11-13 23:10 ` Paul Fulghum
2006-11-14 0:07 ` Krzysztof Halasa
2006-11-14 1:08 ` Paul Fulghum
2006-11-14 14:25 ` Krzysztof Halasa
2006-11-13 23:13 ` Randy Dunlap
2006-11-13 23:06 ` Andrew Morton
2006-11-13 23:15 ` Paul Fulghum
2006-11-14 0:00 ` Daniel Barkalow
2006-11-13 21:36 ` Toralf Förster
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=45588BF0.3000100@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=toralf.foerster@gmx.de \
/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