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]
Date:	Mon, 4 Dec 2006 04:20:37 -0500
From:	Chuck Ebbert <76306.1226@...puserve.com>
To:	Willy Tarreau <w@....eu>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: makei: shell script for building .i files

On Fri, 24 Nov 2006 22:23:06 +0100, Willy Tarreau wrote:

> BTW, has anyone a good idea on how to make gcc dump the preprocessed files
> for everything it builds ? I mean, just by changing some variables in the
> Makefile.

I came up with this.  Separate output directory option is untested.
It's not quite what you wanted but this is as close as I could get.

#!/bin/bash
#
#	scripts/makei
#
# Make .i files in Linux kernel tree.  You must first build a
# working kernel so this script knows which files to make.
#
# usage:
#	scripts/makei [subdir]
#
#	Use the optional subdir parameter to build .i files
#	for just part of the source tree.
#
# Set the shell variables MAKE and OBJDIR if necessary.
#
#   Examples
#	If:
#		Your output dir is ~/build,
#		you are building the UML arch
#		and you only want to build .i files in drivers/base/
#	Then use:
#		OBJDIR=~/build MAKE='make O=~/build ARCH=um' scripts/makei drivers/base

OBJDIR=${OBJDIR:=.}
MAKE=${MAKE:=make}

OBJDIR=${OBJDIR%/}/

find $OBJDIR$1 -type f -name \*.o |
while read fullname
do
	fullname=${fullname#$OBJDIR}
	name=${fullname%.o}
	[ -f $name.c -o -f $name.S ] && $MAKE $name.i
done
-- 
Chuck
"Even supernovas have their duller moments."
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ