From: Hannes Reinecke <hare@suse.de>
To: ZX <jencce.kernel@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: linux-next: Tree for May 1
Date: Thu, 02 May 2013 09:46:05 +0200 [thread overview]
Message-ID: <518219BD.9090208@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1305021529430.23933@M2420>
On 05/02/2013 09:37 AM, ZX wrote:
>
>
> On Wed, 1 May 2013, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Please do not add any v3.11 destined work to your linux-next included
>> branches until after v3.10-rc1 is released.
>>
>> Changes since 20130430:
>>
>> The nfsd tree lost its build failure.
>>
>> The xfs tree lost its build failure.
>>
>> The vfs tree gained conflicts against Linus' and the powerpc trees and
>> gained a build failure for which I applied a merge fix patch.
>>
>> The drm-intel tree gained a conflict against the drm tree.
>>
>> The block tree gained a conflict against Linus' tree.
>>
>> The arm-soc tree gained a conflict against the arm tree.
>>
>> The akpm tree lost a lot of patches that turned up elsewhere.
>>
>> ----------------------------------------------------------------------------
>
> randconf build failure:
>
> make -C drivers/scsi/aic7xxx/aicasm
> *** Install db development libraries
> gcc -I/usr/include -I. aicasm.c aicasm_symbol.c aicasm_gram.c
> aicasm_macro_gram.c aicasm_scan.c aicasm_macro_scan.c -o aicasm -ldb
> aicasm_symbol.c:48:19: fatal error: aicdb.h: No such file or directory
> compilation terminated.
>
>
> random config file attached.
>
>
You need to install berkeley db ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2013-05-02 7:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 8:37 linux-next: Tree for May 1 Stephen Rothwell
2013-05-01 8:37 ` Stephen Rothwell
2013-05-01 11:22 ` Sedat Dilek
2013-05-01 17:59 ` linux-next: Tree for May 1 (media/usb/stk1160) Randy Dunlap
2013-05-01 19:28 ` Yann E. MORIN
2013-05-01 19:32 ` Randy Dunlap
2013-05-01 19:58 ` David Rientjes
2013-05-01 20:23 ` Randy Dunlap
2013-05-01 20:40 ` David Rientjes
2013-05-01 20:53 ` Yann E. MORIN
2013-05-01 20:58 ` Randy Dunlap
2013-05-02 14:52 ` Mauro Carvalho Chehab
2013-05-02 21:23 ` Randy Dunlap
2013-05-04 17:21 ` Splitting stk1160-ac97 as a module (Re: linux-next: Tree for May 1 (media/usb/stk1160)) Ezequiel Garcia
2013-05-04 19:59 ` Yann E. MORIN
2013-05-06 13:11 ` Ezequiel Garcia
2013-05-01 18:44 ` [PATCH -next] hid: fix hid-steelseries kconfig/build Randy Dunlap
2013-05-01 19:27 ` simon
2013-05-01 19:39 ` Randy Dunlap
2013-05-01 20:32 ` simon
2013-05-02 6:27 ` [PATCH] HID: hid-steelseries fix led class build issue Simon Wood
2013-05-02 21:50 ` Randy Dunlap
2013-05-02 21:58 ` David Rientjes
2013-05-03 1:43 ` [PATCH-V2] " Simon Wood
2013-05-03 8:27 ` Jiri Kosina
2013-05-02 6:30 ` [PATCH] " Simon Wood
2013-05-01 19:18 ` [PATCH -next] power: fix lp8788-charger kconfig & build Randy Dunlap
2013-05-01 23:04 ` Kim, Milo
2013-05-03 4:22 ` Anton Vorontsov
2013-05-01 19:27 ` [PATCH -next] staging: sep: fix driver build and kconfig Randy Dunlap
2013-05-02 7:37 ` linux-next: Tree for May 1 ZX
2013-05-02 7:46 ` Hannes Reinecke [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 10:21 Stephen Rothwell
2020-05-01 8:18 Stephen Rothwell
2019-05-01 11:52 Stephen Rothwell
2018-05-01 5:38 Stephen Rothwell
2017-05-01 6:44 Stephen Rothwell
2015-05-01 4:32 Stephen Rothwell
2014-05-01 7:40 Stephen Rothwell
2014-05-01 7:40 ` Stephen Rothwell
2012-05-01 6:22 Stephen Rothwell
2009-05-01 6:34 Stephen Rothwell
2008-05-02 6:40 Stephen Rothwell
2008-05-02 6:43 ` Stephen Rothwell
2008-05-01 6:36 Stephen Rothwell
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=518219BD.9090208@suse.de \
--to=hare@suse.de \
--cc=jencce.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.