mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Duffy <tduffy@directvinternet.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Kbuild Devel <kbuild-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-devel] Announce: Kernel Build for 2.5, release 3.0 is available
Date: 03 Jun 2002 12:22:18 -0700	[thread overview]
Message-ID: <1023132138.25501.6.camel@tduffy-lnx.afara.com> (raw)
In-Reply-To: <27953.1023071705@kao2.melbourne.sgi.com>

On Sun, 2002-06-02 at 19:35, Keith Owens wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Content-Type: text/plain; charset=us-ascii
> 
> Release 3.0 of kernel build for kernel 2.5 (kbuild 2.5) is available.
> http://sourceforge.net/projects/kbuild/, package kbuild-2.5, download
> release 3.0.
> 
> kbuild-2.5-core-15
>   Changes from core-14.
> 
>     Replace mdbm with kbuild specific database engine to increase
>     performance.
> 
>     Remove CML2 support, Dominik Brodowski, Keith Owens.
> 
>     Remove the restriction on symlinked sources and targets.  Aegis
>     users should be able to use kbuild 2.5 now.

I get this error now on sparc64:

tduffy@curie:/build2/tduffy/linux_kbuild$ make -f Makefile-2.5 oldconfig
Using ARCH='sparc64' AS='as' LD='ld' CC='sparc64-linux-gcc' CPP='sparc64-linux-gcc -E' AR='ar' HOSTAS='as' HOSTLD='gcc' HOSTCC='gcc' HOSTAR='ar'
Generating global Makefile
  phase 1 (find all inputs)
make: *** [phase1] Error 139

tduffy@curie:/build2/tduffy/linux_kbuild$ make -f Makefile-2.5 oldconfig
Using ARCH='sparc64' AS='as' LD='ld' CC='sparc64-linux-gcc' CPP='sparc64-linux-gcc -E' AR='ar' HOSTAS='as' HOSTLD='gcc' HOSTCC='gcc' HOSTAR='ar'
Generating global Makefile
  phase 1 (find all inputs)
pp_makefile1: Attempt to fetch invalid key s(0x73)-9473
make: *** [phase1] Error 134

more verbose (PP_MAKEFILE1_FLAGS=-v) output:

...
Generating global Makefile
  phase 1 (find all inputs)
pp_makefile1 verbose 1
    scan_trees   0 /build2/tduffy/linux_kbuild/
make: *** [phase1] Error 139


-tduffy


  parent reply	other threads:[~2002-06-03 19:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  2:35 Keith Owens
2002-06-03  5:31 ` Keith Owens
2002-06-03 19:22 ` Thomas Duffy [this message]
2002-06-03 19:31   ` [kbuild-devel] " Thunder from the hill
2002-06-03 19:58     ` Thomas Duffy
2002-06-03 20:06       ` Thunder from the hill
2002-06-03 21:12         ` Thomas Duffy
2002-06-04  0:19   ` Keith Owens
2002-06-04  0:29     ` Thomas Duffy
2002-06-04  4:53 ` Keith Owens
2002-06-04  9:16   ` Alex Riesen
2002-06-04 22:55     ` Keith Owens
2002-06-05  2:25       ` [kbuild-devel] " John Cowan
2002-06-05  2:38         ` Keith Owens
2002-06-05 18:13         ` Mark Mielke
2002-06-05 13:19       ` Alex Riesen
2002-06-04 13:59   ` [kbuild-devel] " Arnd Bergmann
2002-06-05 13:53   ` Keith Owens
2002-06-07  8:49     ` Keith Owens
2002-06-12 13:54       ` Keith Owens
2002-06-12 20:55         ` [kbuild-devel] " Thomas Duffy
2002-06-13  0:15           ` Keith Owens

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=1023132138.25501.6.camel@tduffy-lnx.afara.com \
    --to=tduffy@directvinternet.com \
    --cc=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®