From 716ca530e1c4515d8683c9d5be3d56b301758b66 Mon Sep 17 00:00:00 2001 From: James <> Date: Wed, 4 Nov 2015 11:49:21 +0000 Subject: trunk-47381 --- ...s.fat.c-Use-unsigned-char-for-binary-data.patch | 33 ++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 tools/dosfstools/patches/0003-mkfs.fat.c-Use-unsigned-char-for-binary-data.patch (limited to 'tools/dosfstools/patches/0003-mkfs.fat.c-Use-unsigned-char-for-binary-data.patch') diff --git a/tools/dosfstools/patches/0003-mkfs.fat.c-Use-unsigned-char-for-binary-data.patch b/tools/dosfstools/patches/0003-mkfs.fat.c-Use-unsigned-char-for-binary-data.patch new file mode 100644 index 0000000..842a7c1 --- /dev/null +++ b/tools/dosfstools/patches/0003-mkfs.fat.c-Use-unsigned-char-for-binary-data.patch @@ -0,0 +1,33 @@ +From 8b8948c06de55455b63dc11f765d7ee39f30c4e0 Mon Sep 17 00:00:00 2001 +From: Andreas Bombe +Date: Mon, 29 Dec 2014 18:24:54 +0100 +Subject: [PATCH 03/14] mkfs.fat.c: Use unsigned char for binary data + +Simple char technically works for the dummy_boot_jump variables, but +some compiler warning settings would give a warning over a signed char +overflowing with the values given as initializers. + +Signed-off-by: Andreas Bombe +--- + src/mkfs.fat.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/src/mkfs.fat.c b/src/mkfs.fat.c +index 604b7d0..1f702ad 100644 +--- a/src/mkfs.fat.c ++++ b/src/mkfs.fat.c +@@ -219,9 +219,9 @@ struct msdos_dir_entry { + /* The "boot code" we put into the filesystem... it writes a message and + tells the user to try again */ + +-char dummy_boot_jump[3] = { 0xeb, 0x3c, 0x90 }; ++unsigned char dummy_boot_jump[3] = { 0xeb, 0x3c, 0x90 }; + +-char dummy_boot_jump_m68k[2] = { 0x60, 0x1c }; ++unsigned char dummy_boot_jump_m68k[2] = { 0x60, 0x1c }; + + #define MSG_OFFSET_OFFSET 3 + char dummy_boot_code[BOOTCODE_SIZE] = "\x0e" /* push cs */ +-- +1.9.1 + -- cgit v1.2.3