All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: davidsen@tmr.com, linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: 2.6.2-mjb1
Date: Thu, 12 Feb 2004 11:45:59 -0800	[thread overview]
Message-ID: <12180000.1076615159@flay> (raw)
In-Reply-To: <200402121431.19876.davidsen@oddball.prodigy.com>

Does it go away if you revert these two?

ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/patches/2.6.2/2.6.2-mjb1/370-emulex
ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/patches/2.6.2/2.6.2-mjb1/371-multiple_emulex

M.

--On Thursday, February 12, 2004 14:31:19 -0500 Bill Davidsen <davidsen@oddball.prodigy.com> wrote:

> On Wednesday 11 February 2004 03:44 pm, Martin J. Bligh wrote:
>> The patchset is meant to be pretty stable, not so much a testing ground.
>> Main differences from mainline are:
>> 
>> 1. Better performance & resource consumption, particularly on larger
>> machines. 2. Diagnosis tools (kgdb, early_printk, etc).
>> 3. Updated arch support for AMD64 + PPC64.
>> 4. Better support for sound, especially OSS emulation over ALSA.
>> 5. Better support for video (v4l2, bttv, ivtv).
>> 6. Kexec support.
>> 
>> I'd be very interested in feedback from anyone willing to test on any
>> platform, however large or small.
>> 
>> ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/2.6.2/patch-2.6.2-mjb1.
>> bz2
>> 
>> Since 2.6.1-mjb1 (~ = changed, + = added, - = dropped)
> 
> The first thing I notice is that "make rpm" didn't work, and failed with the 
> error code at the bottom of this message. Too bad, since I've been building 
> RPMs on a big fast WBEL-3.0 four way Xeon, but have to run them on a humble 
> PII-350. Forgive me, I do NOT want to build kernels on the test machine, it 
> takes forever and needs a bit of temp space tweaking as well.
> 
> Built clean by itself, I just can't move and install it easily.
> 
> ~~~~~~~~~~~~~~~~~~~~
> 
> + umask 022
> + cd /usr/src/redhat/BUILD
> + LANG=C
> + export LANG
> + unset DISPLAY
> + exit 0
> Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.33180
> + umask 022
> + cd /usr/src/redhat/BUILD
> + LANG=C
> + export LANG
> + unset DISPLAY
> + rm -rf /tmp/lpfc-LPFC_DRIVER_VERSION
> + mkdir -p /tmp/lpfc-LPFC_DRIVER_VERSION/lpfc-LPFC_DRIVER_VERSION
> + cd lpfc-LPFC_DRIVER_VERSION
> /var/tmp/rpm-tmp.33180: line 28: cd: lpfc-LPFC_DRIVER_VERSION: No such file or 
> directory
> error: Bad exit status from /var/tmp/rpm-tmp.33180 (%build)
> 
> 
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.33180 (%build)
> make: *** [rpm] Error 1
> 
> -- 
> Bill Davidsen, TMR
> 
> 



WARNING: multiple messages have this Message-ID (diff)
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: davidsen@tmr.com, linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: 2.6.2-mjb1
Date: Thu, 12 Feb 2004 11:45:59 -0800	[thread overview]
Message-ID: <12180000.1076615159@flay> (raw)
In-Reply-To: <200402121431.19876.davidsen@oddball.prodigy.com>

Does it go away if you revert these two?

ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/patches/2.6.2/2.6.2-mjb1/370-emulex
ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/patches/2.6.2/2.6.2-mjb1/371-multiple_emulex

M.

--On Thursday, February 12, 2004 14:31:19 -0500 Bill Davidsen <davidsen@oddball.prodigy.com> wrote:

> On Wednesday 11 February 2004 03:44 pm, Martin J. Bligh wrote:
>> The patchset is meant to be pretty stable, not so much a testing ground.
>> Main differences from mainline are:
>> 
>> 1. Better performance & resource consumption, particularly on larger
>> machines. 2. Diagnosis tools (kgdb, early_printk, etc).
>> 3. Updated arch support for AMD64 + PPC64.
>> 4. Better support for sound, especially OSS emulation over ALSA.
>> 5. Better support for video (v4l2, bttv, ivtv).
>> 6. Kexec support.
>> 
>> I'd be very interested in feedback from anyone willing to test on any
>> platform, however large or small.
>> 
>> ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/2.6.2/patch-2.6.2-mjb1.
>> bz2
>> 
>> Since 2.6.1-mjb1 (~ = changed, + = added, - = dropped)
> 
> The first thing I notice is that "make rpm" didn't work, and failed with the 
> error code at the bottom of this message. Too bad, since I've been building 
> RPMs on a big fast WBEL-3.0 four way Xeon, but have to run them on a humble 
> PII-350. Forgive me, I do NOT want to build kernels on the test machine, it 
> takes forever and needs a bit of temp space tweaking as well.
> 
> Built clean by itself, I just can't move and install it easily.
> 
> ~~~~~~~~~~~~~~~~~~~~
> 
> + umask 022
> + cd /usr/src/redhat/BUILD
> + LANG=C
> + export LANG
> + unset DISPLAY
> + exit 0
> Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.33180
> + umask 022
> + cd /usr/src/redhat/BUILD
> + LANG=C
> + export LANG
> + unset DISPLAY
> + rm -rf /tmp/lpfc-LPFC_DRIVER_VERSION
> + mkdir -p /tmp/lpfc-LPFC_DRIVER_VERSION/lpfc-LPFC_DRIVER_VERSION
> + cd lpfc-LPFC_DRIVER_VERSION
> /var/tmp/rpm-tmp.33180: line 28: cd: lpfc-LPFC_DRIVER_VERSION: No such file or 
> directory
> error: Bad exit status from /var/tmp/rpm-tmp.33180 (%build)
> 
> 
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.33180 (%build)
> make: *** [rpm] Error 1
> 
> -- 
> Bill Davidsen, TMR
> 
> 


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-02-12 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 20:44 2.6.2-mjb1 Martin J. Bligh
2004-02-11 20:44 ` 2.6.2-mjb1 Martin J. Bligh
2004-02-12 19:31 ` 2.6.2-mjb1 Bill Davidsen
2004-02-12 19:31   ` 2.6.2-mjb1 Bill Davidsen
2004-02-12 19:45   ` Martin J. Bligh [this message]
2004-02-12 19:45     ` 2.6.2-mjb1 Martin J. Bligh

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=12180000.1076615159@flay \
    --to=mbligh@aracnet.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 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.