[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

r5145 - in glibc-package/trunk/debian: . sysdeps



Author: aurel32
Date: 2012-01-30 22:01:17 +0000 (Mon, 30 Jan 2012)
New Revision: 5145

Modified:
   glibc-package/trunk/debian/changelog
   glibc-package/trunk/debian/sysdeps/kfreebsd.mk
Log:
  * sysdeps/kfreebsd.mk: also symlink x86 directory.



Modified: glibc-package/trunk/debian/changelog
===================================================================
--- glibc-package/trunk/debian/changelog	2012-01-30 22:00:08 UTC (rev 5144)
+++ glibc-package/trunk/debian/changelog	2012-01-30 22:01:17 UTC (rev 5145)
@@ -1,3 +1,10 @@
+eglibc (2.13-26) UNRELEASED; urgency=low
+
+  [ Aurelien Jarno ]
+  * sysdeps/kfreebsd.mk: also symlink x86 directory.
+
+ -- Aurelien Jarno <aurel32@debian.org>  Mon, 30 Jan 2012 23:01:02 +0100
+
 eglibc (2.13-25) unstable; urgency=medium
 
   [ Aurelien Jarno ]

Modified: glibc-package/trunk/debian/sysdeps/kfreebsd.mk
===================================================================
--- glibc-package/trunk/debian/sysdeps/kfreebsd.mk	2012-01-30 22:00:08 UTC (rev 5144)
+++ glibc-package/trunk/debian/sysdeps/kfreebsd.mk	2012-01-30 22:01:17 UTC (rev 5145)
@@ -24,14 +24,11 @@
 $(stamp)mkincludedir:
 	rm -rf debian/include
 	mkdir debian/include
-	ln -s $(KFREEBSD_HEADERS)/bsm debian/include
-	ln -s $(KFREEBSD_HEADERS)/net debian/include
-	ln -s $(KFREEBSD_HEADERS)/netatalk debian/include
-	ln -s $(KFREEBSD_HEADERS)/netipx debian/include
-	ln -s $(KFREEBSD_HEADERS)/nfs debian/include
-	ln -s $(KFREEBSD_HEADERS)/osreldate.h debian/include
-	ln -s $(KFREEBSD_HEADERS)/sys debian/include
-	ln -s $(KFREEBSD_HEADERS)/vm debian/include
+	for file in bsm net netatalk netipx nfs osreldate.h sys x86 vm ; do \
+	    if test -e $(KFREEBSD_HEADERS)/$$file ; then \
+	        ln -s $(KFREEBSD_HEADERS)/$$file debian/include ; \
+	    fi ; \
+	done
 
         # Link all machine directories.  We can't just link machine
         # because of explicit references to <machine-amd64/*> and


Reply to: