linux-kernel - Re: [PATCH 1/1] scripts/recordmcount.pl: There is no -m32 option on Super-H

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150119121028.5b345d0b@gandalf.local.home>
Date:	Mon, 19 Jan 2015 12:10:28 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc:	Heiko Carstens <heiko.carstens@...ibm.com>,
	Michael Karcher <kernel@...rcher.dialup.fu-berlin.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] scripts/recordmcount.pl: There is no -m32 option on
 Super-H

On Mon, 19 Jan 2015 09:18:28 +0100
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de> wrote:

> Hi Steven!
> 
> >> The Super-H architecure seems to be without any maintainer.
> >> Maybe Steven cares to pick this patch up. Dunno...
> 
> > Yeah, I remember when the SH maintainer left.
> 
> > I can pick it up. How urgent is it? Does it need to go in before the
> > next merge window? And does it need to be tagged for stable?
> 
> I am one of the Debian porters of the SH port. Currently, the kernel
> package fails to build from source on our automatic build machines
> due to this bug. Here is the full build log where you can see it
> fail with gcc-4.8:

Unfortunately I don't have a 4.8 cross compiler for superH. It seems to
work fine with -m32 with 4.6 and earlier (which I do have).

> 
> >
> http://buildd.debian-ports.org/status/fetch.php?pkg=linux&arch=sh4&ver=3.16.7-ckt4-1&stamp=1421425783
> 
> Since the SH port of Debian was long time poorly maintained, this
> issue hasn't got any attention for quite a while which means the
> most current kernel version we have at the moment on SH is 3.2.0
> something. I asked Michael to submit this change on my behalf since
> he has submitted kernel patches in the past.
> 
> Thus, it would be nice if this fix could be merged ASAP upstream
> and included in all stable releases as well such that we get a
> working up-to-date kernel on SH soon.

I'll add this info as well to the change log.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/