linux-kernel - m68k: main.c:(.init.text+0x730): undefined reference to `strlen'

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-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0805140958400.5778@anakin>
Date:	Wed, 14 May 2008 10:02:11 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Linux/m68k <linux-m68k@...r.kernel.org>
cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: m68k: main.c:(.init.text+0x730): undefined reference to `strlen'


M68k builds with current mainline fail with

    init/built-in.o: In function `kernel_init':
    main.c:(.init.text+0x730): undefined reference to `strlen'

Reverting commit e662e1cfd434aa234b72fbc781f1d70211cb785b

    Author: Cyrill Gorcunov <gorcunov@...il.com>
    Date:   Mon May 12 14:02:22 2008 -0700

    init: don't lose initcall return values

    There is an ability to lose an initcall return value if it happened with irq
    disabled or imbalanced preemption (and if we debug initcall).

fixes the problem. My first guess is gcc is turning sizeof() into strlen()
again.

Sample build log available at
http://kisskb.ellerman.id.au/kisskb/buildresult/27596/

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
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/