pastebin - collaborative debugging tool
eckelmann.kpaste.net RSS

Difference between
modified post 3e31c2d62 by Anonymous on Wed 21st Aug 2019 09:27
original post 873573a by Anonymous on Tue 20th Aug 2019 14:37
Download diff
Show old version | new version | both versions

    
1-
diff --git a/ptxdist/local_src/ecu-basicsys/usr/bl/barebox-image b/ptxdist/local_src/ecu-basicsys/usr/bl/barebox-image
1+
$ git commit
2-
deleted file mode 100644
2+
[development 224804b] Fix build failure in ./p images triggered by ecu-basissys AND barebox trying to provide a barebox image
3-
index 64c457e..0000000
3+
 2 files changed, 1 deletion(-)
4-
Binary files a/ptxdist/local_src/ecu-basicsys/usr/bl/barebox-image and /dev/null differ
4+
 delete mode 100644 ptxdist/local_src/ecu-basicsys/usr/bl/barebox-image
5-
diff --git a/ptxdist/rules/ecu-basicsys.make b/ptxdist/rules/ecu-basicsys.make
5+
rmainz@vm ~/work/jncg_development_20190820/jncg/ptxdist $ git push
6-
index f2ad2da..7114553 100644
6+
Counting objects: 45, done.
7-
--- a/ptxdist/rules/ecu-basicsys.make
7+
Delta compression using up to 4 threads.
8-
+++ b/ptxdist/rules/ecu-basicsys.make
8+
Compressing objects: 100% (7/7), done.
9-
@@ -171,7 +171,6 @@ $(STATEDIR)/ecu-basicsys.targetinstall:
9+
Writing objects: 100% (8/8), 859 bytes | 0 bytes/s, done.
10+
Total 8 (delta 6), reused 0 (delta 0)
1017
11-
 	#sbin scripts
18+
12-
 	@$(call install_tree, ecu-basicsys, 0, 0, $(ECU_BASICSYS_DIR)/sbin, /sbin)
19+
13-
-	@$(call install_tree, ecu-basicsys, 0, 0, $(ECU_BASICSYS_DIR)/usr/bl, /usr/bl)
20+
1421
15-
 	#local environment
22+
16-
 	@$(call install_copy, ecu-basicsys, 0, 0, 0755, $(ECU_BASICSYS_DIR)/etc/profile.local, \
23+
1724

Submit a correction or amendment below (click here to make a fresh posting)
After submitting an amendment, you'll be able to view the differences between the old and new posts easily.

Syntax highlighting:

To highlight particular lines, prefix each line with {%HIGHLIGHT}




All content is user-submitted.
The administrators of this site (kpaste.net) are not responsible for their content.
Abuse reports should be emailed to us at