| 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
| ||
|
Date: Tue, 28 Apr 2015 21:33:12 -0700 From: Guenter Roeck <linux@...ck-us.net> To: Yoshinori Sato <ysato@...rs.sourceforge.jp> CC: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org Subject: Re: [PATCH v9 00/17] Re-introduce h8300 architecture On 04/28/2015 10:25 AM, Yoshinori Sato wrote: > At Tue, 28 Apr 2015 06:22:10 -0700, > Guenter Roeck wrote: >> >> On Mon, Apr 27, 2015 at 02:35:07PM +0900, Yoshinori Sato wrote: >>> Hello. >>> I will re-introducing h8300. >>> >> >> Hi, >> >> can you provide a link to a working toolchain, or provide directions >> on how to build one ? > > h8300-unknown-linux in gcc / binutils development version. > Patch of a release version has not been prepared yet. > Hi, With a toolchain based on binutils 2.25 (patched), gcc 5.1 (unpatched), and newlib 1.20 (unpatched), I get for both h8300h-sim_defconfig and h8s-sim_defconfig: ./arch/h8300/kernel/vmlinux.lds:247: undefined symbol `jiffies_64' referenced in expression I had to modify arch/h8300/Makefile a bit since the linker does not understand -mh8300helf_linux and -mh8300self_linux; I had to use -mh8300helf and -mh8300self instead. Maybe I am missing a binutils patch. I also had to use h8300-linux-elf as target to convince gcc to accept it as valid target. Both should not result in the undefined symbol error, though. Guenter -- 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/
Powered by blists - more mailing lists