public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "werner" <w.landgraf@ru.ru>
To: Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 3.8-rc1: compiling problem in perf-event-p6.o
Date: Sat, 19 Jan 2013 16:11:45 -0400	[thread overview]
Message-ID: <web-836074559@zbackend1.aha.ru> (raw)
In-Reply-To: <50F75349.2050609@infradead.org>

This didn't happen on 3.6  (3.7 I had no time to check 
out), although I continue to use the same c compiler and 
libraries.  So it should be caused by any change of the 
subroutine perf_event_p6  made in the last time.  Also, 
everything else of the kernel compiled, just not that 
subroutine.   Anyway the kernel should compile correctly 
with all recent versions of the c compiler, so one should 
search and fix that.   The maintainer of that subroutine 
should be notified, and check the last changes since 3.6 .

Also, I always compile the WHOLE kernel, not only changed 
subroutines. Perhaps in any other subroutine was changed 
something of global variables in any other subroutine, 
what is now incompatible with subroutine perf_event_p6

W.Landgraf



=============================================
On Wed, 16 Jan 2013 17:26:33 -0800
  Randy Dunlap <rdunlap@infradead.org> wrote:
> On 01/15/13 06:50, werner wrote:
>> We are now on -rc3 and someone should correct this, 
>>finally
>> 
>> This is a regression, it was not before, on 3.6
>> 
>> This messes up any compilation of the whole kernel, it 
>>results in don't be produced vmlinuz
>> 
>> arch/x86/kernel/cpu/perf_event_p6.o   depends on so much 
>>things that I don't get it switched off, I suppose it's 
>>necesary for the most systems
>> 
>> 
>> W.Landgraf
>> 
>> 
>> 
>> 
>> 
>> 
>> =================
>> The problem continues with 3.8-rc
>> 
>> This is grave, no vmlinuz is produced.
>> 
>> 
>> wl
>> 
>>   CC arch/x86/kernel/cpu/perf_event.o
>>   CC arch/x86/kernel/cpu/perf_event_amd.o
>>   CC arch/x86/kernel/cpu/perf_event_p6.o
>> arch/x86/kernel/cpu/perf_event_p6.c:22: error: 
>>p6_hw_cache_event_ids causes a section type conflict
>> make[3]: [arch/x86/kernel/cpu/perf_event_p6.o] Error 1 
>>(ignored)
>>   CC arch/x86/kernel/cpu/perf_event_knc.o
>>   CC arch/x86/kernel/cpu/perf_event_p4.o
>>   CC arch/x86/kernel/cpu/perf_event_intel_lbr.o
>> 
>> ================================================
>> There ocurs a compiling error in perf-event-p6.o , any 
>>regression, unfortunately I lost the compiling list but I 
>>think it was any incompatibility / redefinition with 
>>something else, pls check and correct that, if not 
>>already done
>> W.Landgraf
> 
> Hi,
> 
> I don't see this problem on 3.8-rc1 or -rc3.
> Maybe a difference/problem in gcc??
> 
> 
> -- 
> ~Randy
> 
> 

"werner" <w.landgraf@ru.ru>
---
Professional hosting for everyone - http://www.host.ru

  reply	other threads:[~2013-01-19 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 14:50 Linux 3.8-rc1: compiling problem in perf-event-p6.o werner
2013-01-17  1:26 ` Randy Dunlap
2013-01-19 20:11   ` werner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-01 15:08 werner
2013-03-01 16:08 ` Linus Torvalds
2013-01-06  0:18 werner
2013-01-03  1:10 werner

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=web-836074559@zbackend1.aha.ru \
    --to=w.landgraf@ru.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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