[leaf-commits] src/bering-uclibc4/source/libpcap libpcap-1.1.1.tar.gz, NONE, 1.1 buildtool.cfg, 1.1.1.1, 1.2 buildtool.mk, 1.1.1.1, 1.2 libpcap-0.9.5.tar.gz, 1.1.1.1, NONE

Andrew <[email protected]>
Newsgroups gmane.linux.leaf.cvs
Message-ID <[email protected]>
Update of /cvsroot/leaf/src/bering-uclibc4/source/libpcap
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv29184/libpcap

Modified Files:
	buildtool.cfg buildtool.mk 
Added Files:
	libpcap-1.1.1.tar.gz 
Removed Files:
	libpcap-0.9.5.tar.gz 
Log Message:
Updated libpcap & tcpdump


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

--- libpcap-0.9.5.tar.gz DELETED ---

Index: buildtool.cfg
===================================================================
RCS file: /cvsroot/leaf/src/bering-uclibc4/source/libpcap/buildtool.cfg,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** buildtool.cfg	26 Apr 2010 09:02:40 -0000	1.1.1.1
--- buildtool.cfg	30 Aug 2010 16:07:20 -0000	1.2
***************
*** 5,9 ****
  </File>
  
! <File libpcap-0.9.5.tar.gz>
    Server = cvs4-sourceforge
    Revision = HEAD  
--- 5,9 ----
  </File>
  
! <File libpcap-1.1.1.tar.gz>
    Server = cvs4-sourceforge
    Revision = HEAD  
***************
*** 14,18 ****
  <Package>
      <libpcap>
! 	    Version = 0.9.5
  	    Revision = 1
  	    
--- 14,18 ----
  <Package>
      <libpcap>
! 	    Version = 1.1.1
  	    Revision = 1
  	    
***************
*** 35,40 ****
  	    <Contents>
  		    <File>
! 			    Source	= usr/lib/libpcap.so.0.9.5
! 			    Filename	= usr/lib/libpcap.so.0.9.5
  			    Type	= binary
  			    Permissions	= 755
--- 35,40 ----
  	    <Contents>
  		    <File>
! 			    Source	= usr/lib/libpcap.so.1.1.1
! 			    Filename	= usr/lib/libpcap.so.1.1.1
  			    Type	= binary
  			    Permissions	= 755
***************
*** 42,46 ****
  		    
  		    <File>
! 			    Target	= usr/lib/libpcap.so.0.9.5
  			    Filename	= usr/lib/libpcap.so
  			    Type	= link
--- 42,46 ----
  		    
  		    <File>
! 			    Target	= usr/lib/libpcap.so.1.1.1
  			    Filename	= usr/lib/libpcap.so
  			    Type	= link

Index: buildtool.mk
===================================================================
RCS file: /cvsroot/leaf/src/bering-uclibc4/source/libpcap/buildtool.mk,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** buildtool.mk	26 Apr 2010 09:02:40 -0000	1.1.1.1
--- buildtool.mk	30 Aug 2010 16:07:20 -0000	1.2
***************
*** 6,10 ****
  
  include $(MASTERMAKEFILE)
! LIBPCAP_DIR:=libpcap-0.9.5
  LIBPCAP_TARGET_DIR:=$(BT_BUILD_DIR)/libpcap
  export CC=$(TARGET_CC)
--- 6,10 ----
  
  include $(MASTERMAKEFILE)
! LIBPCAP_DIR:=libpcap-1.1.1
  LIBPCAP_TARGET_DIR:=$(BT_BUILD_DIR)/libpcap
  export CC=$(TARGET_CC)
***************
*** 35,41 ****
  	$(MAKE) DESTDIR=$(LIBPCAP_TARGET_DIR) -C $(LIBPCAP_DIR) install
  	$(MAKE) DESTDIR=$(LIBPCAP_TARGET_DIR) -C $(LIBPCAP_DIR) install-shared
! 	$(BT_STRIP) $(BT_STRIP_LIBOPTS) $(LIBPCAP_TARGET_DIR)/usr/lib/libpcap.so.0.9.5
  #	ln -sf libpcap.so.0.9.5 $(LIBPCAP_TARGET_DIR)/usr/lib/libpcap.so.0.9
! 	ln -sf libpcap.so.0.9.5 $(LIBPCAP_TARGET_DIR)/usr/lib/libpcap.so
  	cp -a $(LIBPCAP_TARGET_DIR)/* $(BT_STAGING_DIR)
  	touch $(LIBPCAP_DIR)/.build
--- 35,41 ----
  	$(MAKE) DESTDIR=$(LIBPCAP_TARGET_DIR) -C $(LIBPCAP_DIR) install
  	$(MAKE) DESTDIR=$(LIBPCAP_TARGET_DIR) -C $(LIBPCAP_DIR) install-shared
! 	$(BT_STRIP) $(BT_STRIP_LIBOPTS) $(LIBPCAP_TARGET_DIR)/usr/lib/*
  #	ln -sf libpcap.so.0.9.5 $(LIBPCAP_TARGET_DIR)/usr/lib/libpcap.so.0.9
! 	ln -sf libpcap.so.1.1.1 $(LIBPCAP_TARGET_DIR)/usr/lib/libpcap.so
  	cp -a $(LIBPCAP_TARGET_DIR)/* $(BT_STAGING_DIR)
  	touch $(LIBPCAP_DIR)/.build


------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.