From: Ingo Molnar <mingo@elte.hu>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: Parag Warudkar <kernel-stuff@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: RT patch breaks X86_64 build
Date: Thu, 2 Jun 2005 20:33:43 +0200 [thread overview]
Message-ID: <20050602183343.GB30309@elte.hu> (raw)
In-Reply-To: <429F4A19.7030508@stud.feec.vutbr.cz>
* Michal Schmidt <xschmi00@stud.feec.vutbr.cz> wrote:
> Ingo Molnar wrote:
> >hm, it does work for me. I had trouble in the past with gcc & mcount on
> >x64. This version seems to work fine for me:
> >
> > gcc version 3.4.0 20040129 (Red Hat Linux 3.4.0-0.3)
>
> I could not find this exact version, so I downloaded
> gcc34-3.4.0-1.x86_64.rpm from Fedora Core 2, converted it do .deb with
> alien, installed it and made a symlink gcc -> gcc34. gcc --version says:
> gcc (GCC) 3.4.0 (Red Hat Linux 3.4.0-1)
>
> I did "make mrproper", copied back your .config, enabled LATENCY_TRACE
> and rebuilt the kernel.
> init still segfaults.
hm, one difference is that i'm running a 64-bit kernel but 32-bit
userspace (FC3-ish).
> It would be good to hear about other people's experiences with
> LATENCY_TRACE on amd64. Am I the only one for whom it breaks?
i definitely had problems with LATENCY_TRACE on x64 in the past - i am
in fact surprised that it works for me.
Ingo
next prev parent reply other threads:[~2005-06-02 18:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 1:41 Parag Warudkar
2005-05-31 2:01 ` Parag Warudkar
2005-05-31 6:08 ` Michal Schmidt
2005-05-31 11:53 ` Parag Warudkar
2005-05-31 12:05 ` Michal Schmidt
2005-06-01 9:13 ` Ingo Molnar
2005-06-02 12:28 ` Michal Schmidt
2005-06-02 12:39 ` Ingo Molnar
2005-06-02 14:13 ` Michal Schmidt
2005-06-02 15:55 ` Michal Schmidt
2005-06-02 16:17 ` Ingo Molnar
2005-06-02 16:37 ` Michal Schmidt
2005-06-02 18:04 ` Michal Schmidt
2005-06-02 18:33 ` Ingo Molnar [this message]
2005-06-02 22:45 ` Michal Schmidt
2005-06-03 5:18 ` Ingo Molnar
2005-06-03 11:03 ` Michal Schmidt
2005-06-02 12:31 ` Michal Schmidt
2005-06-02 12:37 ` Ingo Molnar
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=20050602183343.GB30309@elte.hu \
--to=mingo@elte.hu \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xschmi00@stud.feec.vutbr.cz \
/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®