public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: GIT head doesn't seem to want to build on 32bit..
Date: Wed, 17 Dec 2008 15:48:32 -0800	[thread overview]
Message-ID: <20081217154832.f29539af.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081217113029.GB5027@uranus.ravnborg.org>

On Wed, 17 Dec 2008 12:30:29 +0100 Sam Ravnborg wrote:

> On Wed, Dec 17, 2008 at 10:07:27AM +0000, Alan Cox wrote:
> > 
> > > Smells like a kbuild issue.
> > > Please copy me and linux-kbuild@vger.kernel.org on any findings.
> > > 
> > > [My 64 bit toolchain is br0ken atm so I could not try to reproduce]
> > 
> > Yes I do indeed need to build x86_64 first, then make distclean or
> > mrproper and then 32bit build fails
> 
> I will fix my 64 bit build soonish.
> In the meantime could someone do:
> 
> 1) git clean -dxf
> 2) Make a 64 bit x86 build.

without using O=dir, correct?

> 3) make distclean
> 4) git ls-files -o
> 
> And post the output of 4)
> Something is left that causes us to fail and I wonder what it is.
> 
> [I'm afraid it is not this simple but I hope this can tell us what it is]

Afraid not; git ls-files -o only listed the build output file for me.  Sorry.

---
~Randy

  reply	other threads:[~2008-12-17 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081216172859.5bc030b6@lxorguk.ukuu.org.uk>
     [not found] ` <alpine.LFD.2.00.0812160946410.14014@localhost.localdomain>
     [not found]   ` <20081216181133.2342b49e@lxorguk.ukuu.org.uk>
     [not found]     ` <20081216183817.GA25108@uranus.ravnborg.org>
2008-12-17 10:07       ` GIT head doesn't seem to want to build on 32bit Alan Cox
2008-12-17 11:30         ` Sam Ravnborg
2008-12-17 23:48           ` Randy Dunlap [this message]
2008-12-20  2:02           ` Alexey Zaytsev
2008-12-19 22:02         ` Sam Ravnborg
2008-12-19 22:08           ` Sam Ravnborg
2008-12-20  0:27           ` Alan Cox

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=20081217154832.f29539af.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.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