From: Helge Deller <deller@gmx.de>
To: Simone Mannori <simone.mannori@gmail.com>
Cc: linux-parisc <linux-parisc@vger.kernel.org>,
John David Anglin <dave.anglin@bell.net>,
Riccardo Schiavi <r.schiavi@evidence.eu.com>
Subject: Re: Kernel for bug hunting
Date: Fri, 15 Apr 2016 17:20:46 +0200 [thread overview]
Message-ID: <571106CE.2040406@gmx.de> (raw)
In-Reply-To: <CACrbsaBDN70Q=JxjpsruVNLgi+X262MEQY+zgy1mdOwVmFZB2A@mail.gmail.com>
On 15.04.2016 16:57, Simone Mannori wrote:
> Inside a clean directory I have cloned the repository
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>
> and everythings looks OK.
>
> I have changed directory with to "cd linux-stable/"; then I have
> verified the presence of other branches with "git branch -a"; then I
> have checkout the branch that you told me using
>
> git checkout -b hppa remotes/origin/linux-4.5.y
>
> Now the situation looks perfect:
> simone@blsw:~/kernel/git/linux-stable$ git branch
> * hppa
> master
>
> GCC looks good:
> simone@blsw:~/kernel/git/linux-stable$ gcc -v
As Dave mentioned, you need the 64bit hppa compiler (gcc-4.9-hppa64).
root@phantom:~# hppa64-linux-gnu-gcc-4.9 --version
hppa64-linux-gnu-gcc-4.9 (GCC) 4.9.3
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Run
"apt-get install gcc-4.9-hppa64", or even better:
"apt-get build-dep linux" to get all packages required to build the kernel (see my other mail).
> I'm using your .config untouched.
Try:
make ARCH=parisc oldconfig
make ARCH=parisc vmlinux modules
Helge
prev parent reply other threads:[~2016-04-15 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 5:04 Kernel for bug hunting Simone Mannori
2016-04-15 8:41 ` Helge Deller
2016-04-15 8:45 ` Simone Mannori
2016-04-15 13:39 ` John David Anglin
2016-04-15 14:57 ` Simone Mannori
2016-04-15 15:20 ` Helge Deller [this message]
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=571106CE.2040406@gmx.de \
--to=deller@gmx.de \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@vger.kernel.org \
--cc=r.schiavi@evidence.eu.com \
--cc=simone.mannori@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.