[leaf-commits] src/bering-uclibc4/source/libopcodes buildtool.cfg, NONE, 1.1 buildtool.mk, NONE, 1.1

Andrew <[email protected]> Mon, 03 Jan 2011 18:34:34 +0000
Newsgroups gmane.linux.leaf.cvs
Message-ID <[email protected]>
Update of /cvsroot/leaf/src/bering-uclibc4/source/libopcodes
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv29397/libopcodes

Added Files:
	buildtool.cfg buildtool.mk 
Log Message:
Added libraries, modified devtools, changed oprofile dependencies


--- NEW FILE: buildtool.cfg ---
<File buildtool.mk>
  Server = cvs4-sourceforge
  Revision = HEAD
  Directory = libopcodes
</File>

<Package>
	<libopcodes>
		Version = 2.20.1
		Revision = 1
		
		Help <<EOF		
		The opcodes library from binutils
		Homepage: http://www.gnu.org/software/binutils/
		LEAF package by __PACKAGER__, __BUILDDATE__
		EOF
		
		<Permissions>
			Files = 644
			Directories = 755
		</Permissions>
                                                       
		<Owner>
			Files = root:root
			Directories = root:root
		</Owner>
		
		<Contents>
			<File>
				Filename        = lib/libopcodes-2.20.1.20100303.so
				Source          = lib/libopcodes-2.20.1.20100303.so
				Type            = binary
			</File>
			<File>
				Filename        = lib/libopcodes.so
				Target          = lib/libopcodes-2.20.1.20100303.so
				Type            = link
			</File>                                                                                                                                                                                
		</Contents>
	</libopcodes>
</Package>                                                                                                                       
                                                                                                                                       		

--- NEW FILE: buildtool.mk ---
#############################################################
#
# libm
#
#############################################################

include $(MASTERMAKEFILE)

source: 
	# nothing to be done

build:
	# nothing to be done

clean:
	# nothing to be done


------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl