public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Randy Dunlap <randy.dunlap@ORACLE.COM>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
	paulus@samba.org, acme@redhat.com, a.p.zijlstra@chello.nl,
	efault@gmx.de, fweisbec@gmail.com, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/urgent] perf tools: Fix the NO_64BIT build on pure 64-bit systems
Date: Wed, 14 Oct 2009 08:20:52 +0200	[thread overview]
Message-ID: <20091014062052.GD784@elte.hu> (raw)
In-Reply-To: <20091013140915.96cfe060.randy.dunlap@oracle.com>


* Randy Dunlap <randy.dunlap@ORACLE.COM> wrote:

> On Mon, 12 Oct 2009 08:34:16 GMT tip-bot for Ingo Molnar wrote:
> 
> > Commit-ID:  55621ccf2b7a8afe39df8c80f55b28424fd07d13
> > Gitweb:     http://git.kernel.org/tip/55621ccf2b7a8afe39df8c80f55b28424fd07d13
> > Author:     Ingo Molnar <mingo@elte.hu>
> > AuthorDate: Mon, 12 Oct 2009 09:57:25 +0200
> > Committer:  Ingo Molnar <mingo@elte.hu>
> > CommitDate: Mon, 12 Oct 2009 10:00:27 +0200
> > 
> > perf tools: Fix the NO_64BIT build on pure 64-bit systems
> > 
> > Randy Dunlap reported that 'make NO_64BIT=1' fails to build
> > a pure 32-b it binary on 64-bit/64-bit x86 systems.
> > 
> > The reason is that we dont pass in the -m32 and GCC defaults
> > to -m64.
> > 
> > So pass it in - and also extend the warning message about libelf
> > dependencies - glibc-dev[el] is needed as well beyond the libelf
> > library.
> 
> Ingo, thanks, I finally got this working, after installing more 32-bit
> libs etc., like Kyle said that I would need to do.
> 
> The error message is still a little misleading/confusing:
> Makefile:426: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel and glibc-dev[el].  Stop.
> 
> when elfutils-libelf-devel.i586 is installed but glibc-devel.i[56]86 is not
> installed.  gcc failed with:
> In file included from /usr/include/features.h:376,
>                  from /usr/include/sys/types.h:27,
>                  from /usr/include/libelf.h:53,
>                  from elfdeveltest.c:1:
> /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory

Why is it misleading? It says it very clearly that you need to install 
both:

  please install libelf-dev/elfutils-libelf-devel and glibc-dev[el].  Stop.

	Ingo

  reply	other threads:[~2009-10-14  6:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-55621ccf2b7a8afe39df8c80f55b28424fd07d13@git.kernel.org>
2009-10-13 21:09 ` [tip:perf/urgent] perf tools: Fix the NO_64BIT build on pure 64-bit systems Randy Dunlap
2009-10-14  6:20   ` Ingo Molnar [this message]
2009-10-14 14:44     ` Randy Dunlap
2009-10-14 15:58       ` Arnaldo Carvalho de Melo
2009-10-14 16:01         ` Ingo Molnar
2009-10-14 16:02         ` Randy Dunlap
2009-10-19  2:20         ` [PATCH] perf tools: better error messages on missing packages Randy Dunlap
2009-10-19  8:42           ` [tip:perf/core] perf tools: Display " tip-bot for Randy Dunlap

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=20091014062052.GD784@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=randy.dunlap@ORACLE.COM \
    --cc=tglx@linutronix.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