[leaf-commits] src/bering-uclibc4/source/dmidecode buildtool.cfg, NONE, 1.1 buildtool.mk, NONE, 1.1 dmidecode-2.10.tar.gz, NONE, 1.1 make.patch, NONE, 1.1

Update of /cvsroot/leaf/src/bering-uclibc4/source/dmidecode
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv20964

Added Files:
	buildtool.cfg buildtool.mk dmidecode-2.10.tar.gz make.patch 
Log Message:
Updated to latest upstream version while migrating to cvs4 and patching for make 3.82

--- NEW FILE: buildtool.mk ---
#############################################################
#
# buildtool makefile for dmidecode
#
#############################################################

include $(MASTERMAKEFILE)

DMI_DIR:=$(shell $(BT_TGZ_GETDIRNAME) $(DMI_SOURCE) 2>/dev/null )
ifeq ($(DMI_DIR),)
DMI_DIR:=$(shell cat DIRNAME)
endif
DMI_TARGET_DIR:=$(BT_BUILD_DIR)/dmidecode

$(DMI_DIR)/.source:
	zcat $(DMI_SOURCE) | tar -xvf -
	echo $(DMI_DIR) > DIRNAME
	cat $(DMI_PATCH1) | patch -p1 -d $(DMI_DIR)
	touch $(DMI_DIR)/.source

source: $(DMI_DIR)/.source
                                                                 
$(DMI_DIR)/.build: $(DMI_DIR)/.source
	mkdir -p $(DMI_TARGET_DIR)
	make CC=$(TARGET_CC) LD=$(TARGET_LD) -C $(DMI_DIR) DESTDIR=$(DMI_TARGET_DIR) prefix=/usr install
	-$(BT_STRIP) $(BT_STRIP_BINOPTS) $(DMI_TARGET_DIR)/usr/sbin/*
	cp -a $(DMI_TARGET_DIR)/* $(BT_STAGING_DIR)
	touch $(DMI_DIR)/.build

build: $(DMI_DIR)/.build
                                                                                         
clean:
	rm -rf $(DMI_TARGET_DIR)
	rm -f $(DMI_DIR)/.build
                                                                                                                 
srcclean: clean
	rm -rf $(DMI_DIR) 
	-rm DIRNAME


--- NEW FILE: buildtool.cfg ---

<File buildtool.mk>
  Server = cvs-sourceforge
  Revision = HEAD
  Directory = dmidecode
</File>
                  
<File dmidecode-2.10.tar.gz>
  Server = cvs-sourceforge
  Revision = HEAD
  envname = DMI_SOURCE
  Directory = dmidecode
</File>

<File make.patch>
  Server = cvs-sourceforge
  Revision = HEAD
  envname = DMI_PATCH1
  Directory = dmidecode
</File>

<Package>
	<dmidec>
		Version = 2.10
		Revision = 1

		Help <<EOF
		DMI decode reports information about your system's hardware 
		as described in your system BIOS according to the SMBIOS/DMI 
		standard.
		Homepage: http://www.nongnu.org/dmidecode/
		LEAF package by __PACKAGER__, __BUILDDATE__
		EOF
		
		<Permissions>
			Files = 644
			Directories = 755
		</Permissions>

		<Owner>
			Files = root:root
			Directories = root:root
		</Owner>
		
		<Contents>
			<File>          
				Source          = usr/sbin/dmidecode
				Filename        = usr/sbin/dmidecode
				Type            = binary
				Permissions = 755
			</File>		
			<File>          
				Source          = usr/sbin/biosdecode
				Filename        = usr/sbin/biosdecode
				Type            = binary
				Permissions = 755
			</File>		
		</Contents>			
	</dmidec>
</Package>


--- NEW FILE: make.patch ---
*** dmidecode-2.9/Makefile.orig	2007-02-16 11:00:12.000000000 +0000
--- dmidecode-2.9/Makefile	2011-01-15 14:47:00.000000000 +0000
***************
*** 39,45 ****
  # BSD make doesn't understand the $(shell) syntax above, it wants the !=
  # syntax below. GNU make ignores the line below so in the end both BSD
  # make and GNU make are happy.
! PROGRAMS != echo dmidecode ; test `uname -m 2>/dev/null` != ia64 && echo biosdecode ownership vpddecode
  
  all : $(PROGRAMS)
  
--- 39,46 ----
  # BSD make doesn't understand the $(shell) syntax above, it wants the !=
  # syntax below. GNU make ignores the line below so in the end both BSD
  # make and GNU make are happy.
! ### This trick no longer works with GNU make 3.82
! ###PROGRAMS != echo dmidecode ; test `uname -m 2>/dev/null` != ia64 && echo biosdecode ownership vpddecode
  
  all : $(PROGRAMS)
  

--- NEW FILE: dmidecode-2.10.tar.gz ---
(This appears to be a binary file; contents omitted.)


------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl