mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "werner" <werner@copaya.yi.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: same problem with 2.6.24-rc2
Date: Wed, 7 Nov 2007 17:06:40 -0800	[thread overview]
Message-ID: <20071107170640.ca861b15.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1194481962.7222@copaya.yi.org>

On Wed, 07 Nov 2007 21:32:43 -0300 (GFT) werner wrote:

> On 7/Nov/2007 20:10 werner wrote ..
> > With 2.6.23-rc2 is the same problem:  it crashed at the beginning:  EIP 060 c03fdea4
> > EFLAGS 00010212 EIP is at xor_sse_2+0x34/0x200
> > Again during the compilation was reclaimed that <source-dir>/arch/x86/Makefile.o
> > cannot be found and were certain dependencies on it not made, such a file isn't
> > present in the source code (present are, f.ex. Makefile_32 , Makefile_64 ), nor
> > was generated automaticaly during compilation, I think this is incorrect and the
> > reason for the problems

Hi,

Please provide the complete build log (with V=1 if possible) for the
missing Makefile.o problem.

E.g.:

make V=1 all >build.log 2>&1

Make sure that build.log contains the error message and then send
the complete build.log file to us at linux-kernel@vger.kernel.org .


> > wl
> > werner@copaya.yi.org
> > =============================================================================
> > On 7/Nov/2007 16:14 Andrew Morton wrote ..
> > > > On Wed, 07 Nov 2007 15:55:12 -0300 (GFT) "werner" <werner@copaya.yi.org> wrote:
> > > > I really don't know what's happening.  I don't understand nothing about the
> > kernel
> > > error reporting system.   Because of this, always when there is a problem, I
> > report
> > > it via e-mail to  linux-kernel@vger.kernel.org .  I don't know what people there
> > > do with my messages.     
> > > 
> > > 
> > > It went like this:
> > > 
> > > 1: you sent an email to linux-kernel
> > > 
> > > 2: I sent a reply to you and linux-kernel
> > > 
> > > 3: you sent a reply to me, but NOT linux-kernel!
> > > 
> > > In other words, you did "reply", not "reply to all", thus you removed three
> > > thousand people from the discussion.  One of those people is the person who
> > > created the bug which you're hitting, and that person no longer knows
> > > what's happening.
> > > 
> > > 
> > > So please go back and resend all those emails, and retain ALL Cc:'s.  Don't
> > > just send them only to me.  Keep all indivisuals and all mailing lists on
> > > the email Cc: list.



---
~Randy

  reply	other threads:[~2007-11-08  1:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  0:32 werner
2007-11-08  1:06 ` Randy Dunlap [this message]
     [not found] <1194501449.25336@copaya.yi.org>
2007-11-08  7:05 ` Randy Dunlap
2007-11-09  5:28   ` 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=20071107170640.ca861b15.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=werner@copaya.yi.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®