linux-kernel - Re: 2.6.24-git7: section mismatches woes

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: <20080203123734.GH20810@uranus.ravnborg.org>
Date:	Sun, 3 Feb 2008 13:37:34 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.24-git7: section mismatches woes

> > > suspend to RAM working?
> > I dunno - never used it I'm afraid. And do not know how to do it either.
> 
> # echo mem > /sys/power/state
> 
> (better do it after a fresh boot for the first time in case it fails).

Will try later - thanks.

> > The way to approach it is straightforward but boring.
> > 
> > You can add:
> > ccflags-y += -fno-inline-functions-called-once
> > to the Makefiles where you think this can have caused troubles until
> > you find the problematic directory.
> > kbuild will pick up that gcc options changed and rebuild
> > all relevant files.
> > 
> > When the problematic directory is located then
> > remove the ccflags-y assignment and do it file-by-file
> > using the CFLAGS_xxx.o syntax:
> > 
> > CFLAGS_file.o := -fno-inline-functions-called-once
> 
> Do I have to pass any special options to "make"?

When you do it this way by tweaking the Makefiles - no.
And you do not have to delete .o files manually to get them
rebuild.

	Sam
--
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/