linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, Thomas@ozlabs.org,
	linux-next@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	Alan Modra <amodra@bigpond.net.au>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: powerpc build failure
Date: Thu, 12 Jun 2008 17:23:57 +1000	[thread overview]
Message-ID: <1213255437.14478.30.camel@pasglop> (raw)
In-Reply-To: <20080612170505.6049fa75.sfr@canb.auug.org.au>

On Thu, 2008-06-12 at 17:05 +1000, Stephen Rothwell wrote:
> So I tried this (added --relax to LDFLAGS_vmlinux if CONFIG FTRACE was
> set) and got this;
> 
> /usr/bin/ld: --relax and -r may not be used together
> 
> So, I will disable FTRACE on powerpc for now by removing HAVE_FTRACE
> from
> being selected in arch/powerpc/Kconfig.

So we completely lose ftrace for the sake of a config that nobody
sane ever uses (allyesconfig) ? :-)

Cheers,
Ben.

  parent reply	other threads:[~2008-06-12  7:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  9:27 linux-next: powerpc build failure Stephen Rothwell
2008-06-11  9:59 ` Ingo Molnar
2008-06-12  1:38   ` Paul Mackerras
2008-06-12  5:33     ` Alan Modra
2008-06-12  7:05       ` Stephen Rothwell
2008-06-12  7:16         ` Ingo Molnar
2008-06-12  7:27           ` Stephen Rothwell
2008-06-12  7:47             ` Ingo Molnar
2008-06-12  7:23         ` Benjamin Herrenschmidt [this message]
2008-06-12  7:24         ` Stephen Rothwell
2008-06-12 18:12           ` Sam Ravnborg
2008-06-12  8:15         ` Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2008-06-10  6:54 Stephen Rothwell
2008-06-10  7:20 ` Benjamin Herrenschmidt

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=1213255437.14478.30.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Thomas@ozlabs.org \
    --cc=amodra@bigpond.net.au \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).