diff --git a/.idea/workspace.xml b/.idea/workspace.xml
index 573f093..e8398f5 100644
--- a/.idea/workspace.xml
+++ b/.idea/workspace.xml
@@ -20,8 +20,1083 @@
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -70,37 +1145,37 @@
- {
- "keyToString": {
- "ASKED_ADD_EXTERNAL_FILES": "true",
- "RunOnceActivity.OpenProjectViewOnStart": "true",
- "RunOnceActivity.ShowReadmeOnStart": "true",
- "RunOnceActivity.cidr.known.project.marker": "true",
- "SHARE_PROJECT_CONFIGURATION_FILES": "true",
- "WebServerToolWindowFactoryState": "false",
- "cf.first.check.clang-format": "false",
- "cidr.known.project.marker": "true",
- "last_opened_file_path": "C:/Qt/Qt5.14.2/Tools/mingw730_64/bin/mingw32-make.exe",
- "node.js.detected.package.eslint": "true",
- "node.js.detected.package.tslint": "true",
- "node.js.selected.package.eslint": "(autodetect)",
- "node.js.selected.package.tslint": "(autodetect)",
- "nodejs_package_manager_path": "npm",
- "settings.editor.selected.configurable": "File.Encoding",
- "structure.view.defaults.are.configured": "true",
- "vue.rearranger.settings.migration": "true"
+
+}]]>
+
-
-
+
@@ -188,11 +1263,11 @@
+
@@ -260,14 +1335,7 @@
-
-
-
- 1701738213205
-
-
-
- 1701738213205
+
1701738485690
@@ -605,7 +1673,14 @@
1704446603814
-
+
+ 1704447222941
+
+
+
+ 1704447222941
+
+
@@ -632,7 +1707,6 @@
-
@@ -657,7 +1731,8 @@
-
+
+
diff --git a/Makefile b/Makefile
index 4dae2fc..d437f39 100644
--- a/Makefile
+++ b/Makefile
@@ -56,7 +56,7 @@ ENABLE_AM_FIX_SHOW_DATA ?= 0
ENABLE_AGC_SHOW_DATA ?= 0
#############################################################
-OPENOCD = C:/openocd-win/bin/openocd.exe
+OPENOCD = openocd-win/bin/openocd.exe
TARGET = firmware
ifeq ($(ENABLE_CLANG),1)
@@ -429,7 +429,7 @@ ifdef MY_PYTHON
endif
-build: $(TARGET)
+build:clean $(TARGET)
$(OBJCOPY) -O binary $(TARGET) $(TARGET).bin
ifndef MY_PYTHON
$(info )
@@ -469,17 +469,6 @@ bsp/dp32g030/%.h: hardware/dp32g030/%.def
-include $(DEPS)
-ifdef OS
- ifeq ($(OS),Windows_NT)
- clean:
- .\clean.bat
- else
- clean:
- $(RM) $(call FixPath, $(TARGET).bin $(TARGET).packed.bin $(TARGET) $(OBJS) $(DEPS))
- doxygen:
- doxygen
- endif
-else
- clean:
- @echo "Unsupported OS. Please use this Makefile on Windows or Linux."
-endif
+clean:
+ $(RM) $(call FixPath, $(TARGET).bin $(TARGET).packed.bin $(TARGET) $(OBJS) $(DEPS))
+
diff --git a/dp32g030.cfg b/dp32g030.cfg
index c41a4f4..c38fc6d 100644
--- a/dp32g030.cfg
+++ b/dp32g030.cfg
@@ -21,7 +21,7 @@ swd newdap $_CHIP_NAME cpu -enable -expected-id $CPUTAPID
dap create $_CHIP_NAME.dap -chain-position $_CHIP_NAME.cpu
-# Set up the GDB target for the CPU, cortex_m is the CPU type,
+# Set up the GDB target for the CPU, cortex_m is the CPU type,
target create $_CHIP_NAME.cpu cortex_m -dap $_CHIP_NAME.dap
@@ -88,7 +88,7 @@ proc uv_wait_busy {} {
}
proc write_image {filename address} {
- global _SECTOR_SIZE
+ global _SECTOR_SIZE
set fs [file size $filename]
set fd [open $filename "rb"]
@@ -110,7 +110,7 @@ proc write_image {filename address} {
}
uv_clear_sectors [expr {(($fs+$_SECTOR_SIZE-1)&(0x10000000-$_SECTOR_SIZE))/($_SECTOR_SIZE/2)}]
uv_flash_unlock
-
+
set addr $address
while {![eof $fd]} {
set data [read $fd 4]
@@ -127,7 +127,7 @@ proc write_image {filename address} {
}
}
uv_flash_lock
-
+
close $fd
}
diff --git a/firmware b/firmware
deleted file mode 100644
index 4e08499..0000000
Binary files a/firmware and /dev/null differ
diff --git a/openocd-win/README.md b/openocd-win/README.md
new file mode 100644
index 0000000..4e7bbf2
--- /dev/null
+++ b/openocd-win/README.md
@@ -0,0 +1,14 @@
+# The xPack OpenOCD
+
+The **xPack OpenOCD** (formerly GNU MCU Eclipse OpenOCD)
+is the **xPack** version of **OpenOCD**,
+an open-source project.
+
+For more details, please read the corresponding release pages:
+
+-
+-
+
+Thank you for using open source software,
+
+Liviu Ionescu
diff --git a/openocd-win/bin/libftdi1.dll b/openocd-win/bin/libftdi1.dll
new file mode 100644
index 0000000..ae775e8
Binary files /dev/null and b/openocd-win/bin/libftdi1.dll differ
diff --git a/openocd-win/bin/libusb-1.0.dll b/openocd-win/bin/libusb-1.0.dll
new file mode 100644
index 0000000..f57958f
Binary files /dev/null and b/openocd-win/bin/libusb-1.0.dll differ
diff --git a/openocd-win/bin/openocd b/openocd-win/bin/openocd
new file mode 100644
index 0000000..f57eb3f
Binary files /dev/null and b/openocd-win/bin/openocd differ
diff --git a/openocd-win/bin/openocd.exe b/openocd-win/bin/openocd.exe
new file mode 100644
index 0000000..17e70e7
Binary files /dev/null and b/openocd-win/bin/openocd.exe differ
diff --git a/openocd-win/openocd/OpenULINK/ulink_firmware.hex b/openocd-win/openocd/OpenULINK/ulink_firmware.hex
new file mode 100644
index 0000000..efaea58
--- /dev/null
+++ b/openocd-win/openocd/OpenULINK/ulink_firmware.hex
@@ -0,0 +1,347 @@
+:040000000200713257
+:01000B0032C2
+:0100130032BA
+:01001B0032B2
+:0100230032AA
+:01002B0032A2
+:01003300329A
+:01003B003292
+:01004300328A
+:01004B003282
+:01005300327A
+:01005B003272
+:01006300326A
+:03006B000201107F
+:0300CA0002006EC3
+:03006E000201018B
+:1000CD00907F937404F0907F9C7495F0907F96745C
+:1000DD0090F0907F94E4F0907F9D747FF0907F97E7
+:1000ED00E4F0907F957440F0907F9E7442F0907F85
+:1000FD0098E4F0221200CD1204ADD2AF1208E090B8
+:10010D00000022C021C0E0C0F0C082C083C007C083
+:10011D0006C005C004C003C002C001C000C0D07538
+:10012D00D000AF9174EF5FF59112040C907FAB741A
+:10013D0001F0907FB4E04402F0D0D0D000D001D0D7
+:10014D0002D003D004D005D006D007D083D082D002
+:10015D00F0D0E0D02132323232323232323232C04D
+:10016D00E0C082C083C007C0D075D000D201AF916E
+:10017D0074EF5FF591907FA97404F0D0D0D007D0C3
+:10018D0083D082D0E032C0E0C082C083C007C0D02F
+:10019D0075D000D200AF9174EF5FF591907FAA7486
+:1001AD0004F0D0D0D007D083D082D0E032323232BA
+:1001BD0032323232323232AF82747F5FFE24F850E7
+:1001CD0003020278EE240A83F582EE240C83F58374
+:1001DD00E473EFF306192C3F52650101020202028E
+:1001ED000202907FB422EF30E7067DB67E7F800459
+:1001FD007DC67E7F8D828E8322EF30E7067DB87EB1
+:10020D007F80047DC87E7F8D828E8322EF30E7064E
+:10021D007DBA7E7F80047DCA7E7F8D828E8322EFA4
+:10022D0030E7067DBC7E7F80047DCC7E7F8D828E07
+:10023D008322EF30E7067DBE7E7F80047DCE7E7FFC
+:10024D008D828E8322EF30E7067DC07E7F80047D18
+:10025D00D07E7F8D828E8322EF30E7067EC27F7F38
+:10026D0080047ED27F7F8E828F832290000022AF0A
+:10027D008274105FFE74075F4206907FD7EEF074B4
+:10028D00204EF022907FE8E0C322907FE8E0FF60EF
+:10029D0005BF0246800A907FB4E0FF4401F0803A2A
+:1002AD00907FEAE0FEA3E0FF4E7027907FECE0FE2A
+:1002BD00A3E08E821201C4AE82AF83EE4F7002C3F3
+:1002CD00228E828F83E0FD5305FE8E828F83EDF0AB
+:1002DD008008907FB4E0FF4401F0D322907FE8E0E6
+:1002ED00FF6005BF02468010907FEAE0FEA3E0FFAD
+:1002FD00BE0239BF0036D322907FEAE0FEA3E0FFB5
+:10030D004E7027907FECE0FEA3E08E821201C4AE0A
+:10031D0082AF83EE4F7002C3228E828F83E0FD4346
+:10032D0005018E828F83EDF08002C322D322907F50
+:10033D00EAE0A3E0FF907FEAE0FDA3E07E00BF01CD
+:10034D0002800DBF02028021BF030280340203EC44
+:10035D007ED37F138F06907FD4EEF07ED37F137FF5
+:10036D0000907FD5EEF00203EE7EE57F138F0690B1
+:10037D007FD4EEF07EE57F137F00907FD5EEF08089
+:10038D0060907FECE0FEA3E0FF4E70187E057F14B9
+:10039D008F06907FD4EEF07E057F147F00907FD581
+:1003AD00EEF0803D907FECE0FEA3E0FFBE092EBF96
+:1003BD00042BED1475F002A42459F582741435F054
+:1003CD00F583E493FEA3E493FF8E048F058D0490D3
+:1003DD007FD4ECF07F00907FD5EEF08004C322C374
+:1003ED0022D32275828212027C75820212027C90C7
+:1003FD007FB87402F0907FC8E4F0907FC9F022902E
+:10040D007FE9E0FF24F3500122EFF5F0240B83F593
+:10041D0082E5F0241183F583E473414F5D655D72D0
+:10042D007B73889899A9AC0404040404040404049F
+:10043D0004040404120291500122907FB4E044019F
+:10044D00F022120297500122907FB4E04401F02275
+:10045D00907FB4E04401F0221202E94042907FB453
+:10046D00E04401F02222907FB4E04401F022120317
+:10047D003B402C907FB4E04401F0229013EAE493CA
+:10048D00907F00F0907FB57401F022229013F0E47C
+:10049D0093907F00F0907FB57401F0221203F0224B
+:1004AD00907FDE7404F0907FDF7404F0907FE0E4C1
+:1004BD00F0907FE1F0907FA17401F0907FAFE04468
+:1004CD0001F0907FAEE04401F0907FAD7404F090A8
+:1004DD007FAC7404F0D2E8907FD6740AF09000C817
+:0A04ED0012137C907FD67406F022F3
+:1013D30012011001FFFFFF4051C21027000101025B
+:1013E3000301090220000101048032090400000204
+:1013F300FFFFFF00070582024000000705020240CD
+:1014030000000403090414034F00700065006E001C
+:1014130055004C0049004E004B0014034F00700070
+:1014230065006E0055004C0049004E004B000E0352
+:101433003000300030003000300031001A034A0021
+:101443005400410047002000410064006100700027
+:0E14530074006500720009141D1431143F145A
+:1004F700E5080424C0F582E4347DF583E0FF30E1AC
+:1005070008907F96E0FE54EFF08F06EE30E00890FB
+:100517007F96E0FE547FF0EF30E308907F96E0FE91
+:100527004410F0EF30E208907F96E0FF4480F0221D
+:100537007F00E50824C0F582E4347DF583E0FE24DE
+:10054700D550030208A6EE240A83F582EE242F83F2
+:10055700F583E473B18AD7B0FAD3A6A6A6A6A6A652
+:10056700A6A6A6A6A6A6A6A6A6A6A6A6A6A6A6A624
+:10057700A6A6A6A621FA512A639CD5053493A205FF
+:1005870006050605060808080808080808080808F0
+:1005970008080808080808080808080808080806D6
+:1005A700060607070707080808087E05E508042464
+:1005B700C0F582E4347DF583E0FFE50804F5828524
+:1005C7000927C007C00612091DD006D0070208A8D0
+:1005D700E5080424C0F582E4347DF583E02405FEB4
+:1005E700E50804F582C007C006120BDED006D00767
+:1005F7000208A8E5080424C0F582E4347DF583E009
+:10060700FF2405FEE50804F58285093CC007C006FE
+:10061700120E79D006D0070208A87E02E508042446
+:10062700C0F582E4347DF583E0FD7402250824C01B
+:10063700F582E4347DF583E0F50A8D82C007C006B4
+:1006470012124AD006D0070208A87E02E508042441
+:10065700C0F582E4347DF583E0FC7D007402250853
+:1006670024C0F582E4347DF583E0FAE44204EA42EB
+:10067700058C828D83C007C0061211DDD006D00716
+:100687000208A87E05E5080424C0F582E4347DF558
+:1006970083E0FFE50804F58285092DC007C006122F
+:1006A7000A67D006D0070208A8E5080424C0F58227
+:1006B700E4347DF583E02405FEE50804F582C007F0
+:1006C700C006120D14D006D0070208A8E5080424B6
+:1006D700C0F582E4347DF583E0FF2405FEE50804D8
+:1006E700F582850943C007C006121013D006D0074C
+:1006F7000208A87E02E5080424C0F582E4347DF5EB
+:1007070083E0FB7402250824C0F582E4347DF58379
+:10071700E0F50A8B82C007C006121281D006D00707
+:100727000208A87E02E5080424C0F582E4347DF5BA
+:1007370083E0FC7D007402250824C0F582E4347D43
+:10074700F583E0FAE44204EA42058C828D83C00710
+:10075700C006121207D006D0070208A87E02E508D5
+:100767000424C0F582E4347DF583E0FC7D00740247
+:10077700250824C0F582E4347DF583E0FAE44204D9
+:10078700EA42058C828D83C007C006121349D00642
+:10079700D0070208A87E02E5080424C0F582E434E5
+:1007A7007DF583E0FC7D007402250824C0F582E412
+:1007B700347DF583E0FAE44204EA42058C828D83B6
+:1007C700C007C00612137CD006D0070208A87E0017
+:1007D7007F02C007C0061212CEAC82AD83D006D00E
+:1007E7000785098275837E8D03EBF0E509042400F4
+:1007F700F582E4347EF5837D00ECF00208A87E02E2
+:10080700E5080424C0F582E4347DF583E0FD740235
+:10081700250824C0F582E4347DF583E0F50A8D824E
+:10082700C007C006121311D006D00780747E05E5F5
+:10083700080424C0F582E4347DF583E0FD740225C5
+:100847000824C0F582E4347DF583E0F50A740325B6
+:100857000824C0F582E4347DF583E0F50B740425A4
+:100867000824C0F582E4347DF583E0F50C74052592
+:100877000824C0F582E4347DF583E0F50D8D82C050
+:1008870007C006121329D006D00780157E01C007BE
+:10089700C0061204F7D006D00780067E0180027ECC
+:1008A70000EF2509F509AD087F008E037C00EB2DCD
+:1008B700FDEC3FFF0DBD00010F907FC9E0FC7B0001
+:1008C700C3ED9CEF64808BF063F08095F04002D31A
+:1008D70022EE042508F508C32275080075090010E3
+:1008E700000280FB907F96E0FF547FF0C202200257
+:1008F70007120537920280F6907F96E0FF4480F05A
+:10090700E509600B907FB9E509F010010280FB90C3
+:100917007FC9E4F080C3E582FF24C0F582E4347D1B
+:10092700F583E0F528EF0424C0F582E4347DF583F0
+:10093700E0F52974022FFC24C0F582E4347DF583A9
+:10094700E0C4540FFB53030FEC24C0F582E4347D5D
+:10095700F583E0FC740F5CF52A74032F24C0F5823D
+:10096700E4347DF583E0FA74042F24C0F582E4347F
+:100977007DF583E0F52BEB60078A0A8B8212124A1A
+:10098700907F97E0FB5303F874044BFA7900A8288B
+:100997007C0018B8FF011C89067F00C3EE98EF643E
+:1009A700808CF063F08095F050347F007E00907F5C
+:1009B70097EBF0EFC313FF907F97EAF0907F99E0F2
+:1009C700FC30E5034307800EBE080040E1E5272918
+:1009D7002400F582E4347EF583EFF00980B0892C9A
+:1009E7007F00AC2A7A00C3EA95295040A8297900EC
+:1009F70018B8FF01198A057E00EDB50011EEB501A3
+:100A07000DEC600A4303021CE52BC313F52B907F03
+:100A170097EBF0EFC313FF907F9774044BF0907F31
+:100A270099E0FE30E5034307800A80BAAD297E00CE
+:100A37007408C39DFDE49EFE8DF005F0EF8002C3B0
+:100A470013D5F0FBFFE527252C2400F582E4347E3F
+:100A5700F583EFF0EC6008852B0A8C8202124A229C
+:100A6700E582FF24C0F582E4347DF583E0F52EEFBF
+:100A77000424C0F582E4347DF583E0F52F74022F5A
+:100A8700FC24C0F582E4347DF583E0C4540FFB53A6
+:100A9700030FEC24C0F582E4347DF583E0FC740F8A
+:100AA7005CF53074032F24C0F582E4347DF583E0D0
+:100AB700FA74042F24C0F582E4347DF583E0F53120
+:100AC700EB60078A0A8B82121281907F97E0FB53B3
+:100AD70003F874044BFA753200A82E7C0018B8FF8F
+:100AE700011CA9327E00C3E998EE64808CF063F0A4
+:100AF7008095F0504C7E007C00907F97EBF079005A
+:100B0700C3E9952250030980F7EEC313FE907F9740
+:100B1700EAF07900C3E9952250030980F7907F999D
+:100B2700E0F930E5034306800CBC080040CBE52D17
+:100B370025322400F582E4347EF583EEF005328019
+:100B4700987E00AA307900C3E9952F5056A82F7CCC
+:100B57000018B8FF011C89057F00EDB50011EFB53E
+:100B6700040DEA600A4303021AE531C313F5319015
+:100B77007F97EBF07F00C3EF952250030F80F7EECE
+:100B8700C313FE907F9774044BF07F00C3EF952249
+:100B970050030F80F7907F99E0FF30E5034306800D
+:100BA7000980A4AD2F7F007408C39DFDE49FFF8DCE
+:100BB700F005F0EE8002C313D5F0FBFEE52D2532DC
+:100BC7002400F582E4347EF583EEF0EA600885318F
+:100BD7000A8A8202128122E582FF24C0F582E43468
+:100BE7007DF583E0F533EF0424C0F582E4347DF529
+:100BF70083E0F53474022FFC24C0F582E4347DF5DC
+:100C070083E0C4540FFB53030FEC24C0F582E43494
+:100C17007DF583E0FC740F5CF53574032F24C0F574
+:100C270082E4347DF583E0FA74042F24C0F582E46E
+:100C3700347DF583E0F536EB600B8A0A8B82C007BB
+:100C470012124AD007907F97E0FB5303F97A00A866
+:100C5700337C0018B8FF011C8A017E00C3E998EEB7
+:100C670064808CF063F08095F05039EF2A240524D6
+:100C7700C0F582E4347DF583E0FE7C00EE30E005CC
+:100C870043030180068B0174FE59FB907F97EBF0BD
+:100C9700EEC313FE907F9774044BF00CBC08004022
+:100CA700DB0A80ABEF2A240524C0F582E4347DF506
+:100CB70083E0FEAF357C00C3EC95345044EE30E062
+:100CC7000543030180068B0274FE5AFBA9347A00A0
+:100CD70019B9FF011A8C007D00E8B50111EDB502C5
+:100CE7000DEF600A4303021FE536C313F536907F05
+:100CF70097EBF0EEC313FE907F9774044BF00C80D4
+:100D0700B6EF600885360A8F8202124A22E582F51D
+:100D17003724C0F582E4347DF583E0F538E5370400
+:100D270024C0F582E4347DF583E0F5397402253774
+:100D3700FC24C0F582E4347DF583E0C4540FFB53F3
+:100D4700030FEC24C0F582E4347DF583E0FC740FD7
+:100D57005CF53A7403253724C0F582E4347DF583C6
+:100D6700E0FA7404253724C0F582E4347DF583E086
+:100D7700F53BEB60078A0A8B82121281907F97E01E
+:100D8700FB5303F97A00A8387C0018B8FF011C8AC6
+:100D9700067F00C3EE98EF64808CF063F08095F0D7
+:100DA7005050E5372A240524C0F582E4347DF583C5
+:100DB700E0FF7E00EF30E00543030180068B0474FB
+:100DC700FE5CFB907F97EBF07C00C3EC9523500310
+:100DD7000C80F7EFC313FF907F9774044BF07C00F0
+:100DE700C3EC952350030C80F70EBE080040C50ADC
+:100DF7008094E5372A240524C0F582E4347DF58301
+:100E0700E0FFAE3A7C00C3EC9539505AEF30E0056D
+:100E170043030180068B0274FE5AFBA8397A001837
+:100E2700B8FF011A8C017D00E9B50011EDB5020D7F
+:100E3700EE600A4303021EE53BC313F53B907F9721
+:100E4700EBF07D00C3ED952350030D80F7EFC3133F
+:100E5700FF907F9774044BF07D00C3ED95235003FB
+:100E67000D80F70C80A0EE6008853B0A8E82021287
+:100E77008122E582FF24C0F582E4347DF583E0F525
+:100E87003DEF0424C0F582E4347DF583E0F53E743C
+:100E9700022FFC24C0F582E4347DF583E0C4540FAF
+:100EA700FB53030FEC24C0F582E4347DF583E0FCAB
+:100EB700740F5CF53F74032F24C0F582E4347DF58D
+:100EC70083E0FA74042F24C0F582E4347DF583E0CF
+:100ED700F540EB600B8A0A8B82C00712124AD007D3
+:100EE700907F97E0FB5303F97A00A83D7C0018B880
+:100EF700FF011C8A017E00C3E998EE64808CF063D1
+:100F0700F08095F0505CEF2A240524C0F582E43484
+:100F17007DF583E0F5417C007900E54130E005434C
+:100F2700030180068B0074FE58FB907F97EBF0E57A
+:100F370041C313F541907F9774044BF0ECC313FC46
+:100F4700907F99E0F830E50343048009B908004031
+:100F5700C9E53C2A2400F582E4347EF583ECF00AE7
+:100F670080888A01EF2A240524C0F582E4347DF5C0
+:100F770083E0F5417C00AF3F754200C3E542953EF3
+:100F87005057E54130E00543030180068B0074FEAE
+:100F970058FBA83E7D0018B8FF011DAA427E00EA53
+:100FA700B50011EEB5050DEF600A4303021FE540DA
+:100FB700C313F540907F97EBF0E541C313F54190DC
+:100FC7007F9774044BF0ECC313FC907F99E0FE30DD
+:100FD700E503430480054280A2AD3E7E007408C34A
+:100FE7009DFDE49EFE8DF005F0EC8002C313D5F065
+:100FF700FBFCE53C292400F582E4347EF583ECF024
+:10100700EF600885400A8F8202124A22E582F54482
+:1010170024C0F582E4347DF583E0F545E5440424F6
+:10102700C0F582E4347DF583E0F54674022544FC7F
+:1010370024C0F582E4347DF583E0C4540FFB5303E9
+:101047000FEC24C0F582E4347DF583E0FC740F5C7B
+:10105700F5477403254424C0F582E4347DF583E025
+:10106700FA7404254424C0F582E4347DF583E0F561
+:1010770048EB60078A0A8B82121281907F97E0FB08
+:101087005303F97A00A8457C0018B8FF011C8A06AB
+:101097007F00C3EE98EF64808CF063F08095F0508A
+:1010A70074E5442A240524C0F582E4347DF583E001
+:1010B700F5497E007C00E54930E0054303018006E1
+:1010C7008B0074FE58FB907F97EBF07800C3E89590
+:1010D7002450030880F7E549C313F549907F9774B7
+:1010E700044BF07800C3E8952450030880F7EEC35B
+:1010F70013FE907F99E0F830E5034306800CBC08A7
+:101107000040B3E5432A2400F582E4347EF583EEFC
+:10111700F00A02108C8A04E5442A240524C0F582CB
+:10112700E4347DF583E0F5497E00AA47754A00C39C
+:10113700E54A9546506DE54930E0054303018006D1
+:101147008B0174FE59FBA9467D0019B9FF011DA843
+:101157004A7F00E8B50111EFB5050DEA600A4303C0
+:10116700021AE548C313F548907F97EBF07F00C359
+:10117700EF952450030F80F7E549C313F549907F96
+:101187009774044BF07F00C3EF952450030F80F74B
+:10119700EEC313FE907F99E0FF30E5034306800519
+:1011A7004A808CAD467F007408C39DFDE49FFF8D88
+:1011B700F005F0EE8002C313D5F0FBFEE5432C24C7
+:1011C70000F582E4347EF583EEF0EA600885480A8C
+:1011D7008A8202128122AE82AF83907F97E0FD530D
+:1011E70005FB74044DFC7A007B00C3EA9EEB9F501D
+:1011F7000E907F97EDF0ECF00ABA00EE0B80EB2231
+:10120700AE82AF83907F97E0FD5305FB74044DFCDE
+:101217007A007B00C3EA9EEB9F5027907F97EDF003
+:101227007900C3E9952550030980F7907F97ECF083
+:101237007900C3E9952550030980F70ABA00D50B51
+:1012470080D222AF82907F97E0FE5306FB7D00C3DA
+:10125700ED9F5025E50A30E00543060280068E041F
+:1012670074FD5CFE907F97EEF0E50AC313F50A90D4
+:101277007F9774044EF00D80D622AF82907F97E05F
+:10128700FE5306FB7D00C3ED9F503BE50A30E005AA
+:1012970043060280068E0474FD5CFE907F97EEF095
+:1012A7007C00C3EC952650030C80F7E50AC313F5C1
+:1012B7000A907F9774044EF07C00C3EC9526500388
+:1012C7000C80F70D80C0227F00907F99E0FE30E50B
+:1012D700027F01907F99E0FE30E603430702907F8B
+:1012E7009AE0FE30E703430704907F9BE0FE30E57A
+:1012F70003430708907F9AE0FE53067F8F05E4FFBC
+:10130700FCEE4FF582EC4DF58322E582547FF4FF26
+:10131700907F97E05FF0747F550AFF907F97E04FCB
+:10132700F022858222850A23850B24850C25850DCD
+:10133700262200227E567F021EBEFF011FEE4F703F
+:10134700F722750A05750B001213A6AE82AF837CD0
+:10135700007D00C3EC9EED9F501AC007C006C00574
+:10136700C004121339D004D005D006D0070CBC0036
+:10137700E20D80DF22AE82AF837C007D00C3EC9E4E
+:10138700ED9F501AC007C006C005C00412133BD01A
+:0F13970004D005D006D0070CBC00E20D80DF2289
+:03004300021B009D
+:101B0000020110000201630002016400020165008D
+:101B1000020166000201670002016800020169001B
+:101B200002016A0002016B0002016C0002019300D5
+:101B30000201BA000201BB000201BC000201BD00AB
+:101B40000201BE000201BF000201C0000201C1008B
+:081B50000201C2000201C30002
+:1013A6007A10E4FBFCE58225E0F582E58333F583DC
+:1013B600EB33FBEC33FCEB950AF5F0EC950B4006B2
+:0913C600FCABF0438201DADD22E8
+:0600A000E478FFF6D8FD34
+:10007E007900E94400601B7A009014617800759253
+:10008E0020E493F2A308B800020592D9F4DAF275CF
+:02009E0092FFCF
+:1000A6007800E84400600A7900759220E4F309D8E4
+:1000B600FC7800E84400600C7900902000E4F0A38E
+:0400C600D8FCD9FA8F
+:0D00710075814A1213CFE582600302006E14
+:0413CF007582002201
+:00000001FF
diff --git a/openocd-win/openocd/README.md b/openocd-win/openocd/README.md
new file mode 100644
index 0000000..4e7bbf2
--- /dev/null
+++ b/openocd-win/openocd/README.md
@@ -0,0 +1,14 @@
+# The xPack OpenOCD
+
+The **xPack OpenOCD** (formerly GNU MCU Eclipse OpenOCD)
+is the **xPack** version of **OpenOCD**,
+an open-source project.
+
+For more details, please read the corresponding release pages:
+
+-
+-
+
+Thank you for using open source software,
+
+Liviu Ionescu
diff --git a/openocd-win/openocd/angie/angie_bitstream.bit b/openocd-win/openocd/angie/angie_bitstream.bit
new file mode 100644
index 0000000..aebd370
Binary files /dev/null and b/openocd-win/openocd/angie/angie_bitstream.bit differ
diff --git a/openocd-win/openocd/angie/angie_firmware.bin b/openocd-win/openocd/angie/angie_firmware.bin
new file mode 100644
index 0000000..da69631
Binary files /dev/null and b/openocd-win/openocd/angie/angie_firmware.bin differ
diff --git a/openocd-win/openocd/bin/libftdi1.dll b/openocd-win/openocd/bin/libftdi1.dll
new file mode 100644
index 0000000..ae775e8
Binary files /dev/null and b/openocd-win/openocd/bin/libftdi1.dll differ
diff --git a/openocd-win/openocd/bin/libusb-1.0.dll b/openocd-win/openocd/bin/libusb-1.0.dll
new file mode 100644
index 0000000..f57958f
Binary files /dev/null and b/openocd-win/openocd/bin/libusb-1.0.dll differ
diff --git a/openocd-win/openocd/bin/openocd b/openocd-win/openocd/bin/openocd
new file mode 100644
index 0000000..f57eb3f
Binary files /dev/null and b/openocd-win/openocd/bin/openocd differ
diff --git a/openocd-win/openocd/bin/openocd.exe b/openocd-win/openocd/bin/openocd.exe
new file mode 100644
index 0000000..17e70e7
Binary files /dev/null and b/openocd-win/openocd/bin/openocd.exe differ
diff --git a/openocd-win/openocd/contrib/60-openocd.rules b/openocd-win/openocd/contrib/60-openocd.rules
new file mode 100644
index 0000000..42b43f0
--- /dev/null
+++ b/openocd-win/openocd/contrib/60-openocd.rules
@@ -0,0 +1,243 @@
+# SPDX-License-Identifier: GPL-2.0-or-later
+
+# Copy this file to /etc/udev/rules.d/
+# If rules fail to reload automatically, you can refresh udev rules
+# with the command "udevadm control --reload"
+
+ACTION!="add|change", GOTO="openocd_rules_end"
+
+SUBSYSTEM=="gpio", MODE="0660", GROUP="plugdev", TAG+="uaccess"
+
+SUBSYSTEM!="usb|tty|hidraw", GOTO="openocd_rules_end"
+
+# Please keep this list sorted by VID:PID
+
+# opendous and estick
+ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="204f", MODE="666"
+
+# Original FT232/FT245 VID:PID
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", MODE="666"
+
+# Original FT2232 VID:PID
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="666"
+
+# Original FT4232 VID:PID
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6011", MODE="666"
+
+# Original FT232H VID:PID
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6014", MODE="666"
+# Original FT231XQ VID:PID
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", MODE="666"
+
+# DISTORTEC JTAG-lock-pick Tiny 2
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="8220", MODE="666"
+
+# TUMPA, TUMPA Lite
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="8a98", MODE="666"
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="8a99", MODE="666"
+
+# Marvell OpenRD JTAGKey FT2232D B
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="9e90", MODE="666"
+
+# XDS100v2
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="a6d0", MODE="666"
+# XDS100v3
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="a6d1", MODE="666"
+
+# OOCDLink
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="baf8", MODE="666"
+
+# Kristech KT-Link
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bbe2", MODE="666"
+
+# Xverve Signalyzer Tool (DT-USB-ST), Signalyzer LITE (DT-USB-SLITE)
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bca0", MODE="666"
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bca1", MODE="666"
+
+# TI/Luminary Stellaris Evaluation Board FTDI (several)
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bcd9", MODE="666"
+
+# TI/Luminary Stellaris In-Circuit Debug Interface FTDI (ICDI) Board
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bcda", MODE="666"
+
+# egnite Turtelizer 2
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bdc8", MODE="666"
+
+# Section5 ICEbear
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="c140", MODE="666"
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="c141", MODE="666"
+
+# Amontec JTAGkey and JTAGkey-tiny
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="cff8", MODE="666"
+
+# ASIX Presto programmer
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="f1a0", MODE="666"
+
+# Nuvoton NuLink
+ATTRS{idVendor}=="0416", ATTRS{idProduct}=="511b", MODE="666"
+ATTRS{idVendor}=="0416", ATTRS{idProduct}=="511c", MODE="666"
+ATTRS{idVendor}=="0416", ATTRS{idProduct}=="511d", MODE="666"
+ATTRS{idVendor}=="0416", ATTRS{idProduct}=="5200", MODE="666"
+ATTRS{idVendor}=="0416", ATTRS{idProduct}=="5201", MODE="666"
+
+# TI ICDI
+ATTRS{idVendor}=="0451", ATTRS{idProduct}=="c32a", MODE="666"
+
+# STMicroelectronics ST-LINK V1
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3744", MODE="666"
+
+# STMicroelectronics ST-LINK/V2
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3748", MODE="666"
+
+# STMicroelectronics ST-LINK/V2.1
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374b", MODE="666"
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3752", MODE="666"
+
+# STMicroelectronics STLINK-V3
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374d", MODE="666"
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374e", MODE="666"
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374f", MODE="666"
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3753", MODE="666"
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3754", MODE="666"
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3755", MODE="666"
+ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3757", MODE="666"
+
+# Cypress SuperSpeed Explorer Kit
+ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="0007", MODE="666"
+
+# Cypress KitProg in KitProg mode
+ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="f139", MODE="666"
+
+# Cypress KitProg in CMSIS-DAP mode
+ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="f138", MODE="666"
+
+# Infineon DAP miniWiggler v3
+ATTRS{idVendor}=="058b", ATTRS{idProduct}=="0043", MODE="666"
+
+# Hitex LPC1768-Stick
+ATTRS{idVendor}=="0640", ATTRS{idProduct}=="0026", MODE="666"
+
+# Hilscher NXHX Boards
+ATTRS{idVendor}=="0640", ATTRS{idProduct}=="0028", MODE="666"
+
+# Hitex STR9-comStick
+ATTRS{idVendor}=="0640", ATTRS{idProduct}=="002c", MODE="666"
+
+# Hitex STM32-PerformanceStick
+ATTRS{idVendor}=="0640", ATTRS{idProduct}=="002d", MODE="666"
+
+# Hitex Cortino
+ATTRS{idVendor}=="0640", ATTRS{idProduct}=="0032", MODE="666"
+
+# Altera USB Blaster
+ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6001", MODE="666"
+# Altera USB Blaster2
+ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6010", MODE="666"
+ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6810", MODE="666"
+
+# Ashling Opella-LD
+ATTRS{idVendor}=="0B6B", ATTRS{idProduct}=="0040", MODE="666"
+
+# Amontec JTAGkey-HiSpeed
+ATTRS{idVendor}=="0fbb", ATTRS{idProduct}=="1000", MODE="666"
+
+# SEGGER J-Link
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0101", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0102", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0103", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0104", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0105", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0107", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0108", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1010", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1011", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1012", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1013", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1014", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1015", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1016", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1017", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1018", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1020", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1051", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1055", MODE="666"
+ATTRS{idVendor}=="1366", ATTRS{idProduct}=="1061", MODE="666"
+
+# Raisonance RLink
+ATTRS{idVendor}=="138e", ATTRS{idProduct}=="9000", MODE="666"
+
+# Debug Board for Neo1973
+ATTRS{idVendor}=="1457", ATTRS{idProduct}=="5118", MODE="666"
+
+# OSBDM
+ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="0042", MODE="666"
+ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="0058", MODE="666"
+ATTRS{idVendor}=="15a2", ATTRS{idProduct}=="005e", MODE="666"
+
+# Olimex ARM-USB-OCD
+ATTRS{idVendor}=="15ba", ATTRS{idProduct}=="0003", MODE="666"
+
+# Olimex ARM-USB-OCD-TINY
+ATTRS{idVendor}=="15ba", ATTRS{idProduct}=="0004", MODE="666"
+
+# Olimex ARM-JTAG-EW
+ATTRS{idVendor}=="15ba", ATTRS{idProduct}=="001e", MODE="666"
+
+# Olimex ARM-USB-OCD-TINY-H
+ATTRS{idVendor}=="15ba", ATTRS{idProduct}=="002a", MODE="666"
+
+# Olimex ARM-USB-OCD-H
+ATTRS{idVendor}=="15ba", ATTRS{idProduct}=="002b", MODE="666"
+
+# ixo-usb-jtag - Emulation of a Altera Bus Blaster I on a Cypress FX2 IC
+ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="06ad", MODE="666"
+
+# USBprog with OpenOCD firmware
+ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c63", MODE="666"
+
+# TI/Luminary Stellaris In-Circuit Debug Interface (ICDI) Board
+ATTRS{idVendor}=="1cbe", ATTRS{idProduct}=="00fd", MODE="666"
+
+# TI XDS110 Debug Probe (Launchpads and Standalone)
+ATTRS{idVendor}=="0451", ATTRS{idProduct}=="bef3", MODE="666"
+ATTRS{idVendor}=="0451", ATTRS{idProduct}=="bef4", MODE="666"
+ATTRS{idVendor}=="1cbe", ATTRS{idProduct}=="02a5", MODE="666"
+
+# TI Tiva-based ICDI and XDS110 probes in DFU mode
+ATTRS{idVendor}=="1cbe", ATTRS{idProduct}=="00ff", MODE="666"
+
+# isodebug v1
+ATTRS{idVendor}=="22b7", ATTRS{idProduct}=="150d", MODE="666"
+
+# PLS USB/JTAG Adapter for SPC5xxx
+ATTRS{idVendor}=="263d", ATTRS{idProduct}=="4001", MODE="666"
+
+# Numato Mimas A7 - Artix 7 FPGA Board
+ATTRS{idVendor}=="2a19", ATTRS{idProduct}=="1009", MODE="666"
+
+# Ambiq Micro EVK and Debug boards.
+ATTRS{idVendor}=="2aec", ATTRS{idProduct}=="6010", MODE="666"
+ATTRS{idVendor}=="2aec", ATTRS{idProduct}=="6011", MODE="666"
+ATTRS{idVendor}=="2aec", ATTRS{idProduct}=="1106", MODE="666"
+
+# Espressif USB JTAG/serial debug units
+ATTRS{idVendor}=="303a", ATTRS{idProduct}=="1001", MODE="666"
+ATTRS{idVendor}=="303a", ATTRS{idProduct}=="1002", MODE="666"
+
+# ANGIE USB-JTAG Adapter
+ATTRS{idVendor}=="584e", ATTRS{idProduct}=="424e", MODE="666"
+ATTRS{idVendor}=="584e", ATTRS{idProduct}=="4255", MODE="666"
+ATTRS{idVendor}=="584e", ATTRS{idProduct}=="4355", MODE="666"
+ATTRS{idVendor}=="584e", ATTRS{idProduct}=="4a55", MODE="666"
+
+# Marvell Sheevaplug
+ATTRS{idVendor}=="9e88", ATTRS{idProduct}=="9e8f", MODE="666"
+
+# Keil Software, Inc. ULink
+ATTRS{idVendor}=="c251", ATTRS{idProduct}=="2710", MODE="666"
+ATTRS{idVendor}=="c251", ATTRS{idProduct}=="2750", MODE="666"
+
+# CMSIS-DAP compatible adapters
+ATTRS{product}=="*CMSIS-DAP*", MODE="666"
+
+LABEL="openocd_rules_end"
diff --git a/openocd-win/openocd/contrib/libdcc/README b/openocd-win/openocd/contrib/libdcc/README
new file mode 100644
index 0000000..1135b24
--- /dev/null
+++ b/openocd-win/openocd/contrib/libdcc/README
@@ -0,0 +1,18 @@
+This code is an example of using the openocd debug message system.
+
+Before the message output is seen in the debug window, the functionality
+will need enabling:
+
+From the gdb prompt:
+monitor target_request debugmsgs enable
+monitor trace point 1
+
+From the Telnet prompt:
+target_request debugmsgs enable
+trace point 1
+
+To see how many times the trace point was hit:
+(monitor) trace point 1
+
+Spen
+spen@spen-soft.co.uk
diff --git a/openocd-win/openocd/contrib/libdcc/dcc_stdio.c b/openocd-win/openocd/contrib/libdcc/dcc_stdio.c
new file mode 100644
index 0000000..9ad633b
--- /dev/null
+++ b/openocd-win/openocd/contrib/libdcc/dcc_stdio.c
@@ -0,0 +1,144 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+
+/***************************************************************************
+ * Copyright (C) 2008 by Dominic Rath *
+ * Dominic.Rath@gmx.de *
+ * Copyright (C) 2008 by Spencer Oliver *
+ * spen@spen-soft.co.uk *
+ * Copyright (C) 2008 by Frederik Kriewtz *
+ * frederik@kriewitz.eu *
+ ***************************************************************************/
+
+#include "dcc_stdio.h"
+
+#define TARGET_REQ_TRACEMSG 0x00
+#define TARGET_REQ_DEBUGMSG_ASCII 0x01
+#define TARGET_REQ_DEBUGMSG_HEXMSG(size) (0x01 | ((size & 0xff) << 8))
+#define TARGET_REQ_DEBUGCHAR 0x02
+
+#if defined(__ARM_ARCH_7M__) || defined(__ARM_ARCH_7EM__) || defined(__ARM_ARCH_6SM__)
+
+/* we use the System Control Block DCRDR reg to simulate a arm7_9 dcc channel
+ * DCRDR[7:0] is used by target for status
+ * DCRDR[15:8] is used by target for write buffer
+ * DCRDR[23:16] is used for by host for status
+ * DCRDR[31:24] is used for by host for write buffer */
+
+#define NVIC_DBG_DATA_R (*((volatile unsigned short *)0xE000EDF8))
+
+#define BUSY 1
+
+void dbg_write(unsigned long dcc_data)
+{
+ int len = 4;
+
+ while (len--)
+ {
+ /* wait for data ready */
+ while (NVIC_DBG_DATA_R & BUSY);
+
+ /* write our data and set write flag - tell host there is data*/
+ NVIC_DBG_DATA_R = (unsigned short)(((dcc_data & 0xff) << 8) | BUSY);
+ dcc_data >>= 8;
+ }
+}
+
+#elif defined(__ARM_ARCH_4T__) || defined(__ARM_ARCH_5TE__) || defined(__ARM_ARCH_5T__)
+
+void dbg_write(unsigned long dcc_data)
+{
+ unsigned long dcc_status;
+
+ do {
+ asm volatile("mrc p14, 0, %0, c0, c0" : "=r" (dcc_status));
+ } while (dcc_status & 0x2);
+
+ asm volatile("mcr p14, 0, %0, c1, c0" : : "r" (dcc_data));
+}
+
+#else
+ #error unsupported target
+#endif
+
+void dbg_trace_point(unsigned long number)
+{
+ dbg_write(TARGET_REQ_TRACEMSG | (number << 8));
+}
+
+void dbg_write_u32(const unsigned long *val, long len)
+{
+ dbg_write(TARGET_REQ_DEBUGMSG_HEXMSG(4) | ((len & 0xffff) << 16));
+
+ while (len > 0)
+ {
+ dbg_write(*val);
+
+ val++;
+ len--;
+ }
+}
+
+void dbg_write_u16(const unsigned short *val, long len)
+{
+ unsigned long dcc_data;
+
+ dbg_write(TARGET_REQ_DEBUGMSG_HEXMSG(2) | ((len & 0xffff) << 16));
+
+ while (len > 0)
+ {
+ dcc_data = val[0]
+ | ((len > 1) ? val[1] << 16: 0x0000);
+
+ dbg_write(dcc_data);
+
+ val += 2;
+ len -= 2;
+ }
+}
+
+void dbg_write_u8(const unsigned char *val, long len)
+{
+ unsigned long dcc_data;
+
+ dbg_write(TARGET_REQ_DEBUGMSG_HEXMSG(1) | ((len & 0xffff) << 16));
+
+ while (len > 0)
+ {
+ dcc_data = val[0]
+ | ((len > 1) ? val[1] << 8 : 0x00)
+ | ((len > 2) ? val[2] << 16 : 0x00)
+ | ((len > 3) ? val[3] << 24 : 0x00);
+
+ dbg_write(dcc_data);
+
+ val += 4;
+ len -= 4;
+ }
+}
+
+void dbg_write_str(const char *msg)
+{
+ long len;
+ unsigned long dcc_data;
+
+ for (len = 0; msg[len] && (len < 65536); len++);
+
+ dbg_write(TARGET_REQ_DEBUGMSG_ASCII | ((len & 0xffff) << 16));
+
+ while (len > 0)
+ {
+ dcc_data = msg[0]
+ | ((len > 1) ? msg[1] << 8 : 0x00)
+ | ((len > 2) ? msg[2] << 16 : 0x00)
+ | ((len > 3) ? msg[3] << 24 : 0x00);
+ dbg_write(dcc_data);
+
+ msg += 4;
+ len -= 4;
+ }
+}
+
+void dbg_write_char(char msg)
+{
+ dbg_write(TARGET_REQ_DEBUGCHAR | ((msg & 0xff) << 16));
+}
diff --git a/openocd-win/openocd/contrib/libdcc/dcc_stdio.h b/openocd-win/openocd/contrib/libdcc/dcc_stdio.h
new file mode 100644
index 0000000..3447b8c
--- /dev/null
+++ b/openocd-win/openocd/contrib/libdcc/dcc_stdio.h
@@ -0,0 +1,22 @@
+/* SPDX-License-Identifier: GPL-2.0-or-later */
+
+/***************************************************************************
+ * Copyright (C) 2008 by Dominic Rath *
+ * Dominic.Rath@gmx.de *
+ * Copyright (C) 2008 by Spencer Oliver *
+ * spen@spen-soft.co.uk *
+ ***************************************************************************/
+
+#ifndef DCC_STDIO_H
+#define DCC_STDIO_H
+
+void dbg_trace_point(unsigned long number);
+
+void dbg_write_u32(const unsigned long *val, long len);
+void dbg_write_u16(const unsigned short *val, long len);
+void dbg_write_u8(const unsigned char *val, long len);
+
+void dbg_write_str(const char *msg);
+void dbg_write_char(char msg);
+
+#endif /* DCC_STDIO_H */
diff --git a/openocd-win/openocd/contrib/libdcc/example.c b/openocd-win/openocd/contrib/libdcc/example.c
new file mode 100644
index 0000000..7c7d936
--- /dev/null
+++ b/openocd-win/openocd/contrib/libdcc/example.c
@@ -0,0 +1,45 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+
+/***************************************************************************
+ * Copyright (C) 2008 by Spencer Oliver *
+ * spen@spen-soft.co.uk *
+ * Copyright (C) 2008 by Frederik Kriewtz *
+ * frederik@kriewitz.eu *
+ ***************************************************************************/
+
+#include "dcc_stdio.h"
+
+/* enable openocd debugmsg at the gdb prompt:
+ * monitor target_request debugmsgs enable
+ *
+ * create a trace point:
+ * monitor trace point 1
+ *
+ * to show how often the trace point was hit:
+ * monitor trace point
+*/
+
+int main(void)
+{
+ dbg_write_str("hello world");
+
+ dbg_write_char('t');
+ dbg_write_char('e');
+ dbg_write_char('s');
+ dbg_write_char('t');
+ dbg_write_char('\n');
+
+ unsigned long test_u32 = 0x01234567;
+ dbg_write_u32(&test_u32, 1);
+
+ static const unsigned short test_u16[] = {0x0123, 0x4567, 0x89AB, 0xCDEF, 0x0123, 0x4567, 0x89AB, 0xCDEF};
+ dbg_write_u16(test_u16, 8);
+
+ static const unsigned char test_u8[] = {0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88, 0x99, 0xAA, 0xBB, 0xCC, 0XDD, 0xEE, 0xFF};
+ dbg_write_u8(test_u8, 16);
+
+ while(1)
+ {
+ dbg_trace_point(0);
+ }
+}
diff --git a/openocd-win/openocd/distro-info/CHANGELOG.md b/openocd-win/openocd/distro-info/CHANGELOG.md
new file mode 100644
index 0000000..fdbf8ca
--- /dev/null
+++ b/openocd-win/openocd/distro-info/CHANGELOG.md
@@ -0,0 +1,628 @@
+# Change & release log
+
+Entries in this file are in reverse chronological order.
+
+## 2023-09-04
+
+* 8186554 package-lock.json update
+* bdd0375 package.json: use github: helper
+* 43fb8ee package.json: remove pkg-config from deps
+* 99526e9 versioning.sh: bump deps
+* 6743160 versioning.sh: update for latest commit
+* f8e0808 openocd.sh: run_verbose diff
+* c8379f3 CHANGELOG update
+* 5a3f058 README updates
+* 88994ee package.json: bump deps
+* 012f130 dot.*ignore update
+* d3d94dd re-generate workflows
+
+## 2023-09-03
+
+* 70caa99 package.json: bump deps
+
+## 2023-08-28
+
+* b3de5ce READMEs update
+
+## 2023-08-25
+
+* e0e3c8e package.json: rm xpack-dev-tools-build/*
+* e4c5804 package.json: bump deps
+
+## 2023-08-21
+
+* e13385a READMEs update
+* 82b20e2 package.json: bump deps
+
+## 2023-08-19
+
+* c1aa321 READMEs update
+* f2f7239 package.json: bump deps
+
+## 2023-08-15
+
+* 8dd0d21 re-generate workflows
+* f959671 README-MAINTAINER rename xbbla
+* 60ff8ef package.json: rename xbbla
+* a20733a package.json: bump deps
+* 27277ab READMEs update
+* ddcc6a0 package.json: bump deps
+
+## 2023-08-05
+
+* 378cbda READMEs update
+
+## 2023-08-04
+
+* 3c3e82e READMEs update
+* 835a8d2 READMEs update
+* 1188627 READMEs update
+
+## 2023-08-03
+
+* 92f9c49 package.json: reorder build actions
+* 7a5f3eb READMEs update
+* 5be3464 package.json: bump deps
+
+## 2023-07-28
+
+* 0f34460 READMEs update
+* 3e3bceb READMEs update
+* f743191 package.json: bump deps
+* bbd6eb2 package.json: liquidjs --context --template
+* 65ea0a9 scripts cosmetics
+* cb1d34c re-generate workflows
+* 629a380 READMEs update
+* 9cdb678 package.json: minXpm 0.16.3 & @xpack-dev-tools/xbb-helper
+* 40dfb2a READMEs update
+* 77b1b4b package.json: bump deps
+
+## 2023-07-26
+
+* 60a3907 package.json: move scripts to actions
+* c26109e package.json: update xpack-dev-tools path
+* 193f4d5 READMEs update xpack-dev-tools path
+* ef9e796 .vscode/launch.json update
+* fc6ac8c body-jekyll update
+* 2774d4e READMEs update
+
+## 2023-07-17
+
+* 03631fd package.json: bump deps
+* 05f05aa package.json: add -develop-debug actions
+
+## 2023-07-08
+
+* 08fe285 versioning.sh: add 0.12.0-2 commit id
+* 592885b ~/Work/xpack-dev-tools/
+* 5423546 prepare v0.12.0-2
+
+## 2023-04-19
+
+* a6ed8e5 Merge pull request #26 from zqb-all/fix_typo
+* 2aab171 README: fix typo
+
+## 2023-03-31
+
+* 574ff3c README-DEVELOP.md: update
+* 3909232 README-DEVELOP.md: update
+* 63a1335 README-DEVELOP.md: update deep-clean
+* 8e35423 openocd.sh: --enable-internal-libjaylink
+
+## 2023-03-28
+
+* 068dc2d README-DEVELOPER update
+
+## 2023-03-27
+
+* d531f0b README-DEVELOPER update
+* 180d15d README-DEVELOPER update
+
+## 2023-03-25
+
+* 7f7d1db README update
+* c1891fb add README-DEVELOPER.md
+* 29c93c1 READMEs update
+* 26ecf82 READMEs update prerequisites
+
+## 2023-03-24
+
+* 85dfffc package.json: mkdir -pv cache
+* b5081e9 README update
+* c312703 .vscode/settings.json: ignoreWords
+* 07cb567 README-MAINTAINER.md update
+* e320656 README-MAINTAINER: update prerequisites
+
+## 2023-02-22
+
+* 33e43d0 READMEs update
+
+## 2023-02-14
+
+* 32fbd24 body-jekyll update
+
+* ebf9368 package.json: update Work/xpacks
+* 73b0ea7 READMEs update
+
+## 2023-02-07
+
+* 65251a2 READMEs update
+* 813a0e2 package.json: bump deps & reorder git-log
+* 68ba49c versioning.sh: update for https
+* 1ed35c9 body-jekyll update
+
+## 2023-01-30
+
+* 65cdee4 0.12.0-1.1
+* 85ad2d2 CHANGELOG: publish npm v0.12.0-1.1
+* f82dae3 package.json: update urls for 0.12.0-1.1 release
+* e79ff4c READMEs updates
+* af00549 body-jekyll update
+* 8022518 CHANGELOG update
+* b6da41e .vscode/settings.json: ignoreWords
+* v0.12.0-1 released
+* f37a409 README update
+* 3b8d65d remove unused XBB_BRANDING
+* bd6d610 openocd.sh: move docs to LIBRARIES
+* 381fa84 versioning.sh: move GIT_URL defs
+* e0f02bf add .vscode/launch.json
+* 61987a9 package.json: bump deps
+* 73ca561 README updates
+* 8bb511b openocd.sh: re-enable parallel build
+* 65aee84 openocd.sh: use only -ludev on linux
+* 2d369c1 openocd.sh: apply patches locally
+* 427c081 .vscode/settings.json: ignoreWords
+* e619b4d prepare v0.12.0-1
+
+## 2023-01-29
+
+* v0.12.0-1 prepared
+* 02486b4 re-generate workflows
+* 53c05f2 package.json: bump deps
+
+## 2023-01-28
+
+* bcce8c3 versioning.sh: use versioning functions
+* 949bed6 README-MAINTAINER remove caffeinate xpm
+
+## 2023-01-27
+
+* 3b80250 package.json: reorder scripts
+
+## 2023-01-24
+
+* b16e64a README updates
+
+## 2023-01-22
+
+* ac30acd README update
+
+## 2023-01-11
+
+* 4b20bb2 cosmetize xbb_adjust_ldflags_rpath
+
+## 2023-01-09
+
+* ceef268 package.json: bump deps
+* 777c73c package.json: loglevel info
+* 201a58c versioning.sh: add comment before *_installed_bin
+
+## 2023-01-02
+
+* ae9ffd4 package.json: add gcc to windows deps
+
+## 2023-01-01
+
+* 528e1f2 package.json: pass xpm version & loglevel
+* 099a8d5 README update
+
+## 2022-12-30
+
+* fef7655 README-MAINTAINER: xpm run install
+* 3556cba package.json: bump deps
+* f8576b0 versioning.sh: regexp
+
+## 2022-12-27
+
+* d8e72c0 README update
+* 30753c6 echo FUNCNAME[0]
+* 62b1cd0 use autotools_build
+* d588a1f move *_installed_bin to versions.sh
+* c7a592c re-generate from templates
+* 927f3a9 cosmetics: move versions to the top
+
+## 2022-12-26
+
+* 0258972 README updates
+
+## 2022-12-25
+
+* fce7aa2 README update
+* 12952ed versioning.sh: remove explicit xbb_set_executables_install_path
+* 8e83ec7 package.json: add m4 dep
+* 975d1d4 versioning.sh: add comment M4
+
+## 2022-12-24
+
+* 5452b76 README updates
+* 241998a openocd.sh: pass path to test
+* 719eb0a updates for xbb v 5.x
+* 54da172 test.sh: update
+* 3c40213 package.json: update
+* 23269b2 package.json: bump deps
+* 0e195e4 re-generate from templates
+* d93b8ef rename functions
+
+## 2022-12-12
+
+* d41e004 package.json: add caffeinate builds for macOS
+* cca6fcc versioning.sh: use XBB_REQUESTED_*
+
+## 2022-11-18
+
+* e92dd4c .vscode/settings.json: watcherExclude
+
+## 2022-10-28
+
+* 1e9b995 cleanups
+* 6b1c896 tests/run.sh: cosmetics
+* 6237479 README updates
+* 4b65463 README update
+* d713f53 openocd.sh: fix test
+* 33eebca .gitignore xpacks
+
+## 2022-10-27
+
+* 9757baa package.json: bump deps
+* 08b7b90 package.json: bump deps
+* a5e069e package.json: bump deps
+* b2ef4b3 package.json: bump deps
+* b5a9472 versioning.sh: adjust LD_LIBRARY_PATH for libusb1
+* 89e5a13 openocd.sh: set -rpath
+* f40f094 bring build_pkg_config back for macOS
+* af34c4f package.json: add ninja to deps
+* 15f9671 package.json: add cmake to deps
+* ac46aa1 run.sh: cleanups
+* 14be2a2 application.sh: remove pkg-config coreutils
+* 582c24f versioning.sh: remove build_pkg_config
+* 0f5a08d versioning.sh: build_application_versioned_components
+* cc1087a README updates
+* 1183e66 package.json: cp build.sh & test.sh
+* ba1fd0b package.json: bump deps & cleanups
+* cf2b53f .vscode/settings.json: ignoreWords
+* 14504f4 re-generate workflows & scripts
+
+## 2022-10-23
+
+* 821a513 package.json: bump deps
+* f332865 package.json: bump deps
+* c4b9381 READMEs update
+* fb51384 package.json: add devDep realpath
+* 0a13362 package.json: reorder actions
+* c9f1e2e versioning.sh: remove build_coreutils
+* 4a05989 cosmetics
+* d19ddee test.sh: update
+* 19956f9 build.sh: update
+* d328879 rename application.sh
+
+## 2022-10-19
+
+* b853e1c READMEs updates
+* 8b816e4 versioning.sh: add XBB_COREUTILS_INSTALL_REALPATH_ONLY
+* cd61164 updates for xbb v4.0
+* 88d94dc remove patches & pkgconfig (moved to helper)
+* 1a676ae re-generate workflows
+
+## 2022-10-18
+
+* d15ec21 remove submodule
+
+## 2022-10-04
+
+* 101682e README-RELEASE update for bullet lists in CHANGELOG
+
+## 2022-09-25
+
+* 30cf7d8 README-RELEASE update
+
+## 2022-09-17
+
+* d2d81ea package.json: remove -ia32
+* 049765b README update
+* 34d14ba README-BUILD update
+
+## 2022-09-03
+
+* 72e5bc5 READMEs updates
+
+## 2022-09-01
+
+* v0.11.0-5 published on npmjs.com
+* v0.11.0-5 released
+
+## 2022-03-25
+
+* v0.11.0-4 published on npmjs.com
+* v0.11.0-4 published
+
+## 2021-12-07
+
+* v0.11.0-3 published on npmjs.com
+* v0.11.0-3 released
+
+## 2021-11-21
+
+* v0.11.0-3 prepared
+* update for Apple Silicon
+
+## 2021-10-16
+
+* v0.11.0-2 published on npmjs.com
+* v0.11.0-2 released
+
+## 2021-08-27
+
+* v0.11.0-2 prepared
+* [#10] - fix copying license sub-folders
+
+## 2021-03-15
+
+* v0.11.0-1 prepared
+* update to upstream 0.11
+* [#3] - remove deprecated --enable-oocd_trace
+* v0.11.0-1 published
+* v0.11.0-1.1 published on npmjs.com
+
+## 2020-10-13
+
+* v0.10.0-15 published
+* v0.10.0-15.1 published on npmjs.com
+
+## 2020-06-27
+
+* v0.10.0-13.2 published on npmjs.com
+
+## 2020-06-26
+
+* v0.10.0-14.2 published on npmjs.com (wrong skip:3)
+* v0.10.0-14.1 published on npmjs.com (wrong .tgz extension)
+* v0.10.0-14 released
+* add binaries for Arm 32/64-bit
+* update for XBB v3.2
+* based on openocd.git 8833c889da07eae750bcbc11215cc84323de9b74 from June 23rd, 2020
+
+## 2020-03-26
+
+* update for XBB v3.1
+* based on openocd.git d9ffe75e257aa4005dd34603860e45c57b1765b6
+
+## 2019-07-27
+
+* bump v0.10.0-14
+* add support for Arm binaries
+* based on openocd.git e1e63ef30cea39aceda40daf194377c89c570101
+
+## 2019-07-20
+
+* v0.10.0-13.1 published on npmjs.com
+
+## 2019-07-17
+
+* v0.10.0-13 released
+
+## 2019-07-08
+
+* update to 263deb380 from 7 Jul 2019
+
+___
+
+# Historical GNU MCU Eclipse change log
+
+## 2019-04-23
+
+* v0.10.0-12-20190423 released
+
+## 2019-04-09
+
+* prepare - v0.10.0-12
+* update to latest master from Apr 7th, 2019
+* update LIBUSB1_VERSION="1.0.22"
+* update LIBFTDI_VERSION="1.4"
+
+## 2019-01-18
+
+* v0.10.0-11-20190118 released
+* update to latest master from Jan 16, 2019
+* RISC-V specific patches were removed, only upstreamed functionality retained.
+
+## 2018-10-20
+
+* v0.10.0-10-20181020 released
+* rerun, to fix the macOS file dates
+* update the -bit to singular
+
+## 2018-10-16
+
+* v0.10.0-9-20181016 released
+* update to latest master
+* update to latest RISC-V
+* revert some of the RISC-V patches in the common files
+
+## 2018-06-19
+
+* update to latest RISC-V commits, including semihosting
+
+## 2018-06-12
+
+* use separate README-*.md files
+* update to latest commits, which include new semihosting (OpenOCD June 6th, RISC-V June 12th)
+
+## 2018-05-12
+
+* v0.10.0-8-20180512 released
+* use new build scripts based on XBB
+* update to latest commits (OpenOCD April 27th, RISC-V May 8th)
+
+## 2018-01-23
+
+* v0.10.0-7-20180123 released
+* move semihosting code to separate files
+* use them in RISC-V and ARM
+* add 'arm semihosting_resexit enable' to allow exit() to return
+
+## 2018-01-12
+
+* v0.10.0-6-20180112 released
+* update to master from Dec 20
+* update to riscv from Dec 29
+* remove the patch to hide the CSRs, the new version displays only a limited number of them.
+* remove the `remote_bitbang.c` patch, since it compiles ok on mingw-w64
+* the SiFive board scripts were upstreamed to the RISC-V fork
+
+## 2017-11-10
+
+* v0.10.0-5-20171110-dev released
+* update to master from Oct 2
+* update to riscv from Nov 4
+* target.c & riscv/riscv-0[13].c: hide the 4096 CSRs from `monitor reg`
+* update the SiFive board script files
+* revert the risc-v changes in `remote_bitbang.c`, since they break the build on mingw-w64
+
+## 2017-10-04
+
+* v0.10.0-4-20171004-*-dev released
+* update to master from Aug 10
+* update to riscv fom Oct 2
+* gdb_server.c: workaround to gdb errors; disable passing errors back to gdb since this risc-v change breaks other targets.
+
+## 2017-08-25
+
+* v0.10.0-3-20170826-*-dev released
+* merge RISC-V tag v20170818
+* server.c: fix clang warning in getsockname()
+
+## 2017-07-03
+
+* update build script to use Debian 9 Docker containers
+
+## 2017-06-22
+
+* v0.10.0-2-20170622-1535-dev released
+* merge RISC-V tag v20170621
+
+## 2017-06-15
+
+* move the build specific gnu-mcu-eclipse folder to a separate openocd-build project
+
+## 2017-06-12
+
+* add --enable-riscv and #if BUILD_RISCV
+* add --enable-branding
+
+## 2017-06-07
+
+* v0.10.0-1-20170607-2132-dev released
+* add sifive-* configuration files to the board folder
+* 60-openocd.rules: simplify access rights
+* merge RISC-V commit '11008ba' into gnu-mcu-eclipse-dev
+
+## 2017-06-06
+
+* rename gnu-mcu-eclipse & content
+
+## 2017-06-04
+
+* merge original branch 'master' from 2017-06-02 into gnuarmeclipse-dev.
+* merge RISC-V commit '51ab5a0' from 2017-05-26 into gnuarmeclipse-dev
+
+## 2017-01-24
+
+* v0.10.0-20170124* released (stable)
+* merge original 0.10.0, override local relative path processing
+
+## 2016-10-28
+
+* v0.10.0-20161028*-dev released
+
+## 2016-10-20
+
+* nsi file: add InstallDir; silent install should honour /D
+
+## 2016-01-10
+
+* v0.10.0-20160110*-dev released
+
+## 2015-10-28
+
+* v0.10.0-20151028*-dev released
+
+## 2015-05-19
+
+* v0.9.0-20150519*-dev released
+* remove @raggedright from openocd.texi
+
+## 2015-05-11
+
+* the three separate build scripts were deprecated, and a single script,
+using Docker, was added to the main gnuarmeclipse-se.git/scripts.
+
+* the greeting shows 32-bits or 64-bits (plural for bits). (wrong!)
+
+## 2015-03-24
+
+* v0.9.0-20150324*-dev released
+* v0.8.0-20150324* released
+
+## 2015-03-22
+
+* the NSIS script was fixed to prevent removing the keys when
+uninstalling an older version.
+
+## 2015-03-20
+
+* v0.9.0-20150320*-dev released
+* v0.8.0-20150320* released
+
+## 2015-03-18
+
+* the build scripts were extended to generate both the stable and the
+development version.
+
+* multiple versions of the package can be installed in separate folders,
+named using the version.
+
+* for Windows, more accurate keys were stored, so remember separate locations
+for 32/64-bit versions.
+
+## 2015-01-31
+
+* v0.8.0-20150131* released
+
+## 2015-01-30
+
+* gnuarmeclipse
+
+All GNU ARM Eclipse OpenOCD build related files were grouped under this folder.
+
+* README.md
+
+Markdown files were added in all new folders, to improve the look when browsed
+in the SourceForge Git web browser.
+
+## 2015-01-19
+
+* v0.8.0-20150119* released
+
+## 2015-01-12
+
+* src/openocd.c
+
+Add branding 'GNU ARM Eclipse' to the greeting message, to
+more easily identify this custom version.
+
+* helper/options.c
+
+Update the logic used to locate the 'scripts' folder, by
+using the argv[0], as on Windows. The logic is a bit more
+complicated, to accommodate 3 cases (no path, relative path
+and absolute path).
diff --git a/openocd-win/openocd/distro-info/licenses/autoconf-2.71/AUTHORS b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/AUTHORS
new file mode 100644
index 0000000..b6a63f2
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/AUTHORS
@@ -0,0 +1,128 @@
+Authors of GNU Autoconf.
+
+Autoconf was originally written by David MacKenzie, with help from
+François Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor, Roland
+McGrath, Noah Friedman, david d zuhn, and many others.
+
+Ben Elliston next took over the maintenance, facing a huge Autoconf
+backlog that had been piling up since the departure of David. Other
+maintainers have included Akim Demaille, Jim Meyering, Alexandre
+Oliva, and Tom Tromey, with plenty of contributions from Lars J. Aas,
+Mo DeJong, Steven G. Johnson, Matthew D. Langston, Pavel Roskin.
+
+Today, the primary maintainers are Paul Eggert and Eric Blake, with
+help from Ralf Wildenhues, Stepan Kasal, and Benoit Sigoure. Many
+other people have contributed, as listed in the THANKS file.
+
+The following contributors have warranted legal paper exchanges with
+the Free Software Foundation for their contributions to GNU Autoconf.
+This list results from searching for AUTOCONF in the file
+/gd/gnuorg/copyright.list on the fencepost.gnu.org machine.
+
+David J. MacKenzie djm@gnu.org 1991-07-09
+James L. Avera ? 1993-10-04
+Roland McGrath roland@gnu.org 1994-06-24
+Noah Friedman friedman@gnu.org 1994-07-15
+Francois Pinard pinard@iro.umontreal.ca 1997-02-02
+Thomas E. Dickey dickey@clark.net 1998-01-11
+Matthew D. Langston langston@slac.stanford.edu 1998-09-29
+Mark Elbrecht snowball3@usa.net 1999-01-11
+Akim Demaille akim@gnu.org 1999-02-02
+Pavel Roskin pavel_roskin@geocities.com 1999-02-24
+Alexandre Oliva oliva@dcc.unicamp.br 1999-03-26
+Thomas Tanner tanner@ffii.org 1999-06-23
+Gary V. Vaughan gary@gnu.org 2000-01-10
+Joseph Samuel Myers jsm28@cam.ac.uk 2000-03-13
+Lars J. Aas larsa@sim.no 2000-07-07
+Morten Eriksen mortene@sim.no 2000-07-07
+Martin Wilck martin@tropos.de 2000-07-12
+Paul Eggert eggert@twinsun.com 2000-10-13
+Alexandre Duret-Lutz duret_g@epita.fr 2001-02-12
+Tim Van Holder tim.van.holder@pandora.be 2001-02-13
+Christian Marquardt marq@gfz-potsdam.de 2001-02-19
+Derek R. Price dprice@collab.net 2001-03-12
+Markus Kuhn Markus.Kuhn@cl.cam.ac.uk 2001-07-07
+Erik Lindahl erik@theophys.kth.se 2001-08-22
+Hans-Peter Nilsson hp@bitrange.com 2001-10-24
+Paul Wagland paul@wagland.net 2001-10-30
+Paolo Bonzini bonzini@gnu.org 2001-11-08
+Nishio Futoshi fut_nis@d3.dion.ne.jp 2002-01-23
+Federico G. Schwindt fgsch@openbsd.org 2002-05-21
+Mark D. Roth roth@feep.net 2002-05-28
+Greg McGary greg@mcgary.org 2002-06-05
+Charles Stephen Wilson cwilson@ece.gatech.edu 2002-07-25
+Robert Bernstein rocky@panix.com 2002-08-20
+Assar Westerlund assar@kth.se 2002-09-13
+Scott Bambrough sbambrough@storm.ca 2002-09-24
+Richard Dawe rich@phekda.freeserve.co.uk 2003-01-23
+Andreas Buening andreas.buening@nexgo.de 2003-02-18
+Raja R. Harinath harinath@acm.org 2003-02-25
+Ilya Zakharevich ilya@Math.Berkeley.EDU 2003-03-11
+Kaveh Ghazi ghazi@caip.rutgers.edu 2003-03-15
+Felix Lee felix.1@canids.net 2003-03-31
+Nathanael Nerode neroden@twcny.rr.com 2003-04-04
+Gavin Puche user42@zip.com.au 2003-04-10
+Steven Glenn Johnson stevenj@alum.mit.edu 2003-07-26
+Bernardo Innocenti bernie@codewiz.org 2003-07-31
+Albert Marsden Chin-A-Young china@thewrittenword.com 2003-08-02
+Ralf Corsepius corsepiu@faw.uni-ulm.de 2003-09-03
+Scott Remnant scott@netsplit.com 2003-10-04
+Daniel Jacobowitz dan@debian.org 2003-10-17
+Kevin Fleming kpfleming@backtobasicsmgmt.com 2003-11-17
+John David Anglin dave.anglin@nrc-cnrc.gc.ca 2004-01-21
+Eric Sunshine sunshine@sunshineco.com 2004-01-25
+Ralf Wildenhues Ralf.Wildenhues@gmx.de 2004-02-12
+Noah Jeffrey Misch noah@cs.caltech.edu 2004-07-05
+Thorsten Glaser tg@66h.42h.de 2004-10-11
+Peter O'Gorman peter@pogma.com 2004-11-14
+Toshio Ernie Kuratomi toshio@tiki-lounge.com 2004-11-17
+Roger Leigh rleigh@whinlatter.ukfsn.org 2004-12-09
+Ian Lance Taylor ian@airs.com 2004-12-22
+Daniel Manthey dan_manthey@partech.com 2005-02-14
+Gregorio Guidi greg_g@gentoo.org 2005-03-03
+Bruno Haible bruno@clisp.org 2005-06-12
+Toby Oliver Hilary White tow21@cam.ac.uk 2005-10-18
+Eric Benjamin Blake ebb9@byu.net 2006-01-18
+Romain Lenglet romain.lenglet@laposte.net 2006-02-10
+Markus Duft markus.duft@salomon.at 2006-08-03
+Robert Schiele rschiele@gmail.com 2006-09-12
+Joel Edward Denny jdenny@clemson.edu 2006-09-15
+Helge Deller deller@gmx.de 2007-02-01
+Benoit Sigoure tsuna@lrde.epita.fr 2007-04-20
+Bob Proulx bob@proulx.com 2007-06-25
+Bruce Korb bkorb@gnu.org 2008-05-06
+Benjamin Pfaff blp@gnu.org 2008-09-29
+Peter Breitenlohner peb@mppmu.mpg.de 2009-08-18
+Stefano Lattarini stefano.lattarini@gmail.com 2009-10-01
+Reuben Thomas rrt@sc3d.org 2010-03-10
+Peter Rosin peda@lysator.liu.se 2010-07-21
+John W. Eaton jwe@gnu.org 2010-11-05
+Christopher Hulbert cchgroupmail@gmail.com 2010-11-09
+Tim Rice tim@multitalents.net 2011-01-24
+KO Myun-Hun komh78@gmail.com 2011-04-05
+Christian Roessel christian.roessel@gmx.de 2011-08-26
+Nicolai Stange nicolai.stange@zmaw.de 2011-10-13
+Zachary Weinberg zackw@panix.com 2013-06-11
+
+========================================================================
+
+Local Variables:
+mode: text
+coding: utf-8
+End:
+
+Copyright (C) 1996, 2000-2001, 2005, 2007-2017, 2020-2021 Free Software
+Foundation, Inc.
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see .
diff --git a/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYING b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYING
new file mode 100644
index 0000000..7b63d8e
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYING
@@ -0,0 +1,338 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
diff --git a/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYING.EXCEPTION b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYING.EXCEPTION
new file mode 100644
index 0000000..7d5c24e
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYING.EXCEPTION
@@ -0,0 +1,43 @@
+ AUTOCONF CONFIGURE SCRIPT EXCEPTION
+ Version 3.0, 18 August 2009
+
+ Copyright (C) 2009 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+This Exception is an additional permission under section 7 of the GNU
+General Public License, version 3 ("GPLv3"). It applies to a given
+file that bears a notice placed by the copyright holder of the file
+stating that the file is governed by GPLv3 along with this Exception.
+
+The purpose of this Exception is to allow distribution of Autoconf's
+typical output under terms of the recipient's choice (including
+proprietary).
+
+0. Definitions
+
+"Covered Code" is the source or object code of a version of Autoconf
+that is a covered work under this License.
+
+"Normally Copied Code" for a version of Autoconf means all parts of
+its Covered Code which that version can copy from its code (i.e., not
+from its input file) into its minimally verbose, non-debugging and
+non-tracing output.
+
+"Ineligible Code" is Covered Code that is not Normally Copied Code.
+
+1. Grant of Additional Permission.
+
+You have permission to propagate output of Autoconf, even if such
+propagation would otherwise violate the terms of GPLv3. However, if
+by modifying Autoconf you cause any Ineligible Code of the version you
+received to become Normally Copied Code of your modified version, then
+you void this Exception for the resulting covered work. If you convey
+that resulting covered work, you must remove this Exception in accordance
+with the second paragraph of Section 7 of GPLv3.
+
+2. No Weakening of Autoconf Copyleft.
+
+The availability of this Exception does not imply any general presumption
+that third-party software is unaffected by the copyleft requirements of
+the license of Autoconf.
diff --git a/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYINGv3 b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYINGv3
new file mode 100644
index 0000000..f288702
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/COPYINGv3
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ Copyright (C)
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+.
diff --git a/openocd-win/openocd/distro-info/licenses/autoconf-2.71/NEWS b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/NEWS
new file mode 100644
index 0000000..f035e65
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/NEWS
@@ -0,0 +1,2608 @@
+GNU Autoconf NEWS - User visible changes.
+
+* Noteworthy changes in release 2.71 (2021-01-28) [stable]
+
+** Bug fixes, including:
+
+*** Compilers that support C99 but not C2011 are detected correctly.
+
+*** Compatibility improved with clang and Oracle C++.
+
+*** Compatibility restored with automake's rules for regenerating configure.
+
+*** Compatibility restored with old versions of std-gnu11.m4.
+
+ Packages that wish to maintain compatibility with Autoconf 2.69 or
+ older, should update their copy of std-gnu11.m4 from Gnulib as soon
+ as practical, as the compatibility code bulks up the configure script.
+
+ Packages that require Autoconf 2.70 can drop this file entirely.
+
+* Noteworthy changes in release 2.70 (2020-12-08) [stable]
+
+** Backward incompatibilities:
+
+*** Warnings about obsolete constructs are now on by default.
+
+ These warnings can be turned off with ‘-Wno-obsolete’.
+
+ Many of these warnings advise maintainers to run autoupdate.
+ Be aware that autoupdate cannot solve all backward compatibility
+ problems, and cannot completely solve all of the problems it does
+ address. A configure script edited by autoupdate is likely to
+ need further manual fix-ups.
+
+*** Many macros have become pickier about argument quotation.
+
+ If you get a shell syntax error from your generated configure
+ script, or seemingly impossible misbehavior (e.g. entire blocks of
+ the configure script not getting executed), check first that all
+ macro arguments are properly quoted. The “M4 Quotation” section of
+ the manual explains how to quote macro arguments properly.
+
+ It is unfortunately not possible for autoupdate to correct
+ quotation errors.
+
+*** Many macros no longer AC_REQUIRE as many other macros as they used to.
+
+ This can expose several classes of latent bugs. These are the ones
+ we know about:
+
+ - Make sure to explicitly invoke all of the macros that set result
+ variables used later in the configure script, or in generated
+ Makefiles.
+
+ - Autoconf macros that use AC_REQUIRE are not safe to use in shell
+ control-flow constructs that appear outside of macros defined by
+ AC_DEFUN. Use AS_IF, AS_CASE, etc. instead. (See the
+ “Prerequisite Macros” section of the manual for details.)
+
+ The set of macros that use AC_REQUIRE internally may change from
+ release to release. The only macros that are guaranteed *not* to
+ use AC_REQUIRE are the macros for acting on the results of a
+ test: AC_DEFINE, AC_SUBST, AC_MSG_*, AC_CACHE_CHECK, etc.
+
+ - AC_REQUIRE cannot be applied to macros that need to be used with
+ arguments. Instead, invoke the macro normally, with its arguments.
+
+*** More macros use config.sub and config.guess internally.
+
+ As a consequence of improved support for cross compilation (see below),
+ more macros now use the auxiliary scripts ‘config.sub’ and ‘config.guess’.
+ If you use any of the affected macros, these scripts must be available
+ when your configure script is run, even if you have no intention of
+ ever cross-compiling your program.
+
+ autoreconf will issue an error if any auxiliary scripts are needed but
+ cannot be found. (It is not currently possible to make autoconf
+ itself issue this error.)
+
+ ‘autoreconf --install’ will add ‘config.sub’, ‘config.guess’, and
+ ‘install-sh’ to your source tree if they are needed. If you are
+ using Automake, scripts added to your tree by ‘autoreconf --install’
+ will automatically be included in the tarball produced by ‘make dist’;
+ otherwise, you will need to arrange for them to be distributed
+ yourself.
+
+ See the “Input” section of the manual for more detail, including
+ where to get the auxiliary scripts that may be needed by autoconf macros.
+
+*** Setting CC to a C++ compiler is no longer supported.
+
+ The C and C++ languages have diverged enough that we can no longer
+ guarantee that test C programs will be processed as intended by a
+ C++ compiler. In this release, configure will proceed anyway, but
+ many test results will be incorrect. In a future release, we may
+ make AC_PROG_CC error out if it detects that CC is a C++ compiler.
+
+ See the “Language Choice” section of the manual for instructions on
+ how to write configure scripts for C++ programs, and for programs
+ with code in more than one language.
+
+*** Running configure tests with warnings promoted to errors is not supported.
+
+ For instance, setting ‘CC="gcc -Werror"’ on the configure command
+ line, or adding -Werror to CFLAGS early in the configure script when
+ the compiler recognizes this option, is very likely to cause
+ subsequent tests to fail.
+
+ This has never been guaranteed to work; the code generated by
+ AC_CHECK_FUNC, for instance, is incorrect by a strict reading of the
+ original 1989 C standard, and has been ever since that macro was
+ introduced. Problems are more likely with newer, pickier compilers.
+
+ To enable compiler warnings and/or warnings-as-errors mode for your
+ own code, we currently recommend a dedicated Makefile variable
+ (e.g. ‘WARN_CFLAGS’) that is set by AC_SUBST when appropriate.
+ The Gnulib ‘warnings’ and ‘manywarnings’ modules can help with this.
+ We plan to add core support for probing for useful sets of compiler
+ warnings in a future release.
+
+*** Including confdefs.h manually may cause test failures.
+
+ This has never been necessary; confdefs.h is automatically included
+ at the beginning of all test programs (by AC_LANG_SOURCE). Because
+ of the way confdefs.h is generated and used, it is not practical to
+ give it a multiple inclusion guard. Therefore, if you include it
+ yourself, all of its definitions will be scanned twice.
+
+ Historically this has not been a problem, because confdefs.h only
+ makes macro definitions, and the C standard allows redefinitions
+ of macros as long as they’re exactly the same, but newer, pickier
+ compilers may complain anyway (see for instance GCC bug 97998).
+
+*** Older versions of automake and aclocal (< 1.8) are no longer supported.
+
+*** AC_CONFIG_SUBDIRS no longer directly supports Cygnus configure.
+
+ If you are still using an Autoconf script to drive configuration of
+ a multi-package build tree where some subdirectories use Cygnus
+ configure, copy or link $ac_aux_dir/configure into each subdirectory
+ where it is needed. Please also contact us; we were under the
+ impression nobody used this very old tool anymore.
+
+*** AC_CHECK_HEADER and AC_CHECK_HEADERS only do a compilation test.
+
+ This completes the transition from preprocessor-based header tests
+ begun in Autoconf 2.56.
+
+ The double test that was the default since Autoconf 2.64 is no
+ longer available. You can still request a preprocessor-only test
+ by specifying [-] as the fourth argument to either macro, but this
+ is now deprecated. If you really need that behavior use
+ AC_PREPROC_IFELSE.
+
+*** AC_INCLUDES_DEFAULT assumes an ISO C90 compliant C implementation.
+
+ Specifically, it assumes that the ISO C90 header
+ is available, without checking for it, and it does not include
+ the pre-standard header at all. If the POSIX header
+ exists, it will be included, without first testing
+ whether both and can be included in the
+ same source file.
+
+ AC_INCLUDES_DEFAULT still checks for the existence of ,
+ , and , because these headers may not exist
+ in a “freestanding environment” (a compilation mode intended for OS
+ kernels and similar, where most of the features of the C library are
+ optional). Most programs need not use ‘#ifdef HAVE_STDLIB_H’ etc in
+ their own code.
+
+ For compatibility’s sake, the C preprocessor macro STDC_HEADERS
+ will be defined when both and are available;
+ however, and are no longer checked for
+ (these, like , are required to exist in a freestanding
+ environment). New code should not refer to this macro.
+
+ Future releases of Autoconf may reduce the set of headers checked
+ for by AC_INCLUDES_DEFAULT.
+
+*** AS_ECHO and AS_ECHO_N unconditionally use ‘printf’.
+
+ This is substantially simpler, more reliable, and, in most cases,
+ faster than attempting to use ‘echo’ at all. However, if ‘printf’
+ is not a shell builtin, configure scripts will run noticeably
+ slower, and if ‘printf’ is not available at all, they will crash.
+ The only systems where this is known to be a problem are extremely
+ old, and unlikely to be able to handle modern C programs for other
+ reasons (e.g. not having a C90-compliant compiler at all).
+
+*** Configure scripts require support for $( ... ) command substitution.
+
+ This POSIX shell feature is approximately the same age as
+ user-defined functions, but there do exist shells that support
+ functions and not $( ... ), such as Solaris 10 /bin/sh.
+
+ Configure scripts will automatically locate a shell that supports
+ this feature and re-execute themselves with it, if necessary, so
+ the new requirement should be transparent to most users.
+
+ In this release, most of Autoconf’s code still uses the older `...`
+ notation for command substitution.
+
+*** AC_INIT now trims extra white space from its arguments.
+
+ For instance, AC_INIT([ GNU Hello ], [1.0]) will set PACKAGE_NAME
+ to “GNU Hello”.
+
+*** Macros that take whitespace-separated lists as arguments
+ now always expand macros within those arguments.
+
+ Formerly, these macros would *usually* expand those arguments, but
+ the behavior was not reliable nor was it consistent between autoconf
+ and autoheader.
+
+ Macro expansion within these arguments is deprecated; if expansion
+ changes the list, a warning in the “obsolete” category will be
+ emitted. Note that ‘dnl’ is a macro. Putting ‘dnl’ comments inside
+ any argument to an Autoconf macro is, in general, only supported
+ when that argument takes more Autoconf code (e.g. the ACTION-IF-TRUE
+ argument to AC_COMPILE_IFELSE).
+
+ The affected macros are AC_CHECK_FILES, AC_CHECK_FUNCS,
+ AC_CHECK_FUNCS_ONCE, AC_CHECK_HEADERS, AC_CHECK_HEADERS_ONCE,
+ AC_CONFIG_MACRO_DIRS, AC_CONFIG_SUBDIRS, and AC_REPLACE_FUNCS.
+
+*** AC_FUNC_VFORK no longer ignores a signal-handling bug in Solaris 2.4.
+
+ This bug was being ignored because Emacs wanted to use ‘vfork’ on
+ Solaris 2.4 anyway, but current versions of Emacs have dropped
+ support for Solaris 2.4. Most programs will want to avoid ‘vfork’
+ on this OS because of this bug.
+
+*** AC_FUNC_STRERROR_R assumes strerror_r is unavailable if it’s not declared.
+
+ The fallback technique it used to probe strerror_r’s return type
+ when the function was present in the C library, but not declared by
+ , was fragile and did not work at all when cross-compiling.
+ The systems where this fallback was necessary were all obsolete.
+
+ Programs that use AC_FUNC_STRERROR_R should make sure to test the
+ preprocessor macro HAVE_DECL_STRERROR_R before using strerror_r at all.
+
+*** AC_OPENMP can’t be used if you have files named ‘mp’ or ‘penmp’.
+
+ Autoconf will now issue an error if AC_OPENMP is used in a configure
+ script that’s in the same directory as a file named ‘mp’ or ‘penmp’.
+ Configure scripts that use AC_OPENMP will now error out upon
+ encountering files with these names in their working directory
+ (e.g. when the build directory is separate from the source directory).
+
+ If you have files with these names at the top level of your source
+ tree, we recommend either renaming them or moving them into a
+ subdirectory. See the documentation of AC_OPENMP for further
+ explanation.
+
+** New features
+
+*** Configure scripts now support a ‘--runstatedir’ option.
+
+ This defaults to ‘${localstatedir}/run’. It can be used, for
+ instance, to place per-process temporary runtime files (such as pid
+ files) into ‘/run’ instead of ‘/var/run’.
+
+*** autoreconf will now run gtkdocize and intltoolize when appropriate.
+
+*** autoreconf now recognizes AM_GNU_GETTEXT_REQUIRE_VERSION.
+
+ This macro can be used with gettext 0.19.6 or later to specify
+ a *minimum* version requirement for gettext, instead of the *fixed*
+ version requirement specified by AM_GNU_GETTEXT_VERSION.
+
+*** autoheader handles secondary config headers better.
+
+ It is no longer necessary to duplicate AC_DEFINE templates in the
+ main configuration header for autoheader to notice them.
+
+*** AC_PROG_CC now enables C2011 mode if the compiler supports it.
+
+ If not, it will fall back to C99 and C89, as before. Similarly,
+ AC_PROG_CXX now enables C++2011 if available, falling back on C++98.
+
+*** New macro AC_C__GENERIC tests for C2011 _Generic support.
+
+*** AC_C_VARARRAYS has been aligned with C2011.
+
+ It now defines __STDC_NO_VLA__ if variable-length arrays are not
+ supported but the compiler does not define __STDC_NO_VLA__.
+
+ For backward compatibility with Autoconf 2.61-2.69 AC_C_VARARRAYS
+ still defines HAVE_C_VARARRAYS, but this result macro is obsolescent.
+
+*** New macro AC_CONFIG_MACRO_DIRS.
+
+ This macro can be used more than once and accepts a list of
+ directories to search for local M4 macros. With Automake 1.13 and
+ later, use of this macro eliminates a reason to use ACLOCAL_AMFLAGS
+ in Makefile.am.
+
+ The older AC_CONFIG_MACRO_DIR, which could only be used once, is
+ still supported but considered deprecated.
+
+*** AC_USE_SYSTEM_EXTENSIONS knows about more extensions to enable.
+
+ System extensions will now be enabled on HP-UX, macOS, and MINIX.
+ Optional ISO C library components (e.g. decimal floating point) will
+ also be enabled.
+
+*** New compatibility macro AC_CHECK_INCLUDES_DEFAULT.
+
+ This macro runs the checks normally performed as a side-effect by
+ AC_INCLUDES_DEFAULT, if they haven’t already been done. Autoupdate
+ will replace certain obsolete constructs, whose only remaining
+ useful effect is to trigger those checks, with this macro. It is
+ unlikely to be useful otherwise.
+
+*** AC_REQUIRE_AUX_FILE has been improved.
+
+ Configure scripts now check, on startup, for the availability of all
+ the aux files that were mentioned in an AC_REQUIRE_AUX_FILE
+ invocation. This should help prevent certain classes of packaging
+ errors.
+
+ Also, it is no longer necessary for third-party macros that use
+ AC_REQUIRE_AUX_FILE to mention AC_CONFIG_AUX_DIR_DEFAULT. However,
+ if you are using AC_CONFIG_AUX_DIR_DEFAULT *without* also using
+ AC_REQUIRE_AUX_FILE, please start using AC_REQUIRE_AUX_FILE to
+ specify the aux files you actually need, so that the check can be
+ effective.
+
+*** AC_PROG_LEX has an option to not look for yywrap.
+
+ AC_PROG_LEX now takes one argument, which may be either ‘yywrap’ or
+ ‘noyywrap’. If it is ‘noyywrap’, AC_PROG_LEX will only set LEXLIB
+ to ‘-lfl’ or ‘-ll’ if a scanner that defines both main and yywrap
+ itself still needs something else from that library. On the other
+ hand, if it is ‘yywrap’, AC_PROG_LEX will fail (setting LEX to ‘:’
+ and LEXLIB to nothing) if it can’t find a library that defines yywrap.
+
+ In the absence of arguments, AC_PROG_LEX’s behavior is bug-compatible
+ with 2.69, which did neither of the above things (see the manual for
+ details). This mode is deprecated.
+
+ We encourage all programs that use AC_PROG_LEX to use the new
+ ‘noyywrap’ mode, and to define yywrap themselves, or use %noyywrap.
+ The yywrap function in lib(f)l is trivial, and self-contained
+ scanners are easier to work with.
+
+** Obsolete features and new warnings
+
+*** Use of the long-deprecated name ‘configure.in’ for the autoconf
+ input file now elicits a warning in the “obsolete” category.
+
+*** Use of the undocumented internal shell variables $as_echo and
+ $as_echo_n now elicits a warning in the “obsolete” category.
+ The macros AS_ECHO and AS_ECHO_N should be used instead.
+
+*** autoconf will now issue warnings (in the “syntax” category)
+ if the input file is missing a call to AC_INIT and/or AC_OUTPUT.
+
+*** autoconf will now issue warnings (in the “syntax” category)
+ for a non-literal URL argument to AC_INIT, and for a TARNAME
+ argument to AC_INIT which is either non-literal or contains
+ characters that should not be used in file names (e.g. ‘*’).
+
+*** AC_PROG_CC_STDC, AC_PROG_CC_C89, AC_PROG_CC_C99 are now obsolete.
+
+ Applications should use AC_PROG_CC.
+
+*** AC_HEADER_STDC and AC_HEADER_TIME are now stubs.
+
+ They still define the C preprocessor macros STDC_HEADERS and
+ TIME_WITH_SYS_TIME, respectively, but they no longer check for the
+ ancient, non-ISO-C90 compliant systems where formerly those macros
+ would not be defined. Autoupdate will remove them.
+
+ These macros were already labeled obsolete in the manual.
+
+*** AC_DIAGNOSE, AC_FATAL, AC_WARNING, and _AC_COMPUTE_INT are now
+ replaced with modern equivalents by autoupdate.
+
+ These macros were already labeled obsolete in the manual.
+
+*** AC_CONFIG_HEADER is now diagnosed as obsolete, and replaced with
+ AC_CONFIG_HEADERS by autoupdate.
+
+ This macro has been considered obsolete for many years and was not
+ documented at all.
+
+*** The macro AC_OBSOLETE is obsolete.
+
+ Autoupdate will replace it with m4_warn([obsolete], [explanation]).
+ If possible, macros using AC_OBSOLETE should be converted to use
+ AU_DEFUN or AU_ALIAS instead, which enables autoupdate to replace
+ them, but this has to be done by hand and is not always possible.
+
+ This macro has been considered obsolete for many years, but was not
+ officially declared as such.
+
+*** Man pages for config.guess and config.sub are no longer provided.
+
+ They were moved to the master source tree for config.guess and
+ config.sub.
+
+** Notable bug fixes
+
+*** Compatible with current Automake, Libtool, Perl, Texinfo, and shells.
+
+ All of autoconf’s tools and generated scripts, and the build process
+ and testsuite for autoconf itself, have been tested to work
+ correctly with current versions of Automake, Libtool, Perl, Texinfo,
+ bash, ksh93, zsh, and FreeBSD and NetBSD /bin/sh.
+
+ Generated configure scripts are expected to work reliably with an
+ even wider variety of shells, including BusyBox sh and various
+ proprietary Unixes’ /bin/sh, as long as they are minimally compliant
+ with the Unix95 shell specification. Notably, support for
+ shell-script functions and the ‘printf’ builtin are required.
+
+*** Checks compatible with current language standards and compilers.
+
+ Many individual macros have been improved to accommodate changes in
+ recent versions of the C and C++ language standards, and new
+ features and quirks of commonly used compilers (both free and
+ proprietary).
+
+*** Improved support for cross compilation.
+
+ Many individual macros have been improved to produce more accurate
+ results when cross-compiling.
+
+*** Improved robustness against unusual build environments.
+
+ Many bugs have been fixed where generated configure scripts would
+ fail catastrophically under unusual conditions, such as stdout being
+ closed, or $TMPDIR not being an absolute path, or the root directory
+ being mentioned in $PATH.
+
+*** AC_CHECK_FUNCS_ONCE and AC_CHECK_HEADERS_ONCE now support multiple
+ programming languages. They no longer perform all checks in the
+ language active upon the first use of the macro.
+
+*** AC_CHECK_DECL and AC_CHECK_DECLS will now detect missing declarations for
+ library functions that are also Clang compiler builtins.
+
+*** AC_PATH_X and AC_PATH_XTRA don’t search for X11 when cross-compiling.
+
+ Libraries and headers found by running xmkmf or searching /usr/X11,
+ /usr/X11R7, etc. are likely to belong to a native X11 installation
+ for the build machine and to be inappropriate for cross compilation.
+
+ To cross-compile programs that require X11, we recommend putting the
+ headers and libraries for the host system in your cross-compiler’s
+ default search paths. Alternatively, use configure’s --x-includes
+ and --x-libraries command line options to tell it where they are.
+
+*** AS_IF’s if-false argument may be empty after macro expansion.
+
+ This long-standing limitation broke configure scripts that used
+ macros in this position that emitted shell code in 2.69 but no
+ longer do, so we have lifted it.
+
+*** AC_HEADER_MAJOR detects the location of the major, minor, and
+ makedev macros correctly under glibc 2.25 and later.
+
+*** AC_FC_LINE_LENGTH now documents the maximum portable length of
+ “unlimited” Fortran source code lines to be 250 columns, not 254.
+
+*** AC_INIT and AS_INIT no longer embed (part of) the path to the
+ source directory in generated files.
+
+ We believe this was the only case where generated file contents
+ could change depending on the environment outside the source tree
+ itself. If you find any other cases please report them as bugs.
+
+*** config.log properly escapes arguments in the header comment.
+
+*** config.status --config output is now quoted in a more readable fashion.
+
+** Autotest enhancements
+
+*** Autotest provides a new macro AT_DATA_UNQUOTED, similar to AT_DATA
+ but processing variable substitutions, command substitutions and
+ backslashes in the contents argument.
+
+*** AC_CONFIG_TESTDIR will automatically pass EXEEXT to a testsuite (via
+ the atconfig file).
+
+*** AT_TESTED arguments can use variable or command substitutions, including
+ in particular $EXEEXT
+
+*** New macros AT_PREPARE_TESTS, AT_PREPARE_EACH_TEST, and AT_TEST_HELPER_FN.
+
+ These provide an official way to define testsuite-specific
+ initialization code and shell functions.
+
+* Noteworthy changes in release 2.69 (2012-04-24) [stable]
+
+** Autoconf now requires perl 5.6 or better (but generated configure
+ scripts continue to run without perl).
+
+* Noteworthy changes in release 2.68b (2012-03-01) [beta]
+ Released by Eric Blake, based on git versions 2.68.*.
+
+** Autoconf-generated configure scripts now unconditionally re-execute
+ themselves with $CONFIG_SHELL, if that's set in the environment.
+
+** The texinfo documentation no longer specifies "front-cover" or
+ "back-cover" texts, so that it may now be included in Debian's
+ "main" section.
+
+** Support for the Go programming language has been added. The new macro
+ AC_LANG_GO sets variables GOC and GOFLAGS.
+
+** AS_LITERAL_IF again treats '=' as a literal. Regression introduced in
+ 2.66.
+
+** The macro AS_EXECUTABLE_P, present since 2.50, is now documented.
+
+** Macros
+
+- AC_PROG_LN_S and AS_LN_S now fall back on 'cp -pR' (not 'cp -p') if 'ln -s'
+ does not work. This works better for symlinks to directories.
+
+- New macro AC_HEADER_CHECK_STDBOOL.
+
+- New and updated macros for Fortran support:
+
+ AC_FC_CHECK_BOUNDS to enable array bounds checking
+ AC_F77_IMPLICIT_NONE and AC_FC_IMPLICIT_NONE to disable implicit integer
+ AC_FC_MODULE_EXTENSION to compute the Fortran 90 module name extension
+ AC_FC_MODULE_FLAG for the Fortran 90 module search path flag
+ AC_FC_MODULE_OUTPUT_FLAG for the Fortran 90 module output directory flag
+ AC_FC_PP_SRCEXT for preprocessed Fortran source files extensions
+ AC_FC_PP_DEFINE for the Fortran preprocessor define flag
+
+* Noteworthy changes in release 2.68 (2010-09-22) [stable]
+ Released by Eric Blake, based on git versions 2.67.*.
+
+** AC_MSG_ERROR (and AS_ERROR) can once again be followed immediately by
+ `dnl'. Regression introduced in 2.66.
+
+** AC_INIT again allows URLs with '?' for its BUG-REPORT argument.
+ Regression introduced in 2.66.
+
+** AC_REPLACE_FUNCS again allows a non-literal argument, such as a shell
+ variable that expands to a list of functions to check. Regression
+ introduced in 2.66.
+
+** AT_BANNER() with empty argument will cause visual separation from previous
+ test category.
+
+** The macros AC_PREPROC_IFELSE, AC_COMPILE_IFELSE, AC_LINK_IFELSE, and
+ AC_RUN_IFELSE now warn if the first argument failed to use
+ AC_LANG_SOURCE or AC_LANG_PROGRAM to generate the conftest file
+ contents. A new macro AC_LANG_DEFINES_PROVIDED exists if you have
+ a compelling reason why you cannot use AC_LANG_SOURCE but must
+ avoid the warning.
+
+** The macro m4_define_default is now documented.
+
+** Symlinked config.cache files are supported; configure now tries to
+ update non-symlinked cache files atomically, so that concurrent configure
+ runs do not leave behind broken cache files. It is still unspecified
+ which subset or union of results is cached though.
+
+** Autotest testsuites should not contain long text lines any more, and be
+ portable even when very many test groups are used.
+
+** AT_CHECK semantics with respect to the Autotest variable $at_status and
+ shell execution environment of the arguments are documented now.
+
+** AC_FC_LIBRARY_LDFLAGS now tolerates output from newer gfortran.
+
+** Newly obsolete macros
+ The following macros have been marked obsolete. New programs
+ should use the corresponding Gnulib modules. Gnulib not only
+ detects a larger set of portability problems with these functions,
+ but also provides complete workarounds.
+
+ AC_FUNC_ERROR_AT_LINE AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK
+ AC_FUNC_MKTIME AC_FUNC_STRTOD
+
+
+* Major changes in Autoconf 2.67 (2010-07-21) [stable]
+ Released by Eric Blake, based on git versions 2.66.*.
+
+** AC_CONFIG_SUBDIRS with more than one subdirectory at a time works again.
+ Regression introduced in 2.66.
+
+** AC_CHECK_SIZEOF of a pointer type works again. Regression introduced in
+ 2.66.
+
+** New macro AC_FC_LINE_LENGTH to accept long Fortran source code lines.
+
+** AC_PREPROC_IFELSE now keeps the preprocessed output in the conftest.i
+ file for inspection by the commands in the ACTION-IF-TRUE argument.
+
+** AC_INIT again allows parentheses and other characters that are literal
+ in single- or double-quoted strings, and in quoted and unquoted
+ here-documents, for its PACKAGE and VERSION arguments. Regression
+ introduced in 2.66.
+
+** autoreconf passes warning flags to new enough versions of aclocal.
+
+** Running an Autotest testsuite in parallel mode no longer triggers a
+ race condition that could cause the testsuite run to end early,
+ fixing a sporadic failure in autoconf's own testsuite. Bug present
+ since introduction of parallel tests in 2.63b.
+
+
+* Major changes in Autoconf 2.66 (2010-07-02) [stable]
+ Released by Eric Blake, based on git versions 2.65.*.
+
+** AC_FUNC_MMAP works in C++ mode again. Regression introduced in 2.65.
+
+** Use of m4_divert without a named diversion now issues a syntax warning,
+ since it is seldom right to change diversions behind autoconf's back.
+
+** The macros AC_TYPE_INT8_T, AC_TYPE_INT16_T, AC_TYPE_INT32_T, and
+ AC_TYPE_INT64_T work again. Regression introduced in 2.65.
+
+** AC_PROG_INSTALL correctly uses `shtool' again. Regression introduced
+ in 2.64.
+
+** Autoconf should work on EBCDIC hosts.
+
+** AC_CHECK_DECL and AC_CHECK_DECLS accept optional function argument types
+ for overloaded C++ functions.
+
+** AS_SET_CATFILE accepts nonliterals in its variable name argument now.
+
+** Autotest testsuites accept an option --recheck to rerun tests that
+ failed or passed unexpectedly during the last non-debug testsuite run.
+
+** AC_ARG_ENABLE and AC_ARG_WITH now also accept `+' signs in `--enable-*'
+ and `--with-*' arguments, converting them to underscores for the variable
+ names.
+
+** In configure scripts, loading CONFIG_SITE no longer searches PATH,
+ and problems in loading the configuration site files are diagnosed.
+
+** Autotest testsuites may optionally provide colored test results.
+
+** The previously undocumented Autotest macros AT_ARG_OPTION and
+ AT_ARG_OPTION_ARG have seen bug fixes and are documented now.
+ AT_ARG_OPTION has been changed in that the negative of a long option
+ --OPTION is now --no-OPTION rather than --noOPTION.
+
+** The macro AS_LITERAL_IF is slightly more conservative; text
+ containing shell quotes are no longer treated as literals.
+ Furthermore, a new macro, AS_LITERAL_WORD_IF, adds an additional
+ level of checking that no whitespace occurs in literals.
+
+** The macros AS_TR_SH and AS_TR_CPP no longer expand their results.
+
+** The following macros are now documented:
+ AS_BOX
+
+** New macro AC_FC_FIXEDFORM to accept fixed-form Fortran.
+
+
+* Major changes in Autoconf 2.65 (2009-11-21) [stable]
+ Released by Eric Blake, based on git versions 2.64.*.
+
+** Autoconf is now licensed under the General Public License version 3
+ or later (GPLv3+). As with earlier versions, the license includes
+ an exception clause so that you may release a configure script
+ generated by autoconf under the license of your own program.
+
+** New macros to support Objective C++.
+ AC_PROG_OBJCXX AC_PROG_OBJCXXCPP
+
+** The following undocumented autoconf macros, removed in Autoconf 2.64,
+ have been reinstated:
+ AH_CHECK_HEADERS
+
+ These macros are present only for backwards compatibility purposes.
+
+** The macro AC_LANG_COMPILER no longer fails on embedded systems that
+ lack fopen in the C library, such as AVR or RTEMS (regression
+ introduced in 2.64).
+
+** The AC_FC_FREEFORM macro no longer suffers from a whitespace bug that
+ made it fail with some Fortran compilers (regression introduced in
+ 2.64).
+
+** The AC_TYPE_UINT64_T and AC_TYPE_INT64_T macros have been fixed to no
+ longer mistakenly select a 32-bit type on some compilers (bug present
+ since macros were introduced in 2.59c).
+
+** The AC_FUNC_MMAP macro has been fixed to be portable to systems like
+ Cygwin (bug present since macro was introduced in 2.0).
+
+** The following documented autotest macros are new:
+ AT_CHECK_EUNIT
+
+** The following m4sugar macros now quote their expansion:
+ m4_toupper m4_tolower
+
+** The following m4sugar macros are new:
+ m4_escape
+
+** The m4sugar macro m4_text_wrap now copes with embedded quoting without
+ requiring quadrigraphs. For uses like AC_ARG_VAR([a], [[b c]]),
+ this gives the intuitive behavior of "[b c]" in the output (2.63
+ gave the output of "[b], [c]", and 2.64 encountered a failure).
+
+** The `$tmp' temporary directory used in config.status is documented for
+ public use now.
+
+** config.status now provides a --config option to produce the configuration.
+
+** Many cache variables used by Autoconf's macros are now documented.
+
+** Configure scripts work better on DJGPP by avoiding a bug present in
+ the DJGPP port of bash 2.04 in handling 'return' in a shell
+ function (regression introduced in 2.64).
+
+* Major changes in Autoconf 2.64 (2009-07-26) [stable]
+ Released by Eric Blake, based on git versions 2.63b.*.
+
+** Autoconf now requires GNU M4 1.4.6 or later. Earlier versions of M4
+ have a bug in regular expression handling that interferes with some
+ of the speedups provided since Autoconf 2.63. GNU M4 1.4.13 or
+ later is recommended.
+
+** AS_IF and AS_CASE have been taught to avoid syntax errors even when
+ given arguments that expand to just whitespace.
+
+** The following documented autoconf macros are new:
+ AC_ERLANG_SUBST_ERTS_VER
+
+** The autoheader tool now understands m4 macro arguments passed to
+ AC_DEFINE and AC_DEFINE_UNQUOTED.
+
+** Ensure AT_CHECK can support commands that include a # given with
+ proper m4 quoting. For shell comments, this is a new feature; for
+ non-shell comments, this fixes a regression introduced in 2.63b.
+ Additionally, AT_CHECK correctly supplies shell escapes for
+ metacharacters occurring in m4 macro expansions within the expected
+ stdout and stderr parameters.
+
+** The macro AT_CHECK now understands the concept of hard failure. If
+ a test exits with an unexpected status 99, cleanup actions for the
+ test are inhibited and the test is treated as a failure regardless
+ of AT_XFAIL_IF. It also understands the new directives
+ ignore-nolog, stdout-nolog, and stderr-nolog.
+
+** The following documented autotest macros are new:
+ AT_CHECK_UNQUOTED AT_FAIL_IF AT_SKIP_IF
+
+** The following documented m4sugar macros are new:
+ m4_argn m4_copy_force m4_default_nblank m4_default_nblank_quoted
+ m4_ifblank m4_ifnblank m4_rename_force
+
+** The autoconf testsuite now exercises all Erlang macros.
+
+* Major changes in Autoconf 2.63b (2009-03-31) [beta]
+ Released by Eric Blake, based on git versions 2.63.*.
+
+** The manual is now shipped under the terms of the GNU FDL 1.3.
+
+** AC_REQUIRE now detects the case of an outer macro which first expands
+ then later indirectly requires the same inner macro. Previously,
+ this case led to silent out-of-order expansion (bug present since
+ 2.50); it now issues a syntax warning, and duplicates the expansion
+ of the inner macro to guarantee dependencies have been met. See
+ the manual for advice on how to refactor macros in order to avoid
+ the bug in earlier autoconf versions and avoid increased script
+ size in the current version.
+
+** AC_DEFUN_ONCE has improved semantics. Previously, a macro declared
+ with AC_DEFUN_ONCE warned on a second invocation; and out-of-order
+ expansion was still possible. Now, dependencies are guaranteed,
+ and subsequent invocations are a silent no-op. This makes
+ AC_DEFUN_ONCE an ideal macro for silencing AC_REQUIRE warnings.
+
+** The following macros are now defined with AC_DEFUN_ONCE. This means
+ a subtle change in semantics; previously, an AC_DEFUN macro could
+ expand one of these macros multiple times or surround the macro
+ inside shell conditional text to bypass the effects of these
+ macros, but now the macro will expand exactly once, and prior to
+ the start of any enclosing AC_DEFUN macro:
+ AC_CANONICAL_BUILD AC_CANONICAL_HOST AC_CANONICAL_TARGET
+ AC_HEADER_ASSERT AC_PROG_INSTALL AC_PROG_MKDIR_P
+ AC_USE_SYSTEM_EXTENSIONS
+
+** AC_LANG_ERLANG works once again (regression introduced in 2.61a).
+
+** AC_HEADER_ASSERT is fixed so that './configure --enable-assert' no
+ longer mistakenly disables assertions.
+
+** AC_INIT now takes an optional fifth parameter that can be used to
+ set AC_PACKAGE_URL, a URL for the package's home page; the URL is
+ used in `configure --help' and is also available via AC_DEFINE.
+
+** Autotest testsuites accept an option --jobs[=N] for parallel testing.
+ This feature is still in testing, and may not work on every
+ platform, help in improving it would be appreciated.
+
+** Autotest testsuites do not attempt to write startup error messages
+ to the log file before that is opened (regression introduced in 2.63).
+
+** Configure scripts now use shell functions. This feature leads to
+ smaller configure files and faster execution.
+
+** Present But Cannot Be Compiled: Autoconf will now proceed with
+ the compiler's result if a header is present but cannot be compiled.
+ The warning is still printed, and you should really fix it by
+ providing a fourth parameter to AC_CHECK_HEADER/AC_CHECK_HEADERS.
+
+** Autoreconf added aclocal to the set of programs affected by the
+ `autoreconf -I dir' option.
+
+** The following documented m4sugar macros are new:
+ m4_chomp m4_chomp_all m4_cleardivert m4_curry m4_default_quoted
+ m4_esyscmd_s m4_map_args m4_map_args_pair m4_map_args_sep
+ m4_map_args_w m4_set_map m4_set_map_sep m4_stack_foreach
+ m4_stack_foreach_lifo m4_stack_foreach_sep
+ m4_stack_foreach_sep_lifo
+
+** The following m4sugar macros are documented now, but in some cases
+ with slightly different semantics than what the previous
+ undocumented version had:
+ m4_copy m4_dumpdefs m4_rename m4_version_prereq
+
+** The m4sugar macro m4_expand has been taught to handle unterminated
+ comments and shell case statements. As a result, it is used
+ internally in more places, such as AC_DEFINE and AT_CHECK. Most
+ uses of AC_DEFINE and AT_CHECK should not behave any differently;
+ however, it may be necessary to add double-quoting around
+ unbalanced `(' where single-quoting used to be sufficient.
+
+** The following documented m4sh macros are new:
+ AS_INIT_GENERATED AS_LINENO_PREPARE AS_ME_PREPARE AS_SET_STATUS
+ AS_VAR_APPEND AS_VAR_ARITH AS_VAR_COPY
+
+** The following m4sh macros are documented now, but in some cases
+ with slightly different semantics than what the previous
+ undocumented version had:
+ AS_ECHO AS_ECHO_N AS_ESCAPE AS_EXIT AS_LITERAL_IF AS_UNSET
+ AS_VAR_IF AS_VAR_POPDEF AS_VAR_PUSHDEF AS_VAR_SET AS_VAR_SET_IF
+ AS_VAR_TEST_SET AS_VERSION_COMPARE
+
+** The m4sh macros AS_IF and AS_CASE can now be used in shell lists.
+ The responsibility for supplying a trailing newline now belongs to
+ the call site, but since most users did not add dnl, this generally
+ results in fewer empty lines in configure.
+
+
+* Major changes in Autoconf 2.63 (2008-09-09) [stable]
+ Released by Eric Blake, based on git versions 2.62.*.
+
+** AC_C_BIGENDIAN does not mistakenly report "universal" for some
+ bigendian hosts, a regression introduced with universal binary
+ support in 2.62.
+
+** AC_PATH_X now includes /lib64 and /usr/lib64 in its list of default
+ library directories.
+
+** AC_USE_SYSTEM_EXTENSIONS no longer conflicts with an external
+ AC_DEFINE([__EXTENSIONS__]). This fixes a regression introduced in
+ 2.62 when using macros such as AC_AIX that were made obsolete in
+ favor of the more portable AC_USE_SYSTEM_EXTENSIONS.
+
+** AC_CHECK_TARGET_TOOLS is usable in the non-cross-compile case.
+
+** Newly obsolete macros
+ The following macro has been marked obsolete, since current porting
+ targets can safely assume C89 semantics that signal handlers return
+ void. We have no current plans to remove the macro.
+
+ AC_TYPE_SIGNAL
+
+** The macros m4_map and m4_map_sep now ignore any list elements
+ consisting of just empty quotes, and m4_map_sep now expands its
+ separator. This fixes a regression in 2.62 when these macros were
+ first documented, for the sake of clients expecting the semantics
+ that these macros had prior to that time. The new macros m4_mapall
+ and m4_mapall_sep, along with extra quoting of the separator, can
+ be used to get the semantics that m4_map_sep had in 2.62.
+
+** Clients of m4_expand, such as AS_HELP_STRING and AT_SETUP, can now
+ handle properly quoted but otherwise unbalanced parentheses (for
+ some macros, this fixes a regression in 2.62).
+
+** Two new quadrigraphs have been introduced: @{:@ for (, and @:}@ for ),
+ allowing the output of unbalanced parentheses in more contexts.
+
+** The following m4sugar macros are new:
+ m4_cleardivert m4_joinall m4_mapall m4_mapall_sep m4_reverse
+ m4_set_add m4_set_add_all m4_set_contains m4_set_contents
+ m4_set_delete m4_set_difference m4_set_dump m4_set_empty
+ m4_set_foreach m4_set_intersection m4_set_list m4_set_listc
+ m4_set_remove m4_set_size m4_set_union
+
+** The following m4sugar macros now accept multiple arguments, as is the
+ case with underlying m4:
+ m4_defn m4_popdef m4_undefine
+
+** The following m4sugar macros now guarantee linear scaling; they
+ previously had linear scaling with m4 1.6 but quadratic scaling
+ when using m4 1.4.x. All macros built on top of these also gain
+ the scaling improvements.
+ m4_bmatch m4_bpatsubsts m4_case m4_cond m4_do m4_dquote_elt
+ m4_foreach m4_join m4_list_cmp m4_map m4_map_sep m4_max
+ m4_min m4_shiftn
+
+** AT_KEYWORDS once again performs expansion on its argument, such that
+ AT_KEYWORDS([m4_if([$1], [], [default])]) no longer complains about
+ the possibly unexpanded m4_if [regression introduced in 2.62].
+
+** Config header templates `#undef UNDEFINED /* comment */' do not lead to
+ nested comments any more; regression introduced in 2.62.
+
+
+* Major changes in Autoconf 2.62 (2008-04-05) [stable]
+ Released by Eric Blake, based on git versions 2.61a.*.
+
+** Many optimizations have been applied to make overall execution faster.
+
+** Autotest now makes use of shell functions.
+
+** config.status now uses awk instead of sed also for config headers.
+
+ - As a side effect, AC_DEFINE and AC_DEFINE_UNQUOTED now handle multi-line
+ values, i.e., backslash-newline combinations are handled correctly.
+ Further, for config headers, the total size of values is not limited by
+ the POSIX length limit of text lines any more, only each single line.
+
+** New config variable `top_build_prefix'.
+
+** New Autoconf macros:
+ AC_AUTOCONF_VERSION AC_OPENMP AC_PATH_PROGS_FEATURE_CHECK
+
+** AC_C_BIGENDIAN now supports universal binaries a la Mac OS X.
+
+** AC_C_RESTRICT now prefers to #define 'restrict' to a variant spelling
+ like '__restrict' if the variant spelling is available, as this is
+ more likely to work when mixing C and C++ code.
+
+** AC_CHECK_ALIGNOF's type argument T is now documented better: it must
+ be a string of tokens such that "T y;" is a valid member declaration
+ in a struct.
+
+** AC_CHECK_SIZEOF now accepts objects as well as types: the general rule
+ is that sizeof (X) works, then AC_CHECK_SIZEOF (X) should work.
+
+** AC_CHECK_TYPE and AC_CHECK_TYPES now work on any C type-name; formerly,
+ they did not work for function types. In C++, they now work on any
+ type-id that can be the operand of sizeof; this is similar to C,
+ except it excludes anonymous struct and union types. Formerly,
+ some (but not all) C++ types involving anonymous struct and union
+ were accepted, though this was not documented.
+
+** AC_CONFIG_LINKS now prefers to link against files in the build tree
+ if found, and it works to link against a file of the same name in
+ the source tree, even if both trees coincide.
+
+** AC_INIT no longer alters $@; regression introduced in 2.60.
+
+** AC_USE_SYSTEM_EXTENSIONS now defines _ALL_SOURCE for Interix platforms.
+
+** AS_HELP_STRING no longer underquotes its first argument; it also handles
+ the case where the first argument contains single-quoted commas.
+ For example, "AS_HELP_STRING([-a, [--arg[=foo]]], [bar])" produces:
+ " -a, --arg[=foo] bar"
+ Additionally, the macro now takes two additional arguments,
+ indent-column and wrap-column; these should not normally be needed,
+ but can be used to fine-tune how the output text is wrapped.
+
+** AC_PROG_INSTALL now requires an install program that can install multiple
+ files into a target directory.
+
+** The command 'autoconf -' now correctly processes a file from stdin.
+
+** 'autoreconf -m' now honors $MAKE.
+
+** For all of the directory arguments for 'configure', such as '--prefix'
+ or '--bindir', trailing slashes are stripped. As an example, if
+ tab completion in the user's shell appends trailing slashes, the
+ command './configure --prefix=/usr/' will still result in an
+ expanded libdir value of /usr/lib, not /usr//lib.
+
+** `configure --help=recursive' now works in read-only trees and from
+ unconfigured build trees.
+
+** If precious variables differ only in whitespace, then the cache consistency
+ check warns instead of fails, and reuses the old value.
+
+** AT_BANNER is now documented.
+
+** AT_SETUP now handles macro expansions properly when calculating line
+ length.
+
+** Autotest now determines $srcdir correctly.
+
+** Testsuites built by autotest now accept a -C/--directory=DIR option
+ to adjust the working directory prior to creating files.
+
+** Autoconf now requires GNU M4 1.4.5 or later. Earlier versions of M4 have
+ a bug in macro tracing that interferes with the interaction between
+ Autoconf and Automake. GNU M4 1.4.11 or later is recommended. The
+ configure search for a working M4 is improved.
+
+** For portability with the eventual M4 2.0, macros should no longer use
+ anything larger than $9 to refer to arguments.
+
+** Documentation for m4sugar is improved.
+
+ - The following macros were previously available as undocumented
+ interfaces; the macros are now documented as stable interfaces.
+
+ __oline__ m4_assert m4_bmatch m4_bpatsubsts m4_car m4_case
+ m4_cdr m4_default m4_divert_once m4_divert_pop m4_divert_push
+ m4_divert_text m4_do m4_errprintn m4_fatal m4_flatten
+ m4_ifndef m4_ifset m4_ifval m4_ifvaln m4_location
+ m4_n m4_shiftn m4_strip m4_warn
+
+ - The following macros were previously available as undocumented
+ interfaces, but had bug fixes or semantic changes as part of this
+ release. Packages that relied on the undocumented behavior
+ should be analyzed to make sure they will still work with the
+ new documented behavior.
+
+ m4_cmp m4_list_cmp m4_join m4_map m4_map_sep m4_sign
+ m4_text_box m4_text_wrap m4_version_compare
+
+ - The m4_wrap macro used to have unspecified order, but now
+ guarantees FIFO order. m4_wrap_lifo was added to guarantee LIFO
+ order.
+
+ - Packages using the undocumented m4sugar macro m4_PACKAGE_VERSION
+ should consider using the new AC_AUTOCONF_VERSION instead.
+
+ - m4sugar macros that are not documented in the manual are still
+ deemed experimental, and should not be used outside of Autoconf.
+
+** The m4sugar macros m4_append and m4_append_uniq, first documented in
+ 2.60, have been fixed to treat both the string and the separator
+ arguments consistently with regards to quoting. Prior to this fix,
+ m4_append_uniq could mistakenly duplicate entries if the expansion
+ of the separator resulted in a different string (for example, if it
+ contained quotes, a comma, or a macro name). However, it means
+ that programs previously using
+ m4_append([name], [string], [[, ]])
+ are now using a four-character separator instead of the intended
+ comma and space. If you need portability to earlier versions of
+ Autoconf, you can insert the following snippet after AC_INIT but
+ before any other macro expansions, to enforce the new semantics:
+ m4_pushdef([m4_append], [m4_define([$1],
+ m4_ifdef([$1], [m4_defn([$1])[$3]])[$2])])
+ Additionally, m4_append_uniq now takes optional parameters that can
+ be used to take action depending on whether anything was appended,
+ and warns if a non-empty separator occurs within the string being
+ appended, since that can lead to duplicates.
+
+** The following m4sugar macros are new:
+ m4_append_uniq_w m4_apply m4_combine m4_cond m4_count
+ m4_dquote_elt m4_echo m4_expand m4_ignore m4_make_list m4_max
+ m4_min m4_newline m4_shift2 m4_shift3 m4_unquote m4_wrap_lifo
+
+** Warnings are now generated by default when an installer invokes
+ 'configure' with an unknown --enable-* or --with-* option.
+ These warnings can be disabled with the new AC_DISABLE_OPTION_CHECKING
+ macro, or by invoking 'configure' with --disable-option-checking.
+
+** Existing obsolete macros
+ The documentation for the following macros is adjusted to make it
+ more clear that they have previously been marked obsolete, as their
+ functionality can be accomplished by other macros. We have no
+ current plans to remove them from Autoconf.
+
+ AC_ENABLE AC_STRUCT_ST_BLKSIZE AC_STRUCT_ST_RDEV AC_WITH
+
+** Newly obsolete macros
+ The following macros have been marked obsolete, as they only
+ perform a subset of AC_USE_SYSTEM_EXTENSIONS. We have no current
+ plans to remove them.
+
+ AC_AIX AC_GNU_SOURCE AC_ISC_POSIX AC_MINIX
+
+** AC_C_LONG_DOUBLE is obsolescent.
+ The documentation now says that AC_C_LONG_DOUBLE is obsolescent: it
+ tests for problems that are so old that it is no longer of
+ practical importance on current systems. New programs need not use
+ AC_C_LONG_DOUBLE. We have no current plans to remove it.
+
+** AC_DIAGNOSE, AC_WARNING, and AC_FATAL are obsolescent.
+ The documentation now favors the use of M4sugar macros m4_warn and
+ m4_fatal, since the naming makes it more obvious that the
+ diagnostics are associated with M4 expansion (ie. when running
+ `autoconf'), and offers less confusion with the AC_MSG_ERROR,
+ AC_MSG_FAILURE, and AC_MSG_WARN macros which manage diagnostics
+ when running `configure'. We have no current plans to remove these
+ macros.
+
+
+* Major changes in Autoconf 2.61a (2006-12-11)
+
+** AC_FUNC_FSEEKO was broken in 2.61; it didn't make fseeko and ftello visible
+ on many platforms. This has been fixed.
+
+** AC_FUNC_SETVBUF_REVERSED is now obsolete. It is still defined for backward
+ compatibility but it does nothing. The macro was already
+ obsolescent, as the last systems to have the problem were those
+ based on SVR2, which became obsolete in 1987. The macro had bugs
+ on some modern systems and could no longer be maintained reliably
+ due to lack of ancient systems to test it on.
+
+** config.status now uses awk instead of sed for most substitutions, for speed.
+
+ - As a side effect multi-line values of substituted variables no
+ longer have a small limit in total size, though for portability
+ each line should not exceed the POSIX length limit for text lines.
+
+ - It is now documented that Makefile.in should not contain
+ overlapping variable occurrences, e.g., @VAR1@VAR2@.
+ Autoconf's behavior was always iffy in such cases, and the
+ awk implementation has changed the behavior.
+
+** Many uses of 'echo' have been rewritten so that Autoconf-generated
+ scripts have fewer problems with strings or file names containing
+ embedded special characters such as backslash or leading "-". This
+ was implemented by using `printf '%s\n' "$foo"' instead of `echo
+ "$foo"' when printf works. Due to the implementation technique
+ used, Autoconf-generated scripts now run considerably more slowly
+ on ancient implementations lacking printf. However, this should
+ not be a problem, since Autoconf-generated scripts in practice
+ invariably find a more-modern shell these days.
+
+
+* Major changes in Autoconf 2.61 (2006-11-17)
+
+** New macros AC_C_FLEXIBLE_ARRAY_MEMBER, AC_C_VARARRAYS.
+
+** AC_ARG_ENABLE and AC_ARG_WITH now allow '.' in feature and package names.
+
+
+* Major changes in Autoconf 2.60b (2006-10-22)
+
+** BIN_SH
+ Autoconf-generated shell scripts no longer export BIN_SH, due to
+ configuration hassles with this. Installers who need BIN_SH in
+ their environment should set it before invoking 'configure' and
+ 'make'. As far as we know, this affects only Unixware installations.
+
+** Obsolescent macros
+ The documentation now says that the following macros are obsolescent,
+ as they are superseded by Gnulib:
+
+ AC_FUNC_FNMATCH AC_FUNC_FNMATCH_GNU AC_FUNC_GETLOADVG AC_REPLACE_FNMATCH
+
+ New programs should use the Gnulib counterparts of these macros.
+ We have no current plans to remove them from Autoconf.
+
+** AC_COMPUTE_INT no longer caches or reports results.
+
+** AC_CHECK_DECL now also works with aggregate objects.
+
+** AC_USE_SYSTEM_EXTENSIONS now defines _TANDEM_SOURCE for NonStop platforms.
+
+** GNU M4 1.4.7 or later is now recommended.
+
+** m4_mkstemp
+ New M4sugar macro, which is more secure than the POSIX M4 maketemp.
+
+** m4_maketemp
+ Now an alias for m4_mkstemp.
+
+* Major changes in Autoconf 2.60a (2006-08-25)
+
+** GNU M4 1.4.6 or later is now recommended.
+
+** The check for C99 now tests for varargs macros, as documented.
+ It also tests that the preprocessor supports 64-bit integers.
+
+** Autoconf now uses constructs like "#ifdef HAVE_STDLIB_H" rather than
+ "#if HAVE_STDLIB_H", so that it now works with "gcc -Wundef -Werror".
+
+** The functionality of the undocumented _AC_COMPUTE_INT is now provided
+ by a public and documented macro, AC_COMPUTE_INT. The parameters to the
+ two macros are different, so autoupdate will not change the old private name
+ to the new one. _AC_COMPUTE_INT may be removed in a future release.
+
+** AC_TYPE_LONG_LONG_INT and AC_TYPE_UNSIGNED_LONG_LONG_INT now require
+ that long long types be at least 64 bits wide, as C99 and tradition
+ requires. Formerly, they accepted implementations of any width.
+
+
+* Major changes in Autoconf 2.60
+
+ Released 2006-06-23, by Ralf Wildenhues.
+
+** Autoconf no longer depends on whether m4wrap is FIFO (as Posix requires)
+ or LIFO (as in GNU M4 1.4.x). GNU M4 2.0 is expected to conform to Posix
+ here, so m4wrap/m4_wrap users should no longer depend on LIFO behavior.
+
+** Provide a way to turn off warnings about the changed directory variables.
+
+* Major changes in Autoconf 2.59d
+
+ Released 2006-06-05, by Ralf Wildenhues.
+
+** GNU make now recommended for VPATH builds
+ INSTALL now suggests VPATH builds (e.g., "sh ../srcdir/configure")
+ only if you use GNU make. In practice, other 'make' implementations
+ have too many subtle incompatibilities in their support for VPATH.
+ Many packages (including Autoconf itself) are portable to other
+ 'make' implementations, but some packages are not, and recommending
+ GNU make keeps the installation instructions simpler.
+
+** Even more safety checks for the new Directory variables:
+ Warn about suspicious `${datarootdir}' found in config files output.
+
+** AC_TRY_COMMAND, AC_TRY_EVAL, ac_config_guess, ac_config_sub, ac_configure
+ These never-documented macros and variables have been marked with
+ comments saying that they may be removed in a future release,
+ because their use can lead to unintended code being executed.
+ If you need functionality that only these macros or variables
+ currently supply, please write bug-autoconf@gnu.org.
+
+** AC_SUBST, AC_DEFINE
+ Literal arguments to these are passed to m4_pattern_allow now.
+
+** AC_PROG_CC_STDC
+ Passing 'ac_cv_prog_cc_stdc=no' to 'configure' now sets ac_cv_prog_cc_c99
+ and ac_cv_prog_cc_c89 to 'no' as well, for backward compatibility with
+ obsolete K&R tests in the Automake test suite.
+
+** AC_PROG_CXX_C_O
+ New macro.
+
+** AC_PROG_MKDIR_P
+ New macro.
+
+** AS_MKDIR_P
+ Now more robust with special characters in file names, or when
+ multiple processes create the same directory at the same time.
+
+** Obsolescent macros
+ The documentation now says that the following macros are obsolescent:
+ they test for problems that are so old that they are no longer of
+ practical importance on current systems.
+
+ AC_C_BACKSLASH_A AC_FUNC_MEMCMP AC_HEADER_DIRENT
+ AC_C_CONST AC_FUNC_SELECT_ARGTYPES AC_HEADER_STAT
+ AC_C_PROTOTYPES AC_FUNC_SETPGRP AC_HEADER_STDC
+ AC_C_STRINGIZE AC_FUNC_SETVBUF_REVERSED AC_HEADER_SYS_WAIT
+ AC_C_VOLATILE AC_FUNC_STAT AC_HEADER_TIME
+ AC_FUNC_CLOSEDIR_VOID AC_FUNC_STRFTIME AC_ISC_POSIX
+ AC_FUNC_GETPGRP AC_FUNC_UTIME_NULL AC_PROG_GCC_TRADITIONAL
+ AC_FUNC_LSTAT AC_FUNC_VPRINTF AC_STRUCT_TM
+
+ New programs need not use these macros. We have no current plans to
+ remove them.
+
+** autoreconf
+ For compatibility with future Libtool 2.0, autoreconf will invoke
+ libtoolize with the option `--ltdl' now, if LT_CONFIG_LTDL_DIR is
+ used.
+
+* Major changes in Autoconf 2.59c
+
+ Released 2006-04-12, by Ralf Wildenhues.
+
+** The configure command now redirects standard input from /dev/null,
+ to help avoid problems with subsidiary commands that might mistakenly
+ read standard input. AS_ORIGINAL_STDIN_FD points to the original
+ standard input before this redirection, if you really want configure to
+ read from standard input.
+
+** Directory variables adjusted to recent changes in the GNU Coding Standards.
+ The following directory variables are new:
+
+ datarootdir read-only architecture-independent data root [PREFIX/share]
+ localedir locale-specific message catalogs [DATAROOTDIR/locale]
+ docdir documentation root [DATAROOTDIR/doc/PACKAGE]
+ htmldir html documentation [DOCDIR]
+ dvidir dvi documentation [DOCDIR]
+ pdfdir pdf documentation [DOCDIR]
+ psdir ps documentation [DOCDIR]
+
+ The following variables have new default values:
+
+ datadir read-only architecture-independent data [DATAROOTDIR]
+ infodir info documentation [DATAROOTDIR/info]
+ mandir man documentation [DATAROOTDIR/man]
+
+ This means that if you use any of `@datadir@', `@infodir@', or
+ `@mandir@' in a file, you will have to ensure `${datarootdir}' is
+ defined in this file. As a temporary measure, if any of those are
+ found but no mention of `datarootdir', the substitutions will be
+ replaced with values that do not contain `${datarootdir}', and a
+ warning will be issued.
+
+** @top_builddir@ is now a dir name: it is always nonempty and doesn't have
+ a trailing slash. Similar change will be made to ac_top_builddir in a
+ future release; the old style value, which matches (../)*, is (and will
+ continue to be) available as ac_top_build_prefix.
+
+** AC_C_TYPEOF
+ New macro to check for support of 'typeof' syntax a la GNU C.
+
+** AC_CHECK_DECLS_ONCE, AC_CHECK_FUNCS_ONCE, AC_CHECK_HEADERS_ONCE
+ New "once-only" variants of commonly-used macros, to make 'configure'
+ smaller and faster in common cases.
+
+** AC_FUNC_STRTOLD
+ New macro to check for strtold with C99 semantics.
+
+** AC_HEADER_ASSERT
+ New macro that lets builder disable assertions at 'configure'-time.
+
+** AC_PATH_X
+ Now checks for X11/Xlib.h and XrmInitialize (X proper) rather than
+ X11/Intrinsic.h and XtMalloc (Xt).
+
+** AC_PRESERVE_HELP_ORDER
+ New macro that causes `configure' to display help strings for AC_ARG_ENABLE
+ and AC_ARG_WITH arguments in one region, in the order defined. The default
+ behavior is to group options of each classes separately.
+
+** AC_PROG_CC, AC_PROG_CXX
+ No longer automatically arrange to declare the 'exit' function of C,
+ when a C++ compiler is used. Standard Autoconf macros no longer use
+ 'exit', so this is no longer an issue for them. If you use C++, and
+ want to call 'exit', you'll have to arrange for its declaration
+ yourself. But we now suggest you return from 'main' instead.
+
+** AC_PROG_CC_C89, AC_PROG_CC_C99
+ New macros for ISO C99 support. AC_PROG_CC_C89 and AC_PROG_CC_C99
+ check for ANSI C89 and ISO C99 support respectively.
+
+** AC_PROG_CC_STDC
+ Has been unobsoleted, and will check if the compiler supports ISO
+ C99, falling back to ANSI C89 if not. ac_cv_prog_cc_stdc is
+ retained for backwards compatibility, assuming the value of
+ ac_cv_prog_cc_c99 or ac_cv_prog_cc_c89 (whichever is valid, in
+ that order).
+
+** AC_STRUCT_DIRENT_D_INO, AC_STRUCT_DIRENT_D_TYPE
+ New macros for checking commonly-used members of struct dirent.
+
+** AC_SUBST
+ The substituted value can now contain newlines.
+
+** AC_SUBST_FILE
+ The substitution now occurs only when @variable@ is on a line by itself,
+ optionally surrounded by spaces and tabs. The whole line is replaced.
+
+** AC_TYPE_LONG_DOUBLE, AC_TYPE_LONG_DOUBLE_WIDER
+ New macros to check for long double, and whether it is wider than double.
+ The old macro AC_C_TYPE_LONG_DOUBLE has been marked as obsolete;
+ applications should switch to the new macro.
+
+** AC_TYPE_INT8_T, AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T,
+ AC_TYPE_INTMAX_T, AC_TYPE_INTPTR_T, AC_TYPE_LONG_LONG_INT, AC_TYPE_SSIZE_T,
+ AC_TYPE_UINT8_T, AC_TYPE_UINT16_T, AC_TYPE_UINT32_T, AC_TYPE_UINT64_T,
+ AC_TYPE_UINTMAX_T, AC_TYPE_UINTPTR_T, AC_TYPE_UNSIGNED_LONG_LONG_INT
+ New macros to check for C99 and POSIX types.
+
+** AC_USE_SYSTEM_EXTENSIONS
+ New macro to enable extensions to Posix.
+
+** AH_HEADER
+ New macro which is defined to the name of the first declared config header
+ or undefined if no config headers have been declared yet.
+
+** AS_HELP_STRING
+ The macro correctly handles quadrigraphs now.
+
+** AS_BOURNE_COMPATIBLE, AS_SHELL_SANITIZE, AS_CASE
+ These macros are new or published now.
+
+** AT_COPYRIGHT
+ New macro for copyright notices in testsuite files.
+
+** ALLOCA, LIBOBJS, LTLIBOBJS
+ Object names added to these variables are now prefixed with `${LIBOBJDIR}',
+ as in `${LIBOBJDIR}alloca.o'. LIBOBJDIR is meant to be defined from
+ `Makefile.in' in case the object files lie in a different directory.
+ The LIBOBJDIR feature is experimental.
+
+** autoreconf
+ Supports --no-recursive now.
+
+** New macros to support Erlang/OTP.
+ New macros for configuring paths to Erlang tools and libraries:
+ AC_ERLANG_PATH_ERLC, AC_ERLANG_NEED_ERLC, AC_ERLANG_PATH_ERL,
+ AC_ERLANG_NEED_ERL, AC_ERLANG_CHECK_LIB, AC_ERLANG_SUBST_ROOT_DIR,
+ AC_ERLANG_SUBST_LIB_DIR.
+
+ New macros for configuring installation of Erlang libraries:
+ AC_ERLANG_SUBST_INSTALL_LIB_DIR, AC_ERLANG_SUBST_INSTALL_LIB_SUBDIR.
+
+** The manual now mentions Gnulib more prominently.
+
+** New macros to support Objective C.
+ AC_PROG_OBJC, AC_PROG_OBJCPP.
+
+* Major changes in Autoconf 2.59b
+
+ Released 2004-08-20, by Paul Eggert.
+
+** AC_CHECK_ALIGNOF
+ New macro that computes the default alignment of a type.
+
+** AC_CHECK_TOOL, AC_PATH_TOOL, AC_CHECK_TOOLS
+ When cross-compiling, these macros will give a warning if the tool
+ is not prefixed. In the future, unprefixed cross tools will not
+ be detected; please consult the info documentation for information
+ about the reason of this change.
+
+** AC_CHECK_TARGET_TOOL, AC_PATH_TARGET_TOOL, AC_CHECK_TARGET_TOOLS
+ New macros that detect programs whose name is prefixed with the
+ target type, if the build type and target type are different.
+
+** AC_REQUIRE_AUX_FILE
+ New trace macro that declares expected auxiliary files.
+
+** AC_PROG_GREP
+ New macro that tests for a grep program that accepts as a long a line
+ as possible.
+
+** AC_PROG_EGREP, AC_PROG_FGREP
+ These macros now require AC_PROG_GREP, and try EGREP="$GREP -E" and
+ FGREP="$GREP -F" respectively if possible, or else run a path search for
+ a program that accepts as long a line as possible.
+
+** AC_PROG_SED
+ New macro that tests for a sed program that truncates as few characters
+ as possible.
+
+* Major changes in Autoconf 2.59
+
+ Released 2003-11-04, by Akim Demaille
+
+** ac_abs_builddir etc.
+ Absolute file names were actually relative in 2.58.
+
+* Major changes in Autoconf 2.58
+
+ Released 2003-11-04, by Akim Demaille
+
+** core.*
+ core.* files are no longer removed, as they may be valid user files.
+
+** autoreconf and auxiliary directory
+ Autoreconf creates the auxiliary directory if needed. This is
+ especially useful for initial "bootstrapping" of fresh CVS checkouts.
+
+** AC_CONFIG_MACRO_DIR
+ Use this macro to declare the directory for local M4 macros for aclocal.
+
+** AC_LIBOBJS
+ No longer includes twice the same file in LIBOBJS if invoked
+ multiple times.
+
+** AC_CONFIG_COMMANDS
+ The directory for its first argument is automatically created. For
+ instance, with
+
+ AC_CONFIG_COMMANDS([src/modules.hh], [...])
+
+ $top_builddir/src/ is created if needed.
+
+** Autotest and local.at
+ The optional file local.at is always included in Autotest test suites.
+
+** Warnings
+ The warnings are always issued, including with cached runs.
+ This became a significant problem since aclocal and automake can
+ run autoconf behind the scene.
+
+** autoheader warnings
+ The warnings of autoheader can be turned off, using --warning.
+ For instance, -Wno-obsolete disables the complaints about acconfig.h
+ and other deprecated constructs.
+
+** New macros
+ AC_C_RESTRICT, AC_INCLUDES_DEFAULT, AC_LANG_ASSERT, AC_LANG_WERROR,
+ AS_SET_CATFILE.
+
+** AC_DECL_SYS_SIGLIST
+ Works again.
+
+** AC_FUNC_MKTIME
+ Now checks that mktime is the inverse of localtime.
+
+** Improve DJGPP portability
+ The Autoconf tools and configure behave better under DJGPP.
+
+** Present But Cannot Be Compiled
+ New FAQ section dedicated to the mystic
+
+ configure: WARNING: pi.h: present but cannot be compiled
+ configure: WARNING: pi.h: check for missing prerequisite headers?
+ configure: WARNING: pi.h: proceeding with the preprocessor's result
+ messages.
+
+** Concurrent executions of autom4te
+ autom4te now locks its internal files, which enables concurrent
+ executions of autom4te, likely to happen if automake, autoconf,
+ autoheader etc. are run simultaneously.
+
+** Libtool
+ Use of Libtool 1.5 and higher is encouraged. Compatibility with
+ Libtool pre-1.4 is not checked.
+
+** Autotest
+ Testsuites no longer rerun failed tests in verbose mode; instead,
+ failures are logged while the test is run.
+
+ In addition, expected failures can be marked as such.
+
+* Major changes in Autoconf 2.57
+
+ Released 2002-12-03 by Paul Eggert.
+
+Bug fixes for problems with AIX linker, with freestanding C compilers,
+with GNU M4 limitations, and with obsolete copies of GNU documents.
+
+The Free Documentation License has been upgraded from 1.1 to 1.2.
+
+* Major changes in Autoconf 2.56
+
+ Released 2002-11-15 by Akim Demaille.
+
+One packaging problem fixed (config/install-sh was not executable).
+
+* Major changes in Autoconf 2.55
+
+ Released 2002-11-14 by Akim Demaille.
+
+Release tips:
+
+ Have your configure.ac checked by autoscan ("autoscan").
+ Try the warning options ("autoreconf -fv -Wall").
+
+** Documentation
+
+- AC_CHECK_HEADER, AC_CHECK_HEADERS
+ More information on proper use.
+
+- Writing Test Programs
+
+ This sections explains how to write good test sources to use with
+ AC_COMPILE_IFELSE etc. It documents AC_LANG_PROGRAM and so forth.
+
+- AC_FOO_IFELSE vs. AC_TRY_FOO
+
+ Explains why Autoconf moves from AC_TRY_COMPILE etc. to
+ AC_COMPILE_IFELSE and AC_LANG_PROGRAM etc.
+
+** autoreconf
+
+- Is more robust to different Gettext installations.
+
+- Produces messages (when --verbose) to be understood by Emacs'
+ compile mode.
+
+- Supports -W/--warnings.
+
+- -m/--make
+ Once the GNU Build System reinstalled, run `./config.status
+ --recheck && ./config.status && make' if possible.
+
+** autom4te
+
+- Supports --cache, and --no-cache.
+
+- ~/.autom4te.cfg makes it possible to disable the caching mechanism
+ (autom4te.cache). See `Customizing autom4te' in the documentation.
+
+** config.status
+ Supports --quiet.
+
+** Obsolete options
+
+ Support for the obsoleted options -m, --macrodir, -l, --localdir is
+ dropped in favor of the safer --include/--prepend-include scheme.
+
+** Macros
+
+- New macros
+ AC_COMPILER_IFELSE, AC_FUNC_MBRTOWC, AC_HEADER_STDBOOL,
+ AC_LANG_CONFTEST, AC_LANG_SOURCE, AC_LANG_PROGRAM, AC_LANG_CALL,
+ AC_LANG_FUNC_TRY_LINK, AC_MSG_FAILURE, AC_PREPROC_IFELSE.
+
+- Obsoleted
+ Obsoleted macros are kept for Autoconf backward compatibility, but
+ should be avoided in configure.ac. Running autoupdate is advised.
+ AC_DECL_SYS_SIGLIST.
+
+- AC_DEFINE/AC_DEFINE_UNQUOTED
+
+ We have to stop using the old compatibility scheme --that tried to
+ avoid useless backslashes-- because Libtool 1.4.3 contains a
+
+ AC_DEFINE([error_t], [int],
+ [Define to a type to use for \`error_t' if it is not
+ otherwise available.])
+
+ We have to quote the single quotes and backslashes with \. The old
+ compatibility scheme saw that ` was backslashed, and therefore did
+ not quote the single quote... Failure. Hence, Autoconf 2.54 is not
+ compatible with Libtool. Autoconf 2.55 is, but in some cases might
+ produce more \ than wanted.
+
+ Please, note that in the future the same problem will happen with
+ AC_MSG_*: use `autoreconf -f -Wall'.
+
+** Bug Fixes
+
+- Portability of the Autoconf package to Solaris.
+
+- Spurious warnings caused by config.status.
+ This bug is benign, but painful: on some systems (typically
+ FreeBSD), warnings such as:
+
+ config.status: creating Makefile
+ mv: Makefile: set owner/group (was: 1357/0): Operation not permitted
+
+ could be issued. This is fixed.
+
+- Parallel Builds
+ Simultaneous executions of config.status are possible again.
+
+- Precious variables accumulation
+
+ config.status could stack several copies of the precious variables
+ assignments.
+
+
+** Plans for later versions
+
+- ./configure
+
+ The compatibility hooks with the old scheme will be completely
+ removed. Please, advice/use `--build', `--host', and `--target'
+ only.
+
+- AC_CHECK_HEADER, AC_CHECK_HEADERS
+
+ The tests will be stricter, please make sure your invocations are
+ valid.
+
+- shell functions
+
+ Shell functions will gradually be introduced, probably starting with
+ Autotest. If you know machines which are in use that you suspect
+ *not* to support shell functions, please run the test suite of
+ Autoconf 2.55 on it, and report the results to
+ bug-autoconf@gnu.org.
+
+- AC_MSG_*
+
+ Special characters in AC_MSG_* need not be quoted. Currently,
+ Autoconf has heuristics to decide when a string is escaped, or has
+ to be escaped. This scheme is fragile, and will be removed; the
+ only risk is uglified messages. Please, run `autoreconf -f -Wall'
+ to find occurrences that will be affected.
+
+* Major changes in Autoconf 2.54
+
+ Released 2002-09-13 by Akim Demaille.
+
+** Executables
+
+- autoreconf no longer changes the version of the gettext/po/intl
+ support files. It now adds the files the correspond to the
+ AM_GNU_GETTEXT_VERSION declared in configure.ac.
+
+ Warning: It now relies on the 'autopoint' program, which is part
+ of GNU gettext 0.11.4 and newer.
+
+ Please note that you need to have a GNU gettext version that
+ corresponds at least to the AM_GNU_GETTEXT_VERSION declared
+ in configure.ac. You can upgrade to newer GNU gettext versions,
+ though, without needing to change configure.ac.
+
+- The -I DIR or --include=DIR option now appends DIR to the include path
+ instead of prepending; this is for consistency with other GNU tools.
+ The new -B DIR or --prepend-include=DIR option has the old behavior.
+
+** Macros
+
+- AC_OUTPUT
+ Now handles all the gory details about LIBOBJS and LTLIBOBJS.
+ Please, remove lines such as
+
+ # This is necessary so that .o files in LIBOBJS are also
+ # built via the ANSI2KNR-filtering rules.
+ LIBOBJS=`echo $LIBOBJS|sed 's/\.o /\$U.o /g;s/\.o$/\$U.o/'`
+
+ and read the `AC_LIBOBJ vs LIBOBJS' section. Do not define U in
+ your Makefiles either.
+
+- AC_CONFIG_LINKS now makes copies if it can't make links.
+
+- AC_FUNC_FNMATCH now tests only for POSIX compatibility, reverting to
+ Autoconf 2.13 behavior. The new macro AC_FUNC_FNMATCH_GNU also
+ tests for GNU extensions to fnmatch, and replaces fnmatch if needed.
+
+- AC_FUNC_SETVBUF_REVERSED no longer fails when cross-compiling.
+
+- AC_PROG_CC_STDC is integrated into AC_PROG_CC.
+
+- AC_PROG_F77 default search no longer includes cf77 and cfg77.
+
+- New macros
+
+ AC_C_BACKSLASH_A, AC_CONFIG_LIBOBJ_DIR, AC_GNU_SOURCE,
+ AC_PROG_EGREP, AC_PROG_FGREP, AC_REPLACE_FNMATCH,
+ AC_FUNC_FNMATCH_GNU, AC_FUNC_REALLOC, AC_TYPE_MBSTATE_T.
+
+- AC_FUNC_GETLOADAVG
+ looks for getloadavg.c in the CONFIG_LIBOBJ_DIR.
+
+- AC_FUNC_MALLOC
+ Now defines HAVE_MALLOC to 0 if `malloc' does not work, and asks
+ for an AC_LIBOBJ replacement.
+
+** Bug fixes
+
+- Spurious complaints from `m4_bmatch' about invalid regular
+ expressions are suppressed.
+
+- Empty top_builddirs are properly handled.
+
+- AC_CHECK_MEMBER works correctly when the member is an aggregate.
+
+- AC_PATH_PROG
+ Now colon in the optional path arguments are properly handled.
+
+** Improved portability
+
+- Both Autoconf the package, and the scripts it produces, should run
+ more reliably with Zsh. Bear in mind it is the default Bourne shell
+ on Darwin.
+
+- Autoconf and the scripts it produces no longer assume the existence of
+ the obsolescent commands egrep and fgrep.
+
+** Documentation
+
+- Limitations of Make
+ More of them.
+
+- GNATS
+ The GNATS base moved to
+ https://bugs.gnu.org/cgi-bin/gnatsweb.pl?database=autoconf
+ (It is no longer available, though.)
+
+** Misc.
+
+- config.log
+ Now contains the list of output variables and files (AC_SUBST,
+ AC_SUBST_FILES).
+
+* Major changes in Autoconf 2.53
+
+ Released 2002-03-08 by Akim Demaille.
+
+** Requirements
+
+ Perl 5.005_03 or later is required: autom4te is written in Perl and is
+ needed by autoconf. autoheader, autoreconf, ifnames, and autoscan are
+ rewritten in Perl.
+
+** Documentation
+
+- AC_INIT
+ Argument requirements, output variables, defined macros.
+- M4sugar, M4sh, Autotest
+ First sketch.
+- Double quoting macros
+ AC_TRY_CPP, AC_TRY_COMPILE, AC_TRY_LINK and AC_TRY_RUN.
+- Licensing
+ The Autoconf manual is now distributed under the terms of the GNU FDL.
+- Section `Hosts and Cross-Compilation'
+ Explains the rationale for the 2.5x changes in the cross-compilation
+ chain, and in the relationships between build, host, and target
+ types.
+ Emphasizes that `cross-compilation' == `--host is given'.
+ If you are working on compilers etc., be sure to read this section.
+- Section `AC_LIBOBJ vs. LIBOBJS'
+ Explains why assigning LIBOBJS directly is now an error.
+ Details how to update the code.
+
+** configure
+
+- $LINENO
+ Now used instead of hard coded line numbers.
+ This eases the comparison of `configure's, and diminishes the
+ pressure over control version archives.
+ Automatic replacement for shells that don't support this feature.
+- New output variables
+ @builddir@, @top_builddir@, @abs_srcdir@, @abs_top_srcdir@, @abs_builddir@,
+ @abs_top_builddir@.
+
+** Emacs
+
+ Autoconf and Autotest modes are provided.
+
+** Executables
+
+- autom4te
+ New, used by the Autoconf suite to cache and speed up most processing.
+- --force, -f
+ Supported by autom4te, autoconf and autoheader.
+- --include, -I
+ Replaces --autoconf-dir and --localdir in autoconf, autoheader,
+ autoupdate, and autoreconf.
+- autoreconf
+ No longer passes --cygnus, --foreign, --gnits, --gnu, --include-deps:
+ automake options are to be given via AUTOMAKE_OPTIONS.
+- autoreconf
+ Runs gettextize and libtoolize when appropriate.
+- autoreconf
+ --m4dir is no longer supported.
+- autoreconf
+ Now runs only in the specified directories, defaulting to `.',
+ but understands AC_CONFIG_SUBDIRS for dependent directories.
+ Before, it used to run on all the `configure.ac' found in the
+ current tree.
+ Independent packages are properly updated.
+
+** Bug fixes
+
+- The top level $prefix is propagated to the AC_CONFIG_SUBDIRS configures.
+- AC_TRY_RUN
+ Under the user pressure, $? is finally available. Probably a mistake.
+- AC_F77_LIBRARY_LDFLAGS now supports the HP/UX f90 compiler.
+- Precious variables accumulation
+ config.status could stack several copies of the precious variables
+ assignments.
+- AC_PATH_PROG and family.
+ Works properly when given a literal path.
+- AC_FUNC_SETPGRP
+ Somewhere since 2.13, the result had been reversed.
+
+** C Macros
+
+- AC_C_BIGENDIAN supports the cross-compiling case.
+- AC_C_BIGENDIAN accepts ACTION-IF-TRUE, ACTION-IF-FALSE, and
+ ACTION-IF-UNKNOWN arguments. All are optional, and the default
+ for ACTION-IF-TRUE is to define WORDS_BIGENDIAN like AC_C_BIGENDIAN
+ always did.
+- AC_C_LONG_DOUBLE now succeeds only if `long double' has more range or
+ precision than `double'.
+
+** Generic macros
+
+- AC_INIT
+ It now defines the preprocessor symbols PACKAGE_NAME,
+ PACKAGE_TARNAME, PACKAGE_VERSION, PACKAGE_STRING, and
+ PACKAGE_BUGREPORT.
+
+- AC_INIT
+ Admits a fourth optional parameter: the tar name.
+
+- AC_CONFIG_COMMANDS, HEADERS, FILES, LINKS.
+ Provide the user with srcdir, ac_srcdir, ac_top_srcdir, ac_builddir,
+ ac_top_builddir, ac_abs_srcdir, ac_abs_top_srcdir, ac_abs_builddir,
+ ac_abs_top_builddir.
+
+- AC_CONFIG_COMMANDS, HEADERS, FILES, LINKS and AC_OUTPUT.
+ Are much less expensive when using long lists of files.
+
+- AC_PREFIX_PROGRAM
+ Works with shell variables, and non alphanumeric names.
+
+** Library macros
+
+- AC_FUNC_STRERROR_R now sets STRERROR_R_CHAR_P, not HAVE_WORKING_STRERROR_R,
+ because POSIX 1003.1-200x draft 7 says strerror_r returns int, not char *.
+
+- AC_FUNC_STRTOD substitutes POW_LIB.
+
+- AC_FUNC_STRNLEN
+ New.
+
+* Major changes in Autoconf 2.52
+
+ Released 2001-07-18 by Akim Demaille.
+
+** Documentation
+- AC_ARG_VAR
+- Quadrigraphs
+ This feature was present in autoconf 2.50 but was not documented.
+ For example, `@<:@' is translated to `[' just before output. This
+ is useful when writing strings that contain unbalanced quotes, or
+ other hard-to-quote constructs.
+- m4_pattern_forbid, m4_pattern_allow
+- Tips for upgrading from 2.13.
+- Using autoscan to maintain a configure.ac.
+
+** Default includes
+- Now include stdint.h.
+- sys/types.h and sys/stat.h are guarded.
+- strings.h is included if available, and not conflicting with string.h.
+
+** Bug fixes
+- The test suite is more robust and presents less false failures.
+- Invocation of GNU M4 now robust to POSIXLY_CORRECT.
+- configure accepts --prefix='' again.
+- AC_CHECK_LIB works properly when its first argument is not a
+ literal.
+- HAVE_INTTYPES_H is defined only if not conflicting with sys/types.h.
+- build_, host_, and target_alias are AC_SUBST as in 2.13.
+- AC_ARG_VAR properly propagates precious variables inherited from the
+ environment to ./config.status.
+- Using --program-suffix/--program-prefix is portable.
+- Failures to detect the default compiler's output extension are less
+ likely.
+- `config.status foo' works properly when `foo' depends on variables
+ set in an AC_CONFIG_THING INIT-CMD.
+- autoheader is more robust to broken input.
+- Fixed Fortran name-mangling and link tests on a number of systems,
+ e.g. NetBSD; see AC_F77_DUMMY_MAIN, below.
+
+** Generic macros
+- AC_CHECK_HEADER and AC_CHECK_HEADERS support a fourth argument to
+ specify pre-includes. In this case, the headers are compiled with
+ cc, not merely preprocessed by cpp. Therefore it is the _usability_
+ of a header which is checked for, not just its availability.
+- AC_ARG_VAR refuses to run configure when precious variables have
+ changed.
+- Versions of compilers are dumped in the logs.
+- AC_CHECK_TYPE recognizes use of `foo_t' as a replacement type.
+
+** Specific Macros
+- AC_PATH_XTRA only adds -ldnet to $LIBS if it's needed to link.
+- AC_FUNC_WAIT3 and AC_SYS_RESTARTABLE_SYSCALLS are obsoleted.
+- AM_FUNC_ERROR_AT_LINE, AM_FUNC_FNMATCH, AM_FUNC_MKTIME,
+ AM_FUNC_OBSTACK, and AM_FUNC_STRTOD are now activated.
+ Be sure to read `Upgrading from Version 2.13' to understand why
+ running `autoupdate' is needed.
+- AC_F77_DUMMY_MAIN, AC_F77_MAIN: new macros to detect whether
+ a main-like routine is required/possible when linking C/C++ with
+ Fortran. Users of e.g. AC_F77_WRAPPERS should be aware of these.
+- AC_FUNC_GETPGRG behaves better when cross-compiling.
+
+* Major changes in Autoconf 2.51
+There was no release of Autoconf 2.51 since some packagers had used
+this version number without permission to ship intermediary versions
+of 2.50. The version was skipped to avoid confusion.
+
+* Major changes in Autoconf 2.50
+
+ Released 2001-05-21 by Akim Demaille.
+
+** Lots of bug fixes
+There have been far too many to enumerate them here. Check out
+ChangeLog if you really want to know more.
+
+** Improved documentation
+In particular, portability issues are better covered.
+
+** Use of Automake
+All the standard GNU Makefile targets are supported. The layout has
+changed: m4/ holds the M4 extensions Autoconf needs for its
+configuration, doc/ contains the documentation, and tests/ contains
+the test suite.
+
+** Man pages are provided
+For autoconf, autoreconf, autoupdate, autoheader, autoscan, ifnames,
+config.guess, config.sub.
+
+** autoconf
+- --trace
+ Provides a safe and powerful means to trace the macro uses. This
+ provide the parsing layer for tools which need to `study'
+ configure.in.
+
+- --warnings
+ Specify what category of warnings should be enabled.
+
+- When recursing into subdirectories, try for configure.gnu before
+ configure to adapt for packages not using autoconf on case-insensitive
+ file systems.
+
+- Diagnostics
+ More errors are now caught (circular AC_REQUIRE dependencies,
+ AC_DEFINE in the action part of an AC_CACHE_CHECK, too many pops
+ etc.). In addition, their location and call stack are given.
+
+** autoupdate
+autoupdate is much more powerful, and is able to provide the glue code
+which might be needed to move from an old macro to its newer
+equivalent.
+
+You are strongly encouraged to use it to modernize both your
+`configure.in' and your .m4 extension files.
+
+** autoheader
+The internal machinery of autoheader has completely changed. As a
+result, using `acconfig.h' should be considered to be obsoleted, and
+you are encouraged to get rid of it using the AH macros.
+
+** autoreconf
+Extensive overhaul.
+
+** Fortran 77 compilers
+Globally, the support for Fortran 77 is considerably improved.
+
+Support for automatically determining a Fortran 77 compiler's
+name-mangling scheme. New CPP macros F77_FUNC and F77_FUNC_ are
+provided to wrap C/C++ identifiers, thus making it easier and more
+transparent for C/C++ to call Fortran 77 routines, and Fortran 77 to
+call C/C++ routines. See the Texinfo documentation for details.
+
+** Test suite
+The test suite no longer uses DejaGNU. It should be easy to submit
+test cases in this new framework.
+
+** configure
+- --help, --help=long, -hl
+ no longer dumps useless items.
+- --help=short, -hs
+ lists only specific options.
+- --help=recursive, -hr
+ displays the help of all the embedded packages.
+- Remembers environment variables when reconfiguring.
+ The previous scheme to set envvar before running configure was
+ ENV=VAL ./configure
+ what prevented configure from remembering the environment in which
+ it was run, therefore --recheck was run in an inconsistent
+ environment. Now, one should run
+ ./configure ENV=VAR
+ and then --recheck will work properly. Variables declared with
+ AC_ARG_VAR are also preserved.
+- cross-compilation
+ $build defaults to `config.guess`, $host to $build, and then $target
+ to $host.
+ Cross-compilation is a global status of the package, it no longer
+ depends upon the current language.
+ Cross compilation is enabled iff the user specified `--host'.
+ `configure' now fails if it can't run the executables it compiles,
+ unless cross-compilation is enabled.
+- Cache file
+ The cache file is disabled by default. The new options
+ `--config-cache', `-C' set the cache to `config.cache'.
+
+** config.status
+- faster
+ Much faster on most architectures.
+- concurrent executions
+ It is safe to use `make -j' with config.status.
+- human interface improved
+ It is possible to invoke
+ ./config.status foobar
+ instead of the former form (still valid)
+ CONFIG_COMMANDS= CONFIG_HEADERS= CONFIG_LINKS= \
+ CONFIG_FILES=foobar:foo.in:bar.in \
+ ./config.status
+ The same holds for configuration headers and links.
+ You can instantiate unknown files and headers:
+ ./config.status --header foo.h:foo.h.in --file bar:baz
+- has a useful --help
+- accepts special file name "-" for stdin/stdout
+
+
+** Identity Macros
+- AC_COPYRIGHT
+ Specify additional copyright information.
+
+- AC_INIT
+ Now expects the identity of the package as argument.
+
+** General changes.
+- Uniform quotation
+ Most macros, if not all, now strictly follow the `one quotation
+ level' rule. This results in a more predictable expansion.
+
+- AC_REQUIRE
+ A sly bug in the AC_REQUIRE machinery, which could produce incorrect
+ configure scripts, was fixed by Axel Thimm.
+
+** Setup Macros
+- AC_ARG_VAR
+ Document and ask for the registration of an envvar.
+
+- AC_CONFIG_SRCDIR
+ Specifies the file which `configure' should look for when trying to
+ find the source tree (used to be handled by AC_INIT).
+
+- AC_CONFIG_COMMANDS
+ To add new actions to config.status. Should be used instead of
+ AC_OUTPUT_COMMANDS.
+
+- AC_CONFIG_LINKS
+ Replaces AC_LINK_FILES.
+
+- AC_CONFIG_HEADERS, AC_CONFIG_COMMANDS, AC_CONFIG_SUBDIRS,
+ AC_CONFIG_LINKS, and AC_CONFIG_FILES
+ They now obey sh: you should no longer use shell variables as
+ argument. Instead of
+
+ test "$package_foo_enabled" = yes && $my_subdirs="$my_subdirs foo"
+ AC_CONFIG_SUBDIRS($my_subdirs)
+
+ write
+
+ if test "$package_foo_enabled" = yes; then
+ AC_CONFIG_SUBDIRS(foo)
+ fi
+
+- AC_HELP_STRING
+ To format an Autoconf macro's help string so that it looks pretty
+ when the user executes `configure --help'.
+
+
+** Generic Test Macros
+- AC_CHECK families
+ The interface of the AC_CHECK families of macros (decl, header,
+ type, member, func) is now uniform. They support the same set of
+ default includes.
+
+- AC_CHECK_DECL, AC_CHECK_DECLS
+ To check whether a symbol is declared.
+
+- AC_CHECK_SIZEOF, AC_C_CHAR_UNSIGNED.
+ No longer need a cross-compilation default.
+
+- AC_CHECK_TYPE
+ The test it performs is much more robust than previously, and makes
+ it possible to test builtin types in addition to typedefs.
+ It is now schizophrenic:
+ - AC_CHECK_TYPE(TYPE, REPLACEMENT)
+ remains for backward compatibility, but its use is discouraged.
+ - AC_CHECK_TYPE(TYPE, IF-FOUND, IF-NOT-FOUND, INCLUDES)
+ behaves exactly like the other AC_CHECK macros.
+
+- AC_CHECK_TYPES
+ Checks whether given types are supported by the system.
+
+- AC_CHECK_MEMBER, AC_CHECK_MEMBERS
+ Check for given members in aggregates (e.g., pw_gecos in struct
+ passwd).
+
+- AC_PROG_CC_STDC
+ Checks if the compiler supports ISO C, included when needs special
+ options.
+
+- AC_PROG_CPP
+ Checking whether the preprocessor indicates missing includes by the
+ error code. stderr is checked by AC_TRY_CPP only as a fallback.
+
+- AC_LANG
+ Takes a language as argument and replaces AC_LANG_C,
+ AC_LANG_CPLUSPLUS and AC_LANG_FORTRAN77.
+
+- AC_LANG_PUSH, AC_LANG_POP
+ Are preferred to AC_LANG_SAVE, AC_LANG_RESTORE.
+
+** Specific Macros
+- AC_FUNC_CHOWN, AC_FUNC_MALLOC, AC_FUNC_STRERROR_R,
+ AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK, AC_FUNC_STAT, AC_FUNC_LSTAT,
+ AC_FUNC_ERROR_AT_LINE, AC_FUNC_OBSTACK, AC_FUNC_STRTOD, AC_FUNC_FSEEKO.
+ New.
+
+- AC_FUNC_GETGROUPS
+ Sets GETGROUPS_LIBS.
+
+- AC_FUNC_GETLOADAVG
+ Defines `HAVE_STRUCT_NLIST_N_UN_N_NAME' instead of `NLIST_NAME_UNION'.
+
+- AC_PROG_LEX
+ Now integrates `AC_DECL_YYTEXT' which is obsoleted.
+
+- AC_SYS_LARGEFILE
+ Arrange for large-file support.
+
+- AC_EXEEXT, AC_OBJEXT
+ You are no longer expected to use them: their computation is
+ performed by default.
+
+** C++ compatibility
+ Every macro has been revisited in order to support at best CC=c++.
+
+Major changes in Autoconf 2.14:
+ There was no release of GNU Autoconf 2.14.
+
+Major changes in Autoconf 2.13:
+
+ Released 1999-05-01 by Ben Elliston.
+
+* Support for building on 32-bit Windows systems where the only available C or
+ C++ compiler is the Microsoft Visual C++ command line compiler
+ (`cl'). Additional support for building on 32-bit Windows systems which are
+ using the Cygwin or Mingw32 environments.
+* Support for alternative object file and executable file extensions.
+ On 32-bit Windows, for example, these are .obj and .exe. These are discovered
+ using AC_OBJEXT and AC_EXEEXT, which substitute @OBJEXT@ and
+ @EXEEXT@ in the output, respectively.
+* New macros: AC_CACHE_LOAD, AC_CACHE_SAVE, AC_FUNC_SELECT_ARGTYPES,
+ AC_VALIDATE_CACHED_SYSTEM_TUPLE, AC_SEARCH_LIBS, AC_TRY_LINK_FUNC,
+ AC_C_STRINGIZE, AC_CHECK_FILE(S), AC_PROG_F77 (and friends).
+* AC_DEFINE now has an optional third argument for a description to be
+ placed in the config header input file (e.g. config.h.in).
+* The C++ code fragment compiled for the C++ compiler test had to be
+ improved to include an explicit return type for main(). This was
+ causing failures on systems using recent versions of the EGCS C++
+ compiler.
+* Fixed an important bug in AC_CHECK_TYPE that would cause a configure
+ script to report that `sometype_t' was present when only `type_t'
+ was defined.
+* Merge of the FSF version of config.guess and config.sub to modernize
+ these scripts. Add support for a few new hosts in config.guess.
+ Incorporate latest versions of install-sh, mkinstalldirs and
+ texinfo.tex from the FSF.
+* autoreconf is capable of running automake if necessary (and
+ applicable).
+* Support for Fortran 77. See the Texinfo documentation for details.
+* Bug fixes and workarounds for quirky bugs in vendor utilities.
+
+Major changes in Autoconf 2.12:
+
+ Released 1996-11-26 by David J. MacKenzie
+
+* AC_OUTPUT and AC_CONFIG_HEADERS can create output files by
+ concatenating multiple input files separated by colons, like so:
+ AC_CONFIG_HEADERS([config.h:conf.pre:config.h.in:conf.post])
+ AC_OUTPUT([Makefile:Makefile.in:Makefile.rules])
+ The arguments may be shell variables, to compute the lists on the fly.
+* AC_LINK_FILES and AC_CONFIG_SUBDIRS may be called multiple times.
+* New macro AC_OUTPUT_COMMANDS adds more commands to run in config.status.
+* Bug fixes.
+
+Major changes in Autoconf 2.11:
+
+ Released November 18th, 1996, by David J. MacKenzie
+
+* AC_PROG_CC and AC_PROG_CXX check whether the compiler works.
+ They also default CFLAGS/CXXFLAGS to "-g -O2" for gcc, instead of "-g -O".
+* AC_REPLACE_FUNCS defines HAVE_foo if the system has the function `foo'.
+* AC_CONFIG_HEADERS expands shell variables in its argument.
+* New macros: AC_FUNC_FNMATCH, AC_FUNC_SETPGRP.
+* The "checking..." messages and the source code for test programs that
+ fail are saved in config.log.
+* Another workaround has been added for seds with small command length limits.
+* config.sub and config.guess recognize more system types.
+* Bug fixes.
+
+Major changes in Autoconf 2.10:
+
+ Released May 7th, 1996, by Roland McGrath
+
+* Bug fixes.
+* The cache variable names used by `AC_CHECK_LIB(LIB, FUNC, ...)' has
+ changed: now $ac_cv_lib_LIB_FUNC, previously $ac_cv_lib_LIB.
+
+Major changes in Autoconf 2.9:
+
+ Released March 16th, 1996, by Roland McGrath
+
+* Bug fixes.
+
+Major changes in Autoconf 2.8:
+
+ Released March 8th, 1996, by Roland McGrath
+
+* Bug fixes.
+
+Major changes in Autoconf 2.7:
+
+ Released November 22nd, 1995, by David J. MacKenzie
+
+* Bug fixes.
+
+Major changes in Autoconf 2.6:
+
+ Released November 20th, 1995, by David J. MacKenzie
+
+* Bug fixes.
+
+Major changes in Autoconf 2.5:
+
+ Released November 17th, 1995, by Roland McGrath
+
+* New configure options --bindir, --libdir, --datadir, etc., with
+ corresponding output variables.
+* New macro: AC_CACHE_CHECK, to make using the cache easier.
+* config.log contains the command being run as well as any output from it.
+* AC_CHECK_LIB can check for libraries with "." or "/" or "+" in their name.
+* AC_PROG_INSTALL doesn't cache a name for install-sh, for sharing caches.
+* AC_CHECK_PROG, AC_PATH_PROG, AC_CHECK_PROGS, AC_PATH_PROGS, and
+ AC_CHECK_TOOL can search a path other than $PATH.
+* AC_CHECK_SIZEOF takes an optional size to use when cross-compiling.
+
+Major changes in Autoconf 2.4:
+
+ Released June 14th, 1995, by David J. MacKenzie
+
+* Fix a few bugs found by Emacs testers.
+
+Major changes in Autoconf 2.3:
+
+ Released March 27th, 1995, by David J. MacKenzie
+
+* Fix the cleanup trap in several ways.
+* Handle C compilers that are picky about option placement.
+* ifnames gets the version number from the right directory.
+
+Major changes in Autoconf 2.2:
+
+ Released March 8th, 1995, by David J. MacKenzie
+
+* The ifnames utility is much faster but requires a "new awk" interpreter.
+* AC_CHECK_LIB and AC_HAVE_LIBRARY check and add the new
+ library before existing libs, not after, in case it uses them.
+* New macros: AC_FUNC_GETPGRP, AC_CHECK_TOOL.
+* Lots of bug fixes.
+* Many additions to the TODO file :-)
+
+Major changes in Autoconf 2.1:
+
+ Released November 4th, 1994, by David J. MacKenzie
+
+* Fix C++ problems.
+* More explanations in the manual.
+* Fix a spurious failure in the testsuite.
+* Clarify some warning messages.
+* autoreconf by default only rebuilds configure and config.h.in files
+ that are older than any of their particular input files; there is a
+ --force option to use after installing a new version of Autoconf.
+
+Thanks to everybody who's submitted changes and additions to Autoconf!
+I've incorporated many of them, and am still considering others for
+future releases -- but I didn't want to postpone this release indefinitely.
+
+Caution: don't indiscriminately rebuild configure scripts with
+Autoconf version 2. Some configure.in files need minor adjustments to
+work with it; the documentation has a chapter on upgrading. A few
+configure.in files, including those for GNU Emacs and the GNU C
+Library, need major changes because they relied on undocumented
+internals of version 1. Future releases of those packages will have
+updated configure.in files.
+
+It's best to use GNU M4 1.3 (or later) with Autoconf version 2.
+Autoconf now makes heavy use of M4 diversions, which were implemented
+inefficiently in GNU M4 releases before 1.3.
+
+Major changes in Autoconf 2.0:
+
+ Released October 26th, 1994, by David J. MacKenzie
+
+** New copyright terms:
+* There are no restrictions on distribution or use of configure scripts.
+
+** Documentation:
+* Autoconf manual is reorganized to make information easier to find
+ and has several new indexes.
+* INSTALL is reorganized and clearer and is now made from Texinfo source.
+
+** New utilities:
+* autoscan to generate a preliminary configure.in for a package by
+ scanning its source code for commonly used nonportable functions,
+ programs, and header files.
+* ifnames to list the symbols used in #if and #ifdef directives in a
+ source tree.
+* autoupdate to update a configure.in to use the version 2 macro names.
+* autoreconf to recursively remake configure and configuration header
+ files in a source tree.
+
+** Changed utilities:
+* autoheader can take pieces of acconfig.h to replace config.h.{top,bot}.
+* autoconf and autoheader can look for package-local definition files
+ in an alternate directory.
+
+** New macros:
+* AC_CACHE_VAL to share results of tests between configure runs.
+* AC_DEFUN to define macros, automatically AC_PROVIDE them, and ensure
+ that macros invoked with AC_REQUIRE don't interrupt other macros.
+* AC_CONFIG_AUX_DIR, AC_CANONICAL_SYSTEM, AC_CANONICAL_HOST, AC_LINK_FILES to
+ support deciding unguessable features based on the host and target types.
+* AC_CONFIG_SUBDIRS to recursively configure a source tree.
+* AC_ARG_PROGRAM to use the options --program-prefix,
+ --program-suffix, and --program-transform-name to change the names
+ of programs being installed.
+* AC_PREFIX_DEFAULT to change the default installation prefix.
+* AC_TRY_COMPILE to compile a test program without linking it.
+* AC_CHECK_TYPE to check whether sys/types.h or stdlib.h defines a given type.
+* AC_CHECK_LIB to check for a particular function and library.
+* AC_MSG_CHECKING and AC_MSG_RESULT to print test results, on a single line,
+ whether or not the test succeeds. They obsolete AC_CHECKING and AC_VERBOSE.
+* AC_SUBST_FILE to insert one file into another.
+* AC_FUNC_MEMCMP to check whether memcmp is 8-bit clean.
+* AC_FUNC_STRFTIME to find strftime even if it's in -lintl.
+* AC_FUNC_GETMNTENT to find getmntent even if it's in -lsun or -lseq.
+* AC_HEADER_SYS_WAIT to check whether sys/wait.h is POSIX.1 compatible.
+
+** Changed macros:
+* Many macros renamed systematically, but old names are accepted for
+ backward compatibility.
+* AC_OUTPUT adds the "automatically generated" comment to
+ non-Makefiles where it finds @configure_input@ in an input file, to
+ support files with various comment syntaxes.
+* AC_OUTPUT does not replace "prefix" and "exec_prefix" in generated
+ files when they are not enclosed in @ signs.
+* AC_OUTPUT allows the optional environment variable CONFIG_STATUS to
+ override the file name "config.status".
+* AC_OUTPUT takes an optional argument for passing variables from
+ configure to config.status.
+* AC_OUTPUT and AC_CONFIG_HEADERS allow you to override the input-file names.
+* AC_OUTPUT automatically substitutes the values of CFLAGS, CXXFLAGS,
+ CPPFLAGS, and LDFLAGS from the environment.
+* AC_PROG_CC and AC_PROG_CXX now set CFLAGS and CXXFLAGS, respectively.
+* AC_PROG_INSTALL looks for install-sh or install.sh in the directory
+ specified by AC_CONFIG_AUXDIR, or srcdir or srcdir/.. or
+ srcdir/../.. by default.
+* AC_DEFINE, AC_DEFINE_UNQUOTED, and AC_SUBST are more robust and smaller.
+* AC_DEFINE no longer prints anything, because of the new result reporting
+ mechanism (AC_MSG_CHECKING and AC_MSG_RESULT).
+* AC_VERBOSE pays attention to --quiet/--silent, not --verbose.
+* AC_ARG_ENABLE and AC_ARG_WITH support whitespace in the arguments to
+ --enable- and --with- options.
+* AC_CHECK_FUNCS and AC_CHECK_HEADERS take optional shell commands to
+ execute on success or failure.
+* Checking for C functions in C++ works.
+
+** Removed macros:
+* AC_REMOTE_TAPE and AC_RSH removed; too specific to tar and cpio, and
+ better maintained with them.
+* AC_ARG_ARRAY removed because no one was likely using it.
+* AC_HAVE_POUNDBANG replaced with AC_SYS_INTERPRETER, which doesn't
+ take arguments, for consistency with all of the other specific checks.
+
+** New files:
+* Comes with config.sub and config.guess, and uses them optionally.
+* Uses config.cache to cache test results. An alternate cache file
+ can be selected with the --cache-file=FILE option.
+* Uses optional shell scripts $prefix/share/config.site and
+ $prefix/etc/config.site to perform site or system specific initializations.
+* configure saves compiler output to ./config.log for debugging.
+* New files autoconf.m4 and autoheader.m4 load the other Autoconf macros.
+* acsite.m4 is the new name for the system-wide aclocal.m4.
+* Has a DejaGnu test suite.
+
+Major changes in Autoconf 1.11:
+
+* AC_PROG_INSTALL calls install.sh with the -c option.
+* AC_SET_MAKE cleans up after itself.
+* AC_OUTPUT sets prefix and exec_prefix if they weren't set already.
+* AC_OUTPUT prevents shells from looking in PATH for config.status.
+
+Plus a few other bug fixes.
+
+Major changes in Autoconf 1.10:
+
+* autoheader uses config.h.bot if present, analogous to config.h.top.
+* AC_PROG_INSTALL looks for install.sh in srcdir or srcdir/.. and
+ never uses cp.
+* AC_PROG_CXX looks for cxx as a C++ compiler.
+
+Plus several bugs fixed.
+
+Major changes in Autoconf 1.9:
+
+* AC_YYTEXT_POINTER replaces AC_DECLARE_YYTEXT.
+* AC_SIZEOF_TYPE generates the cpp symbol name automatically,
+ and autoheader generates entries for those names automatically.
+* AC_FIND_X gets the result from xmkmf correctly.
+* AC_FIND_X assumes no X if --without-x was given.
+* AC_FIND_XTRA adds libraries to the variable X_EXTRA_LIBS.
+* AC_PROG_INSTALL finds OSF/1 installbsd.
+
+Major changes in Autoconf 1.8:
+
+** New macros:
+* New macros AC_LANG_C, AC_LANG_CPLUSPLUS, AC_LANG_SAVE, AC_LANG_RESTORE,
+ AC_PROG_CXX, AC_PROG_CXXCPP, AC_REQUIRE_CPP
+ for checking both C++ and C features in one configure script.
+* New macros AC_CHECKING, AC_VERBOSE, AC_WARN, AC_ERROR for printing messages.
+* New macros AC_FIND_XTRA, AC_MMAP, AC_SIZEOF_TYPE, AC_PREREQ,
+ AC_SET_MAKE, AC_ENABLE.
+
+** Changed macros:
+* AC_FIND_X looks for X in more places.
+* AC_PROG_INSTALL defaults to install.sh instead of cp, if it's in srcdir.
+ install.sh is distributed with Autoconf.
+* AC_DECLARE_YYTEXT has been removed because it can't work, pending
+ a rewrite of quoting in AC_DEFINE.
+* AC_OUTPUT adds its comments in C format when substituting in C files.
+* AC_COMPILE_CHECK protects its ECHO-TEXT argument with double quotes.
+
+** New or changed command line options:
+* configure accepts --enable-FEATURE[=ARG] and --disable-FEATURE options.
+* configure accepts --without-PACKAGE, which sets withval=no.
+* configure accepts --x-includes=DIR and --x-libraries=DIR.
+* Giving --with-PACKAGE no argument sets withval=yes instead of withval=1.
+* configure accepts --help, --version, --silent/--quiet, --no-create options.
+* configure accepts and ignores most other Cygnus configure options, and
+ warns about unknown options.
+* config.status accepts --help, --version options.
+
+** File names and other changes:
+* Relative srcdir values are not made absolute.
+* The values of @prefix@ and @exec_prefix@ and @top_srcdir@ get substituted.
+* Autoconf library files are installed in ${datadir}/autoconf, not ${datadir}.
+* autoheader optionally copies config.h.top to the beginning of config.h.in.
+* The example Makefile dependencies for configure et al. work better.
+* Namespace cleanup: all shell variables used internally by Autoconf
+ have names beginning with `ac_'.
+
+More big improvements are in process for future releases, but have not
+yet been (variously) finished, integrated, tested, or documented enough
+to release yet.
+
+Major changes in Autoconf 1.7:
+
+* New macro AC_OBSOLETE.
+* Bugs in Makefile.in fixed.
+* AC_LONG_FILE_NAMES improved.
+
+Major changes in Autoconf 1.6:
+
+* New macro AC_LONG_64_BITS.
+* Multiple .h files can be created.
+* AC_FIND_X looks for X files directly if it doesn't find xmkmf.
+* AC_ALLOCA defines C_ALLOCA if using alloca.c.
+* --with-NAME can take a value, e.g., --with-targets=sun4,hp300bsd.
+* Unused --no-create option to configure removed.
+* autoheader doesn't change the timestamp of its output file if
+ the file didn't change.
+* All macros that look for libraries now use AC_HAVE_LIBRARY.
+* config.status checks three optional environment variables to
+ modify its behavior.
+* The usual bug fixes.
+
+Major changes in Autoconf 1.5:
+
+* New macros AC_FIND_X, AC_OFF_T, AC_STAT_MACROS_BROKEN, AC_REVISION.
+* autoconf and autoheader scripts have GNU standards conforming
+ --version and --help options (they print their message and exit).
+* Many bug fixes.
+
+Major changes in Autoconf 1.4:
+
+* New macros AC_HAVE_POUNDBANG, AC_TIME_WITH_SYS_TIME, AC_LONG_DOUBLE,
+ AC_GETGROUPS_T, AC_DEFINE_UNQUOTED.
+* autoconf and autoheader use the M4 environment variable to determine the
+ name of the M4 program to use.
+* The --macrodir option to autoconf and autoheader specifies the directory
+ in which acspecific.m4, acgeneral.m4, etc. reside if not the default.
+* autoconf and autoheader can take `-' as their file names, which means to
+ read stdin as input.
+* Resulting configure scripts can take a --verbose option which causes them
+ to print the results of their tests.
+* AC_DEFINE quotes its second argument in such a way that spaces, magic
+ shell characters, etc. will be preserved during various stages of
+ expansion done by the shell. If you don't want this, use
+ AC_DEFINE_UNQUOTED instead.
+* Much textual processing done with external calls to tr and sed have been
+ internalized with builtin M4 `patsubst' and `translit' calls.
+* AC_OUTPUT doesn't hardwire the file names it outputs. Instead, you can
+ set the shell variables `gen_files' and `gen_config' to the list of
+ file names to output.
+* AC_DECLARE_YYTEXT does an AC_SUBST of `LEX_OUTPUT_ROOT', which may be
+ "lex.yy" or "lexyy", depending on the system.
+* AC_PROGRAMS_CHECK takes an optional third arg. If given, it is used as
+ the default value.
+* If AC_ALLOCA chooses alloca.c, it also defines STACK_DIRECTION.
+* AC_CONST works much more reliably on more systems.
+* Many bug fixes.
+
+Major changes in Autoconf 1.3:
+
+configure no longer requires awk for packages that use a config.h.
+Support handling --with-PACKAGE options.
+New `autoheader' script to create `config.h.in' from `configure.in'.
+Ignore troublesome -lucb and -lPW when searching for alloca.
+Rename --exec_prefix to --exec-prefix for GNU standards conformance.
+Improve detection of STDC library.
+Add AC_HAVE_LIBRARY to check for non-default libraries.
+Function checking should work with future GNU libc releases.
+
+Major changes in Autoconf 1.2:
+
+The --srcdir option is now usually unnecessary.
+Add a file containing sample comments describing CPP macros.
+A comment in config.status tells which host it was configured on.
+Substituted variable values can now contain commas.
+Fix bugs in various feature checks.
+
+Major changes in Autoconf 1.1:
+
+Added AC_STRCOLL macro.
+Made AC_GETLOADAVG check for more things.
+AC_OUTPUT argument is now optional.
+Various bug fixes.
+
+-----
+
+Copyright (C) 1993-1996, 1998-2017, 2020-2021 Free Software Foundation,
+Inc.
+
+Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved. This file is offered as-is,
+without warranty of any kind.
+
+Local Variables:
+mode: outline
+End:
diff --git a/openocd-win/openocd/distro-info/licenses/autoconf-2.71/README b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/README
new file mode 100644
index 0000000..fd16df7
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/README
@@ -0,0 +1,66 @@
+-*- text -*-
+
+Autoconf
+
+Autoconf is an extensible package of M4 macros that produce shell
+scripts to automatically configure software source code packages.
+These scripts can adapt the packages to many kinds of UNIX-like
+systems without manual user intervention. Autoconf creates a
+configuration script for a package from a template file that lists the
+operating system features that the package can use, in the form of M4
+macro calls.
+
+Producing configuration scripts using Autoconf requires GNU M4 and
+Perl. You should install GNU M4 (version 1.4.6 or later is required;
+1.4.14 or later is recommended) and Perl (5.006 or later) before
+configuring Autoconf, so that Autoconf's configure script can find
+them. The configuration scripts produced by Autoconf are
+self-contained, so their users do not need to have Autoconf (or GNU
+M4, Perl, etc.).
+
+You can get GNU M4 here:
+
+https://ftp.gnu.org/gnu/m4/
+
+The file INSTALL should be distributed with packages that use
+Autoconf-generated configure scripts and Makefiles that conform to the
+GNU coding standards. The package's README can just give an overview
+of the package, where to report bugs, and a pointer to INSTALL for
+instructions on compilation and installation. This removes the need
+to maintain many similar sets of installation instructions.
+
+Be sure to read BUGS and INSTALL.
+
+Mail suggestions to autoconf@gnu.org, report bugs to
+bug-autoconf@gnu.org, and submit patches to autoconf-patches@gnu.org.
+All changes can be tracked at the read-only autoconf-commit@gnu.org.
+Always include the Autoconf version number, which you can get by
+running `autoconf --version'. Archives of bug-autoconf@gnu.org can be
+found in , and
+similarly for the other mailing lists.
+
+Licensing
+
+Autoconf is released under the General Public License version 3 (GPLv3+).
+Additionally, Autoconf includes a licensing exception in some of its
+source files; see the respective copyright notices for how your
+project is impacted by including scripts generated by Autoconf, and the
+COPYING.EXCEPTION file for the exception in terms of the Additional
+Permissions as described in section 7 of GPLv3.
+
+For more licensing information, see
+ and
+.
+
+For any copyright year range specified as YYYY-ZZZZ in this package
+note that the range specifies every single year in that closed interval.
+
+-----
+
+Copyright (C) 1992-1994, 1998, 2000-2017, 2020-2021 Free Software
+Foundation, Inc.
+
+Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved. This file is offered as-is,
+without warranty of any kind.
diff --git a/openocd-win/openocd/distro-info/licenses/autoconf-2.71/THANKS b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/THANKS
new file mode 100644
index 0000000..a329031
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/autoconf-2.71/THANKS
@@ -0,0 +1,469 @@
+GNU Autoconf THANKS file
+
+GNU Autoconf was originally written by David J. MacKenzie. It would
+not be what it is today without the invaluable help of these people,
+who have reported problems, suggested improvements, or submitted
+actual code. Please help us keep this list complete and free from
+errors. Also see the AUTHORS file for the list of people with
+contributions significant enough to warrant copyright assignment.
+
+Aaron Crane aaronc@pobox.com
+Aaron M. Ucko amu@alum.mit.edu
+Aaron W. LaFramboise aaronenvelope277@aaronwl.com
+Adam J. Richter adam@yggdrasil.com
+Adrian Bunk bunk@stusta.de
+Aharon Robbins arnold@gnu.org
+Akim Demaille akim@freefriends.org
+Akinori Musha knu@iDaemons.org
+Alain Knaff Alain.Knaff@imag.fr
+Albert Chin-A-Young china@thewrittenword.com
+Alec Wolman wolman@cs.washington.edu
+Alex Unleashed unledev@gmail.com
+Alexander Kurz alexander.kurz@qsc.de
+Alexander Mai ?
+Alexander Pletzer pletzer@txcorp.com
+Alexandre Duret-Lutz duret_g@epita.fr
+Alexandre Julliard ?
+Alexandre Oliva oliva@lsd.ic.unicamp.br
+Alfred G. de Wijn dwijn@iluvatar.eu.org
+Alfred M. Szmidt ams@gnu.org
+Allan Caffee allan.caffee@gmail.com
+Allan Clark allanc@chickenandporn.com
+Anaïs Bouque anais.bouque@fr.thalesgroup.com
+Anders Kaseorg andersk@MIT.EDU
+Andreas Buening andreas.buening@nexgo.de
+Andreas Jaeger aj@suse.de
+Andreas Schott schott@rzg.mpg.de
+Andreas Schwab schwab@linux-m68k.org
+Andreas Waechter andreasw@watson.ibm.com
+Andrej Borsenkow borsenkow.msk@sni.de
+Andrew Belov ?
+Andrew Church achurch@achurch.org
+Andrey Simonenko simon@comsys.ntu-kpi.kiev.ua
+Andris Pavenis andris.pavenis@iki.fi
+Anthony N. Frasso afrasso@yahoo.com
+Arkadiusz Miskiewicz arekm@maven.pl
+Art Haas ahaas@neosoft.com
+Arto C. Nirkko ?
+Artur Frysiak wiget@pld.org.pl
+Assar Westerlund assar@sics.se
+Axel Thimm Axel.Thimm@physik.fu-berlin.de
+Bart Oldeman bartoldeman@users.sourceforge.net
+Ben Elliston bje@redhat.com
+Ben Pfaff pfaffben@debian.org
+Benoit Sigoure tsunanet@gmail.com
+Bill Moseley moseley@hank.org
+Bill Northcott w.northcott@unsw.edu.au
+Bill Sommerfeld sommerfeld@apollo.hp.com
+BJ Terry bjterry@gmail.com
+Bob Friesenhahn bfriesen@simple.dallas.tx.us
+Bob Proulx bob@proulx.com
+Bob Rossi bob_rossi@cox.net
+Bob Wilson bwilson@tensilica.com
+Brad Walker me@bradmwalker.com
+Braden McDaniel braden@endoframe.com
+Bram Moolenaar bram@vim.org
+Brian Gough bjg@network-theory.co.uk
+Brian J. Murrell brian@sun.com
+Bruce Dugan bld0401@gmail.com
+Bruce Korb bkorb@gnu.org
+Bruce Lilly ?
+Bruno Haible haible@ilog.fr
+Björn Lindqvist bjourne@gmail.com
+Carl Edman cedman@princeton.edu
+Carlos Velasco carlosev@newipnet.com
+Chad R. Larson chad@anasazi.com
+Charles 'Buck' Krasic krasic@cs.ubc.ca
+Chikama Masaki masaki.chikama@gmail.com
+Chris P. Ross cross@uu.net
+Chris Pickett chris.pickett@mail.mcgill.ca
+Chris Provenzano proven@cygnus.com
+Chris Torek torek@bsdi.com
+Christian Cornelssen ccorn@cs.tu-berlin.de
+Christian Krackowizer ckrackowiz@std.schuler-ag.com
+Christian Krone krischan@sql.de
+Christian Rössel christian.roessel@gmx.de
+Christophe Jarry christophe.jarry@ouvaton.org
+Christopher Hulbert cchgroupmail@gmail.com
+Christopher Lee chrislee@ri.cmu.edu
+Clinton Roy clinton.roy@gmail.com
+Colin Watson cjwatson@debian.org
+Corinna Vinschen corinna-cygwin@cygwin.com
+Cort Dougan cort@cs.nmt.edu
+D'Arcy A MacIsaac ?
+Dalibor Topic robilad@kaffe.org
+Dan Manthey dan_manthey@partech.com
+Daniel Carroll dan@mesastate.edu
+Daniel Jacobowitz drow@mvista.com
+Daniel Reed ?
+Daniele Arena daniele@ripe.net
+Dave Adams adams@hpesdwa.fc.hp.com
+Dave Erickson retrorandomaccess@hotmail.com
+Dave Korn dave.korn.cygwin@googlemail.com
+Dave Love fx@gnu.org
+David Byron dbyron@hheld.com
+David Carter david@carter.net
+David Cournapeau david@ar.media.kyoto-u.ac.jp
+David Fang fang@csl.cornell.edu
+David Hill dhill@mindcry.org
+David J. MacKenzie djm@uunet.uu.net
+David M. Lloyd dmlloyd@tds.net
+David Morgan dmorgan@symark.com
+Davie Reiss dreiss@facebook.com
+David Relson relson@osagesoftware.com
+Dennis J. Linse ?
+Derek R. Price derek.price@openavenue.com
+Didier Desseaux didess@infonie.fr
+Didier Verna didier@xemacs.org
+Dieter Jurzitza dieter.jurzitza@t-online.de
+Dietmar P. Schindler schd@mra.man.de
+Dmitry Grebeniuk gdsfh1@gmail.com
+Doug Evans dje@canuck.cygnus.com
+Dries Kimpe ?
+Dustin J. Mitchell dustin@zmanda.com
+Edouard Bechetoille ebecheto@ens-lyon.fr
+Elbert Pol elbert.pol@gmail.com
+Eli Zaretskii eliz@gnu.org
+Elias Pipping pipping@macports.org
+Enrique Robledo Arnuncio enrique.robledo@wanadoo.es
+Erez Zadok ezk@cs.columbia.edu
+Eric Backus ericb@lsid.hp.com
+Eric Blake ebb9@byu.net
+Eric Lemings lemings@roguewave.com
+Eric Mumpower nocturne@mit.edu
+Eric Paire ?
+Eric Sunshine sunshine@sunshineco.com
+Ezra Peisach epeisach@zif.mit.edu
+Fedor Sergeev ?
+Felix Lee flee@cygnus.com
+Fernando Carrijo fcarrijo@freedesktop.org
+Franceseco Romani fromani@gmail.com
+Frank Denis j@jedi.claranet.fr
+François Pinard pinard@iro.umontreal.ca
+Fred Kreek Fred.Kreek@kadaster.nl
+Frederik Fouvry fouvry@CoLi.Uni-SB.DE
+Gareth McCaughan gareth.mccaughan@pobox.com
+Gary V. Vaughan gvaughan@oranda.demon.co.uk
+Geir Ove Myhr myhr@stud.fim.ntnu.no
+Gerrit P. Haase gp@familiehaase.de
+Gideon Go gideon.go@gmail.com
+Giorgos Keramidas gkeramidas@gmail.com
+Giuseppe Guerrini guisguerrini@racine.ra.it
+Glenn P. Davis davis@unidata.ucar.edu
+Godmar Back gback@cs.utah.edu
+Gordon Matzigkeit gord@trick.fig.org
+Graham Jenkins c714553@vus415.telstra.com.au
+Greg A. Woods woods@weird.com
+Greg Schafer gschafer@zip.com.au
+Gregorio Guidi ?
+Gregory Giannoni sand@narguile.org
+Giulio Paci giuliopaci@interfree.it
+Guido Draheim Guido.Draheim@gmx.de
+Guido Flohr gufl0000@stud.uni-sb.de
+Guido van Rossum ?
+Guillermo Gomez gomez@mi.uni-erlangen.de
+H. Merijn Brand h.m.brand@hccnet.nl
+H. Peter Anvin ?
+H.J. Lu hjl@gnu.org
+Hallvard B Furuseth h.b.furuseth@usit.uio.no
+Hans Aberg haberg@math.su.se
+Hans Olsson Hans.Olsson@dna.lth.se
+Hans Ulrich Niedermann hun@n-dimensional.de
+Harlan Stenn stenn@whimsy.udel.edu
+Heiko Schlichting inn-workers@fu-berlin.de
+Henk Krus h.krus@cyclone.nl
+Howard Chu hyc@highlandsun.com
+Ian Lance Taylor ian@cygnus.com
+Ian Macdonald iamacdo@telkomsa.net
+Ian Redfern Ian.Redfern@logicacmg.com
+Ilya Bobir ilya.bobir@gmail.com
+Ilya Zakharevich ilya@Math.Berkeley.EDU
+Ineiev ineiev@yahoo.co.uk
+Iohannes m zmoelnig zmoelnig@iem.at
+J C Fitzgerald v7022@wave.co.nz
+Jaap Haitsma jaap@haitsma.org
+James A. Lupo lupoja@feynman.ml.wpafb.af.mil
+Jan Madzik jmadzik@gmail.com
+Jason Molenda jsm@cygnus.com
+Jeff Garzik jgarzik@pobox.com
+Jeff Painter ?
+Jeff Squyres jsquyres@cisco.com
+Jeffrey A Law law@cygnus.com
+Jeffrey J. Barteet ?
+Jennis Pruett ?
+Jens Petersen petersen@redhat.com
+Jens Schmidt jens.schmidt35@arcor.de
+Jeremy Yallop jeremy@yallop.org
+Jerker Bäck jerker.back@home.se
+Jim Blandy jimb@wookumz.gnu.ai.mit.edu
+Jim Meyering meyering@ascend.com
+Jim Warhol jrw@jwarhol.com
+Jiro Takabatake jiro@din.or.jp
+Jochen Friedrich jochen@scram.de
+Joel E. Denny jdenny@ces.clemson.edu
+Joel James Adamson joel@chondestes.bio.unc.edu
+Joey Mingrone joey@mingrone.org
+Johan Danielsson joda@pdc.kth.se
+John Calcote john.calcote@gmail.com
+John David Anglin dave@hiauly1.hia.nrc.ca
+John Fortin fortinj@attglobal.net
+John Interrante interran@uluru.stanford.edu
+John R. Cary cary@txcorp.com
+John W. Eaton jwe@bevo.che.wisc.edu
+Jonathan Kamens jik@kamens.brookline.ma.us
+Jonathan Lebon jlebon@redhat.com
+Josef Tran josef@timetrackertechnology.com
+Josef Vukovic josefvukovic@googlemail.com
+Joseph S. Myers jsm28@cam.ac.uk
+Joshua G. Hale jgh.emc@gmail.com
+Juan Carlos Hurtado adso.lists@gmail.com
+Jules Colding colding@42tools.com
+Julian C. Cummings cummings@cacr.caltech.edu
+Julian Onions j.onions@nexor.co.uk
+Julien Danjou acid@debian.org
+Julien Élie julien@trigofacile.com
+Julio Garvia ?
+Justace Clutter ?
+Jörn Rennecke amylaar@cygnus.co.uk
+Karl Berry karl@cs.umb.edu
+Karl Heuer kwzh@gnu.org
+Karsten Hopp karsten@redhat.com
+Kate Hedstrom ?
+Kathryn Hargreaves kathryn@deas.harvard.edu
+Kaveh R. Ghazi ghazi@caip.rutgers.edu
+Keith Bostic bostic@abyssinian.sleepycat.com
+Keith Marshall keith.marshall@total.com
+Kelly Anderson tgcorp@attglobal.net
+Ken Pizzini ken@halcyon.com
+Ken Raeburn raeburn@cygnus.com
+Kevin Ryde user42@zip.com.au
+Klee Dienes kdienes@apple.com
+Koji Arai JCA02266@nifty.ne.jp
+Kristian Kvilekval kris@cs.ucsb.edu
+Křištof Želechovski giecrilj@stegny.2a.pl
+Kurt D. Zeilenga kurt@openldap.org
+Larry Jones larry.jones@sdrc.com
+Larry Schmitt larry@mail.haleakalawebdesigns.com
+Larry Schwimmer rosebud@cyclone.stanford.edu
+Lars Hecking lhecking@nmrc.ucc.ie
+Lars J. Aas larsa@sim.no
+Laurence Darbe ldarby@tuffmail.com
+Leo Moisio leo.moisio@gmail.com
+Loulou Pouchet loulou@lrde.epita.fr
+Luc Maisonobe luc@spaceroots.org
+Ludovic Courtes ?
+Luke Dalessandro luked@cs.rochester.edu
+Magnus Therning therning@gforge.natlab.research.philips.com
+Manu manubee@wanadoo.fr
+Marc Espie Marc.Espie@liafa.jussieu.fr
+Marcus Brinkmann ?
+Marcus Daniels marcus@sysc.pdx.edu
+Marcus Thiessel marcus@xemacs.org
+Mark Cave-Ayland ?
+Mark D. Baushke ?
+Mark D. Roth ?
+Mark Elbrecht snowball3@usa.net
+Mark Hessling mark@rexx.org
+Mark Kettenis kettenis@gnu.org
+Markku Savela msa@msa.tte.vtt.fi
+Markus Oberhumer markus.oberhumer@jk.uni-linz.ac.at
+Markus Geimer m.geimer@fz-juelich.de
+Martin Buchholz martin@xemacs.org
+Martin Costabel costabel@wanadoo.fr
+Martin Frydl martin@systinet.com
+Martin Koeppe mkoeppe@gmx.de
+Martin Mokrejs mmokrejs@natur.cuni.cz
+Martin Wilck martin@tropos.de
+Martyn Johnson Martyn.Johnson@cl.cam.ac.uk
+Matěj Týč matej.tyc@gmail.com
+Matt Kraai kraai@ftbfs.org
+Matteo Frigo ?
+Matthew D. Langston langston@SLAC.Stanford.EDU
+Matthew Mueller donut@azstarnet.com
+Matthew Woehlke mw_triad@users.sourceforge.net
+Matthias Andree matthias.andree@gmx.de
+Michal Čihař nijel@debian.org
+Michael Elizabeth Chastain chastain@cygnus.com
+Michael Jenning ?
+Michael Matz matz@kde.org
+Michael Schoene mrs@mlc.de
+Michael Wardle ?
+Mike Frysinger vapier@gentoo.org
+Mike Hopkirk hops@sco.com
+Mike Stump mrs@wrs.com
+Mikulas Patocka ?
+Miles Bader miles@gnu.ai.mit.edu
+Mo DeJong mdejong@cygnus.com
+Momchil Velkov velco@fadata.bg
+Monty Taylor mordred@inaugust.com
+Morten Eriksen mortene@sim.no
+Mostafa mostafa_working_away@yahoo.com
+Motoyuki Kasahara m-kasahr@sra.co.jp
+Nathan Schulte reklipz@gmail.com
+Nathanael Nerode neroden@gcc.gnu.org
+Nelson H. F. Beebe beebe@math.utah.edu
+Nicolas Joly njoly@pasteur.fr
+Nicolás Lichtmaier jnl@synapsis-sa.com.ar
+Nick Bowler nbowler@draconx.ca
+NightStrike nightstrike@gmail.com
+Nishio Futoshi fut_nis@d3.dion.ne.jp
+Noah Elliott elliott@hera.llnl.gov
+Noah Friedman friedman@gnu.ai.mit.edu
+Noah Misch noah@cs.caltech.edu
+Noel Grandin noel@peralex.com
+Norman Gray ?
+Olaf Lenz olenz@fias.uni-frankfurt.de
+Ole Holm Nielsen Ole.H.Nielsen@fysik.dtu.dk
+Oliver Kiddle opk@zsh.org
+Olly Betts olly@survex.com
+Ossama Othman ossama@debian.org
+Pallav Gupta pallavgupta@gmail.com
+Paolo Bonzini bonzini@gnu.org
+Patrice Dumas pertusus@free.fr
+Patrick Tullmann tullmann@cs.utah.edu
+Patrick Welche prlw1@newn.cam.ac.uk
+Paul Berrevoets paul@swi.com
+Paul D. Smith psmith@gnu.org
+Paul Eggert eggert@cs.ucla.edu
+Paul Gampe paulg@apnic.net
+Paul Jarc prj@po.cwru.edu
+Paul Martinolich martinol@datasync.com
+Paul Pogonyshev ?
+Paul Townsend ?
+Pavel Roskin pavel_roskin@geocities.com
+Pádraig Brady P@draigbrady.com
+Per Øyvind Karlsen peroyvind@mandriva.org
+Peter Breitenlohner peb@mppmu.mpg.de
+Peter Eisentraut peter_e@gmx.net
+Peter Hendrickson pdh@wiredyne.com
+Peter Johansson trojkan@gmail.com
+Peter O'Gorman peter@pogma.com
+Peter Palfrader weasel@debian.org
+Peter Simons simons@cryp.to
+Peter Stephenson pws@csr.com
+Philipp Thomas kthomas@gwdg.de
+Philippe De Muyter ?
+Pierre pierre42d@9online.fr
+Pierre Ynard linkfanel@yahoo.fr
+Pontus Skoeld pont@soua.net
+Rainer Orth ro@TechFak.Uni-Bielefeld.DE
+Raja R Harinath harinath@cs.umn.edu
+Ralf Corsepius corsepiu@faw.uni-ulm.de
+Ralf Menzel menzel@ls6.cs.uni-dortmund.de
+Ralf S. Engelschall rse@engelschall.com
+Ralf Wildenhues Ralf.Wildenhues@gmx.de
+Randall Cotton recotton@earthlink.net
+Reuben Thomas rrt@sc3d.org
+Richard Dawe rich@phekda.freeserve.co.uk
+Richard Stallman rms@gnu.org
+Robert Lipe robertlipe@usa.net
+Robert S. Maier rsm@math.arizona.edu
+Roberto Bagnara bagnara@cs.unipr.it
+Rochan rochan@ices.utexas.edu
+Roger Leigh rleigh@whinlatter.ukfsn.org
+Roland McGrath roland@gnu.org
+Rolf Ebert rolf.ebert.gcc@gmx.de
+Rolf Vandevaart Rolf.Vandevaart@sun.com
+Romain Lenglet romain.lenglet@laposte.net
+Ruediger Kuhlmann info@ruediger-kuhlmann.de
+Rugxulo rugxulo@gmail.com
+Ruslan Babayev ruslan@babayev.com
+Russ Allbery rra@stanford.edu
+Russ Boylan ross@biostat.ucsf.edu
+Ryuji Abe raeva@t3.rim.or.jp
+Sam Sexton Sam.Sexton@reuters.com
+Sam Sirlin sam@kalessin.jpl.nasa.gov
+Sam Steingold sds@gnu.org
+Sam Varshavchik mrsam@courier-mta.com
+Sander Niemeijer niemeijer@science-and-technology.nl
+santilín listas@gestiong.org
+Scott Bambrough scottb@corelcomputer.com
+Scott McCreary scottmc2@gmail.com
+Scott Stanton stanton@scriptics.com
+Sebastian Freundt hroptatyr@gna.org
+Sergey Poznyakoff ?
+Simon Josefsson jas@extundo.com
+Simon Leinen simon@lia.di.epfl.ch
+Slava Sysoltsev Viatcheslav.Sysoltsev@h-d-gmbh.de
+Stefan Seefeld stefan@codesourcery.com
+Stefan `Sec' Zehl ?
+Stefano Lattarini stefano.lattarini@gmail.com
+Stepan Kasal kasal@ucw.cz
+Stéphane Chazelas Stephane_Chazelas@yahoo.fr
+Stephen Gildea filtered@against.spam
+Stephen Rasku srasku@mail.tantalus-systems.com
+Stephen P. Schaefer sschaefer@acm.org
+Steve Chamberlain sac@cygnus.com
+Steve Goetze goetze@dovetail.com
+Steve Huston shuston@riverace.com
+Steve Robbins steve@nyongwa.montreal.qc.ca
+Steven G. Johnson stevenj@alum.mit.edu
+Steven R. Loomis srl@icu-project.org
+Stu Grossman grossman@cygnus.com
+Sumit Pandya sumit@elitecore.com
+Syd Polk spolk@cygnus.com
+T.E. Dickey dickey@clark.net
+Ted Bullock tbullock@canada.com
+Theodore Ts'o tytso@mit.edu
+Thien-Thi Nguyen ttn@gnu.org
+Thomas Jahns jahns@dkrz.de
+Thomas Winder tom@vlsivie.tuwien.ac.at
+Tim Freeman tim@fungible.com
+Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu
+Tim Rice tim@multitalents.net
+Tim Van Holder tim.van.holder@pandora.be
+Tobias Burnus burnus@net-b.de
+Tom Browder tom.browder@gmail.com
+Tom Epperly tepperly@llnl.gov
+Tom Lane tgl@sss.pgh.pa.us
+Tom Purcell Tom.Purcell@wang.com
+Tom Tromey tromey@cygnus.com
+Tom Yu tlyu@mit.edu
+Tomohiro Suzuki ?
+Tony Leneis tony@plaza.ds.adp.com
+Toshio Kuratomi ?
+Uwe Seimet us@orbacus.com
+Václav Haisman v.haisman@sh.cvut.cz
+Vance Shipley vances@motivity.ca
+Viktor Dukhovni viktor@anaheim.esm.com
+Ville Karaila karaila@iki.fi
+Vincent Lefèvre vincent@vinc17.org
+Vincent Torri vtorri at univ-evry.fr
+Vladimir Volovich vvv@vsu.ru
+Volker Borchert bt@teknon.de
+Wayne Chapeskie waynec@spinnaker.com
+Werner Lemberg wl@gnu.org
+Wilfredo Sanchez wsanchez@apple.com
+William Pursell bill.pursell@gmail.com
+Wiseman Jun junwiseman@gmail.com
+Wolfgang Mueller Wolfgang.Mueller@cui.unige.ch
+Yaakov Selkowitz yselkowitz@users.sourceforge.net
+Yavor Doganov yavor@gnu.org
+Yury Puhalsky pooh@cryptopro.ru
+Zack Weinberg zack@codesourcery.com
+? Seanster@Seanster.com
+
+Many people are not named here because we lost track of them. We
+thank them! Please, help us keep this list up to date.
+
+================
+
+Local Variables:
+mode: text
+coding: utf-8
+End:
+
+Copyright (C) 1999-2017, 2020-2021 Free Software Foundation, Inc.
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see .
diff --git a/openocd-win/openocd/distro-info/licenses/automake-1.16.5/AUTHORS b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/AUTHORS
new file mode 100644
index 0000000..a3c5c01
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/AUTHORS
@@ -0,0 +1,27 @@
+Authors of GNU Automake.
+
+David Mackenzie
+ First version of most ".am" files.
+ Wrote sh version of automake.in.
+
+Tom Tromey
+ Touched all ".am" files.
+ Rewrote automake.in
+
+Alexandre Oliva
+ Some of the user-side dependency tracking system.
+ Some more random hacking.
+
+Alexandre Duret-Lutz
+ Major overhaul of everything.
+ Maintenance since 2002.
+
+Ralf Wildenhues
+ Random breakage.
+ Maintenance since 2006.
+
+Stefano Lattarini
+ Testsuite overhaul.
+ TAP support and custom testsuite drivers.
+ Random breakage.
+ De-facto maintenance since 2012.
diff --git a/openocd-win/openocd/distro-info/licenses/automake-1.16.5/COPYING b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/COPYING
new file mode 100644
index 0000000..d511905
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/COPYING
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
diff --git a/openocd-win/openocd/distro-info/licenses/automake-1.16.5/NEWS b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/NEWS
new file mode 100644
index 0000000..fb05ee2
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/NEWS
@@ -0,0 +1,3118 @@
+For planned incompatibilities in a future Automake 2.0 release,
+please see NEWS-2.0 and start following the advice there now.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.16.5:
+
+* Bugs fixed
+
+ - PYTHON_PREFIX and PYTHON_EXEC_PREFIX are now set according to
+ Python's sys.* values only if the new configure option
+ --with-python-sys-prefix is specified. Otherwise, GNU default values
+ are used, as in the past. (The change in 1.16.3 was too incompatible.)
+
+ - consistently depend on install-libLTLIBRARIES.
+
+* Distribution
+
+ - use const for yyerror declaration in bison/yacc tests.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.16.4:
+
+* New features added
+
+ - The PYTHON_PREFIX and PYTHON_EXEC_PREFIX variables are now set from
+ Python's sys.prefix and sys.exec_prefix; use the new configure options
+ --with-python_prefix and --with-python_exec_prefix to specify explicitly.
+
+ - Common top-level files can be provided as .md; the non-md version is
+ used if both are present:
+ AUTHORS ChangeLog INSTALL NEWS README README-alpha THANKS
+
+ - CTAGS, ETAGS, SCOPE variables can be set via configure.
+
+ - Silent make output for custom link commands.
+
+ - New option "no-dist-built-sources" skips generating $(BUILT_SOURCES)
+ before building the tarball as part of "make dist", that is,
+ omits the dependency of $(distdir): $(BUILT_SOURCES).
+
+* Bugs fixed
+
+ - automake output more reproducible.
+
+ - test-driver less likely to clash with tests writing to the same file.
+
+ - DejaGnu tests always use the directory name, testsuite/, for
+ compatibility with the newer dejagnu-1.6.3 and with prior versions.
+
+* Distribution
+
+ - config.sub and config.guess updates include restoration of `...`
+ for maximum portability.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.16.3:
+
+* New features added
+
+ - In the testsuite summary, the "for $(PACKAGE_STRING)" suffix
+ can be overridden with the AM_TESTSUITE_SUMMARY_HEADER variable.
+
+* Bugs fixed
+
+ - Python version number 3.10 no longer considered to be 3.1.
+
+ - Broken links in manual fixed or removed, and new script
+ contrib/checklinkx (a small modification of W3C checklink) added,
+ with accompany target checklinkx to recheck urls.
+
+ - install-exec target depends on $(BUILT_SOURCES).
+
+ - valac argument matching more precise, to avoid garbage in DIST_COMMON.
+
+ - Support for Vala in VPATH builds fixed so that both freshly-generated and
+ distributed C files work, and operation is more reliable with or without
+ an installed valac.
+
+ - Dejagnu doesn't break on directories containing spaces.
+
+* Distribution
+
+ - new variable AM_DISTCHECK_DVI_TARGET, to allow overriding the
+ "make dvi" that is done as part of distcheck.
+
+* Miscellaneous changes
+
+ - install-sh tweaks:
+ . new option -p to preserve mtime, i.e., invoke cp -p.
+ . new option -S SUFFIX to attempt backup files using SUFFIX.
+ . no longer unconditionally uses -f when rm is overridden by RMPROG.
+ . does not chown existing directories.
+
+ - Removed function up_to_date_p in lib/Automake/FileUtils.pm.
+ We believe this function is completely unused.
+
+ - Support for in-tree Vala libraries improved.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.16.2:
+
+* New features added
+
+ - add zstd support and the automake option, dist-zstd.
+
+ - support for Python 3: py-compile now supports both Python 3
+ and Python 2; tests do not require .pyo files, and uninstall
+ deletes __pycache__ correctly (automake bug #32088).
+
+* Miscellaneous changes
+
+ - automake no longer requires a @setfilename in each .texi file
+
+* Bugs fixed
+
+ - When cleaning the compiled python files, '\n' is not used anymore in the
+ substitution text of 'sed' transformations. This is done to preserve
+ compatibility with the 'sed' implementation provided by macOS which
+ considers '\n' as the 'n' character instead of a newline.
+ (automake bug#31222)
+
+ - For make tags, lisp_LISP is followed by the necessary space when
+ used with CONFIG_HEADERS.
+ (automake bug#38139)
+
+ - The automake test txinfo-vtexi4.sh no longer fails when localtime
+ and UTC cross a day boundary.
+
+ - Emacsen older than version 25, which require use of
+ byte-compile-dest-file, are supported again.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.16.1:
+
+* Bugs fixed:
+
+ - 'install-sh' now ensures that nobody can cross privilege boundaries by
+ pre-creating symlink on the directory inside "/tmp".
+
+ - 'automake' does not depend on the 'none' subroutine of the List::Util
+ module anymore to support older Perl version. (automake bug#30631)
+
+ - A regression in AM_PYTHON_PATH causing the rejection of non literal
+ minimum version parameter hasn't been fixed. (automake bug#30616)
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.16:
+
+* Miscellaneous changes
+
+ - When subdir-objects is in effect, Automake will now construct
+ shorter object file names when no programs and libraries name
+ clashes are encountered. This should make the discouraged use of
+ 'foo_SHORTNAME' unnecessary in many cases.
+
+* Bugs fixed:
+
+ - Automatic dependency tracking has been fixed to work also when the
+ 'subdir-object' option is used and some 'foo_SOURCES' definition
+ contains unexpanded references to make variables, as in, e.g.:
+
+ a_src = sources/libs/aaa
+ b_src = sources/bbb
+ foo_SOURCES = $(a_src)/bar.c $(b_src)/baz.c
+
+ With such a setup, the created makefile fragment containing dependency
+ tracking information will be correctly placed under the directories
+ named 'sources/libs/aaa/.deps' and 'sources/bbb/.deps', rather than
+ mistakenly under directories named (literally!) '$(src_a)/.deps' and
+ '$(src_b)/.deps' (this was the first part of automake bug#13928).
+
+ Notice that in order to fix this bug we had to slightly change the
+ semantics of how config.status bootstraps the makefile fragments
+ required for the dependency tracking to work: rather than attempting
+ to parse the Makefiles via grep and sed trickeries only, we actually
+ invoke 'make' on a slightly preprocessed version of those Makefiles,
+ using a private target that is only meant to bootstrap the required
+ makefile fragments.
+
+ - The 'subdir-object' option no longer causes object files corresponding
+ to source files specified with an explicit '$(srcdir)' component to be
+ placed in the source tree rather than in the build tree.
+
+ For example, if Makefile.am contains:
+
+ AUTOMAKE_OPTIONS = subdir-objects
+ foo_SOURCES = $(srcdir)/foo.c $(srcdir)/s/bar.c $(top_srcdir)/baz.c
+
+ then "make all" will create 'foo.o' and 's/bar.o' in $(builddir) rather
+ than in $(srcdir), and will create 'baz.o' in $(top_builddir) rather
+ than in $(top_srcdir).
+
+ This was the second part of automake bug#13928.
+
+ - Installed 'aclocal' m4 macros can now accept installation directories
+ containing '@' characters (automake bug#20903)
+
+ - "./configure && make dist" no longer fails when a distributed file depends
+ on one from BUILT_SOURCES.
+
+ - When combining AC_LIBOBJ or AC_FUNC_ALLOCA with the
+ "--disable-dependency-tracking" configure option in an out of source
+ build, the build sub-directory defined by AC_CONFIG_LIBOBJ_DIR is now
+ properly created. (automake bug#27781)
+
+ - The time printed by 'mdate-sh' is now using the UTC time zone to support
+ the reproducible build effort. (automake bug#20314)
+
+ - The elisp byte-compilation rule now uses byte-compile-dest-file-function,
+ rather than byte-compile-dest-file, which was obsoleted in 2009. We expect
+ that Emacs-26 will continue to support the old function, but will complain
+ loudly, and that Emacs-27 will remove support for it altogether.
+
+* New features added
+
+ - A custom testsuite driver for the Guile Scheme SRFI-64 API has been added
+ to the "contrib" section. This allows a more convenient way to test Guile
+ code without having to use low primitives such as exit status. See
+ SRFI-64 API specification for more details:
+
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.15.1:
+
+* Bugs fixed:
+
+ - The code has been adapted to remove a warning present since Perl
+ 5.22 stating that "Unescaped left brace in regex is deprecated".
+ This warning has become an hard error in Perl 5.26 (bug#22372).
+
+ - The generated Makefiles do not rely on the obsolescent GZIP
+ environment variable which was used for passing arguments to
+ 'gzip'. Compatibility with old versions has been
+ preserved. (bug#20132)
+
+* Miscellaneous changes:
+
+ - Support the Windows version of the Intel C Compiler (icl) in the
+ 'compile' script in the same way the (compatible) Microsoft C
+ Compiler is supported.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.15:
+
+* Improvements and refactorings in the install-sh script:
+
+ - It has been modernized, and now makes the following assumptions
+ *unconditionally*:
+ (1) a working 'dirname' program is available;
+ (2) the ${var:-value} shell parameters substitution works;
+ (3) the "set -f" and "set +f" shell commands work, and, respectively,
+ disable and enable shell globbing.
+
+ - The script implements stricter error checking, and now it complains
+ and bails out if any of the following expectations is not met:
+ (1) the options -d and -t are never used together;
+ (2) the argument passed to option -t is a directory;
+ (3) if there are two or more SOURCEFILE arguments, the
+ DESTINATION argument must be a directory.
+
+* Automake-generated testsuites:
+
+ - The default test-driver used by the Automake-generated testsuites
+ now appends the result and exit status of each "plain" test to the
+ associated log file (automake bug#11814).
+
+ - The perl implementation of the TAP testsuite driver is no longer
+ installed in the Automake's scripts directory, and is instead just
+ distributed as a "contrib" addition. There should be no reason to
+ use this implementation anyway in real packages, since the awk+shell
+ implementation of the TAP driver (which is documented in the manual)
+ is more portable and has feature parity with the perl implementation.
+
+ - The rule generating 'test-suite.log' no longer risk incurring in an
+ extra useless "make all" recursive invocation in some corner cases
+ (automake bug#16302).
+
+* Distribution:
+
+ - Automake bug#18286: "make distcheck" could sometimes fail to detect
+ files missing from the distribution tarball, especially in those cases
+ where both the generated files and their dependencies are explicitly
+ in $(srcdir). An important example of this are *generated* makefile
+ fragments included at Automake time in Makefile.am; e.g.:
+
+ ...
+ $(srcdir)/fragment.am: $(srcdir)/data.txt $(srcdir)/preproc.sh
+ cd $(srcdir) && $(SHELL) preproc.sh fragment.am
+ include $(srcdir)/fragment.am
+ ...
+
+ If the use forgot to add data.txt and/or preproc.sh in the distribution
+ tarball, "make distcheck" would have erroneously succeeded! This issue
+ is now fixed.
+
+ - As a consequence of the previous change, "make distcheck" will run
+ using '$(distdir)/_build/sub' as the build directory, rather than
+ simply '$(distdir)/_build' (as it was the case for Automake 1.14 and
+ earlier). Consequently, the './configure' and 'make' invocations
+ issued by the distcheck recipe now have $(srcdir) equal to '../..',
+ rather than to just '..'. Dependent and similar variables (e.g.,
+ '$(top_srcdir)') are also changed accordingly.
+
+ Thus, Makefiles that made assumptions about the exact values of the
+ build and source directories used by "make distcheck" will have to
+ be adjusted. Notice that making such assumptions was a bad and
+ unsupported practice anyway, since the exact locations of those
+ directories should be considered implementation details, and we
+ reserve the right to change them at any time.
+
+* Miscellaneous bugs fixed:
+
+ - The expansion of AM_INIT_AUTOMAKE ends once again with a trailing
+ newline (bug#16841). Regression introduced in Automake 1.14.
+
+ - We no longer risk to use '$ac_aux_dir' before it's defined (see
+ automake bug#15981). Bug introduced in Automake 1.14.
+
+ - The code used to detect whether the currently used make is GNU make
+ or not (relying on the private macro 'am__is_gnu_make') no longer
+ risks causing "Arg list too long" for projects using automatic
+ dependency tracking and having a ton of source files (bug#18744).
+
+ - Automake tries to offer a more deterministic output for generated
+ Makefiles, in the face of the newly-introduced randomization for
+ hash keys order in Perl 5.18.
+
+ - In older Automake versions, if a user defined one single Makefile
+ fragment (say 'foo.am') to be included via Automake includes in
+ his main Makefile.am, and defined a custom make rule to generate that
+ file from other data, Automake used to spuriously complain with some
+ message like "... overrides Automake target '$(srcdir)/foo.am".
+ This bug is now fixed.
+
+ - The user can now extend the special .PRECIOUS target, the same way
+ he could already do with the .MAKE .and .PHONY targets.
+
+ - Some confusing typos have been fixed in the manual and in few warning
+ messages (automake bug#16827 and bug#16997).
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.14.1:
+
+* Bugs fixed:
+
+ - The user is no longer allowed to override the --srcdir nor the --prefix
+ configure options used by "make distcheck" (bug#14991).
+
+ - Fixed a gross inefficiency in the recipes for installing byte-compiled
+ python files, that was causing an O(N^2) performance on the number N of
+ files, instead of the expected O(N) performance. Note that this bug
+ was only relevant when the number of python files was high (which is
+ unusual in practice).
+
+ - Automake try to offer a more deterministic output for warning messages,
+ in the face of the newly-introduced randomization for hash keys order
+ in Perl 5.18.
+
+ - The 'test-driver' script now actually error out with a clear error
+ message on the most common invalid usages.
+
+ - Several spurious failures/hangs in the testsuite (bugs #14706, #14707,
+ #14760, #14911, #15181, #15237).
+
+* Documentation fixes:
+
+ - Fixed typos in the 'fix-timestamp.sh' example script that made it
+ nonsensical.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.14:
+
+* C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
+
+ - The 'compile' script is now unconditionally required for all packages
+ that perform C compilation (if you are using the '--add-missing'
+ option, automake will fetch that script for you, so you shouldn't
+ need any explicit adjustment). This new behaviour is needed to avoid
+ obscure errors when the 'subdir-objects' option is used, and the
+ compiler is an inferior one that doesn't grasp the combined use of
+ both the "-c -o" options; see discussion about automake bug#13378 for
+ more details:
+
+
+
+ - The next major Automake version (2.0) will unconditionally activate
+ the 'subdir-objects' option. In order to smooth out the transition,
+ we now give a warning (in the category 'unsupported') whenever a
+ source file is present in a subdirectory but the 'subdir-object' is
+ not enabled. For example, the following usage will trigger such a
+ warning:
+
+ bin_PROGRAMS = sub/foo
+ sub_foo_SOURCES = sub/main.c sub/bar.c
+
+ - Automake will automatically enhance the autoconf-provided macro
+ AC_PROG_CC to force it to check, at configure time, that the
+ C compiler supports the combined use of both the '-c' and '-o'
+ options. The result of this check is saved in the cache variable
+ 'am_cv_prog_cc_c_o', and said result can be overridden by
+ pre-defining that variable.
+
+ - The AM_PROG_CC_C_O macro can still be called, albeit that should no
+ longer be necessary. This macro is now just a thin wrapper around the
+ Automake-enhanced AC_PROG_CC. This means, among the other things,
+ that its behaviour is changed in three ways:
+
+ 1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
+ macro behind the scenes.
+
+ 2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
+ and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
+ dynamically computed only at configure runtime (really!) from
+ the content of the '$CC' variable.
+
+ 3. It no longer automatically AC_DEFINE the C preprocessor
+ symbol 'NO_MINUS_C_MINUS_O'.
+
+* Texinfo support:
+
+ - Automake can now be instructed to place '.info' files generated from
+ Texinfo input in the builddir rather than in the srcdir; this is done
+ specifying the new automake option 'info-in-builddir'. This feature
+ was requested by the developers of GCC, GDB, GNU binutils and the GNU
+ bfd library. See the extensive discussion about automake bug#11034
+ for more details.
+
+ - For quite a long time, Automake has been implementing an undocumented
+ hack which ensured that '.info' files which appeared to be cleaned
+ (by being listed in the CLEANFILES or DISTCLEANFILES variables) were
+ built in the builddir rather than in the srcdir; this hack was
+ introduced to ensure better backward-compatibility with package
+ such as Texinfo, which do things like:
+
+ info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
+ DISTCLEANFILES = texinfo texinfo-* info*.info*
+ # Do not create info files for distribution.
+ dist-info:
+ @:
+
+ in order not to distribute generated '.info' files.
+
+ Now that we have the 'info-in-builddir' option that explicitly causes
+ generated '.info' files to be placed in the builddir, this hack should
+ be longer necessary, so we deprecate it with runtime warnings.
+ It will be removed altogether in Automake 2.0.
+
+* Relative directory in Makefile fragments:
+
+ - The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
+ (and their short versions, '%D%' and '%C%' respectively) can now be used
+ in an included Makefile fragment. The former is substituted with the
+ relative directory of the included fragment (compared to the top-level
+ including Makefile), and the latter with the canonicalized version of
+ the same relative directory.
+
+ # in 'Makefile.am':
+ bin_PROGRAMS = # will be updated by included Makefile fragments
+ include src/Makefile.inc
+
+ # in 'src/Makefile.inc':
+ bin_PROGRAMS += %reldir%/foo
+ %canon_reldir%_foo_SOURCES = %reldir%/bar.c
+
+ This should be especially useful for packages using a non-recursive
+ build system.
+
+* Deprecated distribution formats:
+
+ - The 'shar' and 'compress' distribution formats are deprecated, and
+ scheduled for removal in Automake 2.0. Accordingly, the use of the
+ 'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
+ (in the 'obsolete' category), and the recipes of the Automake-generated
+ targets 'dist-shar' and 'dist-tarZ' will unconditionally display
+ (non-fatal) warnings at make runtime.
+
+* New configure runtime warnings about "rm -f" support:
+
+ - To simplify transition to Automake 2.0, the shell code expanded by
+ AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
+ 'rm' program in PATH doesn't complain when called without any
+ non-option argument if the '-f' option is given (so that commands like
+ "rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
+ If this is not the case, the configure script is aborted, to call the
+ attention of the user on the issue, and invite him to fix his PATH.
+ The checked 'rm' behavior is very widespread in the wild, and will be
+ required by future POSIX versions:
+
+
+
+ The user can still force the configure process to complete even in the
+ presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
+ environment variable to "yes". And the generated Makefiles should
+ still work correctly even when such broken 'rm' is used. But note
+ that this will no longer be the case with Automake 2.0 though, so, if
+ you encounter the warning, please report it to us ASAP (and try to fix
+ your environment as well).
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.13.4:
+
+* Bugs fixed:
+
+ - Fix a minor regression introduced in Automake 1.13.3: when two or more
+ user-defined suffix rules were present in a single Makefile.am,
+ automake would needlessly include definition of some make variables
+ related to C compilation in the generated Makefile.in (bug#14560).
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.13.3:
+
+* Documentation fixes:
+
+ - The documentation no longer mistakenly reports that the obsolete
+ 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
+ to be removed in Automake 2.0.
+
+* Bugs fixed:
+
+ - Byte-compilation of Emacs lisp files could fail spuriously on
+ Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
+
+ - If the same user-defined suffixes were transformed into different
+ Automake-known suffixes in different Makefile.am files in the same
+ project, automake could get confused and generate inconsistent
+ Makefiles (automake bug#14441).
+ For example, if 'Makefile.am' contained a ".ext.cc:" suffix rule,
+ and 'sub/Makefile.am' contained a ".ext.c:" suffix rule, automake
+ would have mistakenly placed into 'Makefile.in' rules to compile
+ "*.c" files into object files, and into 'sub/Makefile.in' rules to
+ compile "*.cc" files into object files --- rather than the other
+ way around. This is now fixed.
+
+* Testsuite work:
+
+ - The test cases no longer have the executable bit set. This should
+ make it clear that they are not meant to be run directly; as
+ explained in t/README, they can only be run through the custom
+ 'runtest' script, or by a "make check" invocation.
+
+ - The testsuite has seen the introduction of a new helper function
+ 'run_make', and several related changes. These serve a two-fold
+ purpose:
+
+ 1. Remove brittleness due to the use of "make -e" in test cases.
+
+ 2. Seamlessly allow the use of parallel make ("make -j...") in the
+ test cases, even where redirection of make output is involved
+ (see automake bug#11413 for a description of the subtle issues
+ in this area).
+
+ - Several spurious failures have been fixed (they hit especially
+ MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
+ #14498, #14499, #14500, #14501, #14517 and #14528.
+
+ - Some other minor miscellaneous changes and fixlets.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.13.2:
+
+* Documentation fixes:
+
+ - The long-deprecated but still supported two-arguments invocation form
+ of AM_INIT_AUTOMAKE is documented once again. This seems the sanest
+ thing to do, given that support for such usage might need to remain
+ in place for an unspecified amount of time in order to cater to people
+ who want to define the version number for their package dynamically at
+ configure runtime (unfortunately, Autoconf does not yet support this
+ scenario, so we cannot delegate the work to it).
+
+ - The serial testsuite harness is no longer reported as "deprecated",
+ but as "discouraged". We have no plan to remove it, nor to make its
+ use cause runtime warnings.
+
+ - The parallel testsuite is no longer reported as "experimental"; it
+ is well tested, and should be stable now.
+
+ - The 'shar' and 'tarZ' distribution formats and the 'dist-shar' and
+ 'dist-tarZ' options are obsolescent, and their use is deprecated
+ in the documentation.
+
+ - Other minor miscellaneous fixes and improvements; in particular,
+ some improvements in cross-references.
+
+* Obsolescent features:
+
+ - Use of suffix-less info files (that can be specified through the
+ '@setfilename' macro in Texinfo input files) is discouraged, and
+ its use will raise warnings in the 'obsolete' category. Simply
+ use the '.info' extension for all your info files, transforming
+ usages like:
+
+ @setfilename myprogram
+
+ into:
+
+ @setfilename myprogram.info
+
+ - Use of Texinfo input files with '.txi' or '.texinfo' extensions
+ is discouraged, and its use will raise warnings in the 'obsolete'
+ category. You are advised to simply use the '.texi' extension
+ instead.
+
+* Bugs fixed:
+
+ - When the 'ustar' option is used, the generated configure script no
+ longer risks hanging during the tests for the availability of the
+ 'pax' utility, even if the user running configure has a UID or GID
+ that requires more than 21 bits to be represented.
+ See automake bug#8343 and bug#13588.
+
+ - The obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC work once
+ again, as they did in Automake 1.12.x (albeit printing runtime
+ warnings in the 'obsolete' category). Removing them has turned
+ out to be a very bad idea, because it complicated distro packing
+ enormously. Making them issue fatal warnings, as we did in
+ Automake 1.13, has turned out to be a similarly very bad idea,
+ for exactly the same reason.
+
+ - aclocal will no longer error out if the first local m4 directory
+ (as specified by the '-I' option or the 'AC_CONFIG_MACRO_DIRS' or
+ 'AC_CONFIG_MACRO_DIR' macros) doesn't exist; it will merely report
+ a warning in the 'unsupported' category. This is done to support
+ some pre-existing real-world usages. See automake bug#13514.
+
+ - aclocal will no longer consider directories for extra m4 files more
+ than once, even if they are specified multiple times. This ensures
+ packages that specify both
+
+ AC_CONFIG_MACRO_DIR([m4]) in configure.ac
+ ACLOCAL_AMFLAGS = -I m4 in Makefile.am
+
+ will work correctly, even when the 'm4' directory contains no
+ package-specific files, but is used only to install third-party
+ m4 files (as can happen with e.g., "libtoolize --install").
+ See automake bug#13514.
+
+ - Analysis of make flags in Automake-generated rules has been made more
+ robust, and more future-proof. For example, in presence of make that
+ (like '-I') take an argument, the characters in said argument will no
+ longer be spuriously considered as a set of additional make options.
+ In particular, automake-generated rules will no longer spuriously
+ believe to be running in dry mode ("make -n") if run with an invocation
+ like "make -I noob"; nor will they believe to be running in keep-going
+ mode ("make -k") if run with an invocation like "make -I kool"
+ (automake bug#12554).
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.13.1:
+
+* Bugs fixed:
+
+ - Use of the obsolete macros AM_CONFIG_HEADER or AM_PROG_CC_STDC now
+ causes a clear and helpful error message, instead of obscure ones
+ (issue introduced in Automake 1.13).
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.13:
+
+* Bugs fixed:
+
+ - ylwrap renames properly header guards in generated header files
+ (*.h), instead of leaving Y_TAB_H.
+
+ - ylwrap now also converts header guards in implementation files
+ (*.c). Because ylwrap failed to rename properly #include in the
+ implementation files, current versions of Bison (e.g., 2.7)
+ duplicate the generated header file in the implementation file.
+ The header guard then protects the implementation file from
+ duplicate definitions from the header file.
+
+* Version requirements:
+
+ - Autoconf 2.65 or greater is now required.
+
+ - The rules to build PDF and DVI output from Texinfo input now
+ require Texinfo 4.9 or later.
+
+* Obsolete features:
+
+ - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
+ option) has been removed. See discussion about automake bug#11034
+ for more background: .
+
+ - The deprecated aclocal option '--acdir' has been removed. You
+ should use the options '--automake-acdir' and '--system-acdir'
+ instead (which have been introduced in Automake 1.11.2).
+
+ - The following long-obsolete m4 macros have been removed:
+
+ AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
+ fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
+ fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
+ AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
+ ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
+ jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
+ ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
+ gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
+ fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
+ of the now-removed automatic de-ANSI-fication
+ support of Automake)
+
+ - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
+
+ - Use of the long-deprecated two- and three-arguments invocation forms
+ of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
+ though (albeit with a warning in the 'obsolete' category), to cater
+ for people who want to define the version number for their package
+ dynamically (e.g., from the current VCS revision). We'll have to
+ continue this support until Autoconf itself is fixed to allow better
+ support for such dynamic version numbers.
+
+* Elisp byte-compilation:
+
+ - The byte compilation of '.el' files into '.elc' files is now done
+ with a suffix rule. This has simplified the compilation process, and
+ more importantly made it less brittle. The downside is that emacs is
+ now invoked once for each '.el' files, which cause some noticeable
+ slowdowns. These should however be mitigated on multicore machines
+ (which are becoming the norm today) if concurrent make ("make -j")
+ is used.
+
+ - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
+ files in the same subdirectory; for example, byte-compiling of file
+ 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
+ 'foo.elc'. This behaviour is backward-incompatible with older
+ Automake versions, but it is more natural and more sane. See also
+ automake bug#7441.
+
+ - The Emacs invocation performing byte-compilation of '.el' files honors
+ the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
+ one is developer-reserved and the latter one user-reserved.
+
+ - The 'elisp-comp' script, once provided by Automake, has been rendered
+ obsoleted by the just-described changes, and thus removed.
+
+* Changes to Automake-generated testsuite harnesses:
+
+ - The parallel testsuite harness (previously only enabled by the
+ 'parallel-tests' option) is the default one; the older serial
+ testsuite harness will still be available through the use of the
+ 'serial-tests' option (introduced in Automake 1.12).
+
+ - The 'color-tests' option is now unconditionally activated by default.
+ In particular, this means that testsuite output is now colorized by
+ default if the attached terminal seems to support ANSI escapes, and
+ that the user can force output colorization by setting the variable
+ AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
+ for backward-compatibility, although it's a handled as a no-op now.
+
+* Silent rules support:
+
+ - Support for silent rules is now always active in Automake-generated
+ Makefiles. So, although the verbose output is still the default,
+ the user can now always use "./configure --enable-silent-rules" or
+ "make V=0" to enable quieter output in the package he's building.
+
+ - The 'silent-rules' option has now become a no-op, preserved for
+ backward-compatibility only. In particular, its use no longer
+ disables the warnings in the 'portability-recursive' category.
+
+* Texinfo Support:
+
+ - The rules to build PDF and DVI files from Texinfo input now require
+ Texinfo 4.9 or later.
+
+ - The rules to build PDF and DVI files from Texinfo input now use the
+ '--build-dir' option, to keep the auxiliary files used by texi2dvi
+ and texi2pdf around without cluttering the build directory, and to
+ make it possible to run the "dvi" and "pdf" recipes in parallel.
+
+* Automatic remake rules and 'missing' script:
+
+ - The 'missing' script no longer tries to update the timestamp of
+ out-of-date files that require a maintainer-specific tool to be
+ remade, in case the user lacks such a tool (or has a too-old version
+ of it). It just gives a useful warning, and in some cases also a
+ tip about how to obtain such a tool.
+
+ - The missing script has thus become useless as a (poor) way to work
+ around the sketched-timestamps issues that can happen for projects
+ that keep generated files committed in their VCS repository. Such
+ projects are now encouraged to write a custom "fix-timestamps.sh"
+ script to avoid such issues; a simple example is provided in the
+ "CVS and generated files" chapter of the automake manual.
+
+* Recursive targets:
+
+ - The user can now define his own recursive targets that recurse
+ in the directories specified in $(SUBDIRS). This can be done by
+ specifying the name of such targets in invocations of the new
+ 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
+
+* Tags:
+
+ - Any failure in the recipe of the "tags", "ctags", "cscope" or
+ "cscopelist" targets in a subdirectory is now propagated to the
+ top-level make invocation.
+
+ - Tags are correctly computed also for files in _SOURCES variables that
+ only list files with non-standard suffixes (see automake bug#12372).
+
+* Improvements to aclocal and related rebuilds rules:
+
+ - Autoconf-provided macros AC_CONFIG_MACRO_DIR and AC_CONFIG_MACRO_DIRS
+ are now traced by aclocal, and can be used to declare the local m4
+ include directories. Formerly, one had to specify it with an explicit
+ '-I' option to the 'aclocal' invocation.
+
+ - The special make variable ACLOCAL_AMFLAGS is deprecated; future
+ Automake versions will warn about its use, and later version will
+ remove support for it altogether.
+
+* The depcomp script:
+
+ - Dropped support for libtool 1.4.
+
+ - Various internal refactorings. They should cause no visible change,
+ but the chance for regression is there anyway, so please report any
+ unexpected or suspicious behaviour.
+
+ - Support for pre-8.0 versions of the Intel C Compiler has been dropped.
+ This should cause no problem, since icc 8.0 has been released in
+ December 2003 -- almost nine years ago.
+
+ - Support for tcc (the Tiny C Compiler) has been improved, and is now
+ handled through a dedicated 'tcc' mode.
+
+* The ylwrap script:
+
+ - ylwrap generates header guards with a single '_' for series of non
+ alphabetic characters, instead of several. This is what Bison >=
+ 2.5.1 does.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bugs fixed in 1.12.6:
+
+* Python-related bugs:
+
+ - The default installation location for python modules has been improved
+ for Python 3 on Debian and Ubuntu systems, changing from:
+
+ ${prefix}/lib/python3/dist-packages
+
+ to
+
+ ${prefix}/lib/python3.x/site-packages
+
+ This change should ensure modules installed using the default ${prefix}
+ "/usr/local" are found by default by system python 3.x installations.
+ See automake bug#10227.
+
+ - Python byte-compilation supports the new layout mandated by PEP-3147,
+ with its __pycache__ directory (automake bug#8847).
+
+* Build system issues:
+
+ - The maintainer rebuild rules for Makefiles and aclocal.m4 in
+ Automake's own build system works correctly again (bug introduced
+ in Automake 1.12.5).
+
+* Testsuite issues:
+
+ - The Vala-related tests has been changed to adjust to the removal of
+ the 'posix' profile in the valac compiler. See automake bug#12934
+ a.k.a. bug#12522.
+
+ - Some spurious testsuite failures related to older tools and systems
+ have been fixed.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.12.5:
+
+* Vala support:
+
+ - The AM_PROG_VALAC macro has been enhanced to takes two further
+ optional arguments; it's signature now being
+
+ AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
+ [ACTION-IF-NOT-FOUND])
+
+ - By default, AM_PROG_VALAC no longer aborts the configure invocation
+ if the Vala compiler found is too old, but simply prints a warning
+ messages (as it did when the Vala compiler was not found). This
+ should avoid unnecessary difficulties for end users that just want
+ to compile the unmodified, distributed Vala-generated C sources,
+ but happens to have an old Vala compiler in their PATH. This fixes
+ automake bug#12688.
+
+ - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
+ will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
+ This is a better default, because with it a triggered makefile rule
+ invoking a Vala compilation will clearly fail with an informative error
+ message like "valac: command not found", rather than silently, with
+ the error possibly going unnoticed or triggering harder-to-diagnose
+ fallout failures in later steps.
+
+* Miscellaneous changes:
+
+ - automake and aclocal no longer honours the 'perllibdir' environment
+ variable. That had always been intended only as an hack required in
+ the testsuite, not meant for any use beyond that.
+
+Bugs fixed in 1.12.5:
+
+* Long-standing bugs:
+
+ - Automake no longer generates spurious remake rules invoking autoheader
+ to regenerate the template corresponding to header files specified after
+ the first one in AC_CONFIG_HEADERS (automake bug#12495).
+
+ - When wrapping Microsoft tools, the 'compile' script falls back to
+ finding classic 'libname.a' style libraries when 'name.lib' and
+ 'name.dll.lib' aren't available.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.12.4:
+
+* Warnings and deprecations:
+
+ - Warnings in the 'obsolete' category are enabled by default both in
+ automake and aclocal.
+
+* Miscellaneous changes:
+
+ - Some testsuite weaknesses and spurious failures have been fixed.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.12.3:
+
+* Miscellaneous changes:
+
+ - The '.m4' files provided by Automake no longer define serial numbers.
+ This should cause no difference in the behaviour of aclocal though.
+
+ - Some testsuite weaknesses and spurious failures have been fixed.
+
+ - There is initial support for automatic dependency tracking with the
+ Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
+
+Bugs fixed in 1.12.3:
+
+* Long-standing bugs:
+
+ - Instead of renaming only self-references of files (typically for
+ #lines), ylwrap now also renames references to the other generated
+ files. This fixes support for GLR and C++ parsers from Bison (PR
+ automake/491 and automake bug#7648): 'parser.c' now properly
+ #includes 'parser.h' instead of 'y.tab.h'.
+
+ - Generated files unknown to ylwrap are now preserved. This fixes
+ C++ support for Bison (automake bug#7648): location.hh and the
+ like are no longer discarded.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.12.2:
+
+* Warnings and deprecations:
+
+ - Automake now issues a warning (in the 'portability' category) if
+ 'configure.in' is used instead of 'configure.ac' as the Autoconf
+ input file. Such a warning will also be present in the next
+ Autoconf version (2.70).
+
+* Cleaning rules:
+
+ - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
+ order (as done by the other recursive rules), rather than in the
+ inverse order. They used to do that in order to work a round a
+ limitation in an older implementation of the automatic dependency
+ tracking support, but that limitation had been lifted years ago
+ already, when the automatic dependency tracking based on side-effects
+ of compilation had been introduced.
+
+ - Cleaning rules for compiled objects (both "plain" and libtool) work
+ better when subdir objects are involved, not triggering a distinct
+ 'rm' invocation for each such object. They do so by removing *any*
+ compiled object file that is in the same directory of a subdir
+ object. See automake bug#10697.
+
+* Silent rules support:
+
+ - A new predefined $(AM_V_P) make variable is provided; it expands
+ to a shell conditional that can be used in recipes to know whether
+ make is being run in silent or verbose mode.
+
+Bugs fixed in 1.12.2:
+
+* SECURITY VULNERABILITIES!
+
+ - The 'distcheck' recipe no longer grants temporary world-write
+ permissions on the extracted distdir. Even if such rights were
+ only granted for a vanishingly small time window, the implied
+ race condition proved to be enough to allow a local attacker
+ to run arbitrary code with the privileges of the user running
+ "make distcheck". This is CVE-2012-3386.
+
+* Long-standing bugs:
+
+ - The "recheck" targets behaves better in the face of build failures
+ related to previously failed tests. For example, if a test is a
+ compiled program that must be rerun by "make recheck", and its
+ compilation fails, it will still be rerun by further "make recheck"
+ invocations. See automake bug#11791.
+
+* Bugs introduced by 1.12.1:
+
+ - Automake provides once again the '$(mkdir_p)' make variable and the
+ '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
+ for better backward-compatibility.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.12.1:
+
+* New supported languages:
+
+ - Support for Objective C++ has been added; it should work similarly to
+ the support for Objective C.
+
+* Deprecated obsolescent features:
+
+ - Use of the long-deprecated two- and three-arguments invocation forms
+ of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
+ category. Starting from some future major Automake release (likely
+ post-1.13), such usages will no longer be allowed.
+
+ - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
+ now deprecated (its use triggers a warning in the 'obsolete' category).
+ It will be removed in the next major Automake release (1.13).
+
+ - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
+ variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
+ m4 macro are deprecated, eliciting a warning in the 'obsolete'
+ category.
+
+* Miscellaneous changes:
+
+ - The Automake test cases now require a proper POSIX-conforming shell.
+ Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
+ be accepted. In most cases, the user shouldn't have to specify such
+ POSIX shell explicitly, since it will be looked up at configure time.
+ Still, when this lookup fails, or when the user wants to override its
+ conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
+ to the shell that will be used to run the Automake test cases).
+
+Bugs fixed in 1.12.1:
+
+* Bugs introduced by 1.12:
+
+ - Several weaknesses in Automake's own build system and test suite
+ have been fixed.
+
+* Bugs introduced by 1.11.3:
+
+ - When given non-option arguments, aclocal rejects them, instead of
+ silently ignoring them.
+
+* Long-standing bugs:
+
+ - When the 'color-tests' option is in use, forcing of colored testsuite
+ output through "AM_COLOR_TESTS=always" works even if the terminal is
+ a non-ANSI one, i.e., if the TERM environment variable has a value of
+ "dumb".
+
+ - Several inefficiencies and poor performances in the implementation
+ of the parallel-tests 'check' and 'recheck' targets have been fixed.
+
+ - The post-processing of output "#line" directives done the ylwrap
+ script is more faithful w.r.t. files in a subdirectory; for example,
+ if the processed file is "src/grammar.y", ylwrap will correctly
+ produce directives like:
+ #line 7 "src/grammar.y"
+ rather than like
+ #line 7 "grammar.y"
+ as it did before.
+
+* Bugs with new Perl versions:
+
+ - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.12:
+
+* Obsolete features removed:
+
+ - The never documented nor truly used script 'acinstall' has been
+ removed.
+
+ - Support for automatic de-ANSI-fication has been removed.
+
+ - The support for the "obscure" multilib feature has been removed
+ from Automake core (but remains available in the 'contrib/'
+ directory of the Automake distribution).
+
+ - Support for ".log -> .html" conversion and the check-html and
+ recheck-html targets has been removed from Automake core (but
+ remains available in the 'contrib/' directory of the Automake
+ distribution).
+
+ - The deprecated 'lzma' compression format for distribution archives
+ has been removed, in favor of 'xz' and 'lzip'.
+
+ - The obsolete AM_WITH_REGEX macro has been removed.
+
+ - The long-deprecated options '--output-dir', '--Werror' and
+ '--Wno-error' have been removed.
+
+ - The chapter on the history of Automake has been moved out of the
+ reference manual, into a new dedicated Texinfo file.
+
+* New targets:
+
+ - New 'cscope' target to build a cscope database for the source tree.
+
+* Changes to Automake-generated testsuite harnesses:
+
+ - The new automake option 'serial-tests' has been introduced. It can
+ be used to explicitly instruct automake to use the older serial
+ testsuite harness. This is still the default at the moment, but it
+ might change in future versions.
+
+ - The 'recheck' target (provided by the parallel testsuite harness) now
+ depends on the 'all' target. This allows for a better user-experience
+ in test-driven development. See automake bug#11252.
+
+ - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
+ and unexpected or internal error, or a failure to set up the test case
+ scenario) have their outcome reported as an 'ERROR' now. Previous
+ versions of automake reported such an outcome as a 'FAIL' (the only
+ difference with normal failures being that hard errors were counted
+ as failures even when the test originating them was listed in
+ XFAIL_TESTS).
+
+ - The testsuite summary displayed by the parallel-test harness has a
+ completely new format, that always list the numbers of passed, failed,
+ xfailed, xpassed, skipped and errored tests, even when these numbers
+ are zero (but using smart coloring when the color-tests option is in
+ effect).
+
+ - The default testsuite driver offered by the 'parallel-tests' option is
+ now implemented (partly at least) with the help of automake-provided
+ auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
+ on code in the generated Makefile.in.
+ This has two noteworthy implications. The first one is that projects
+ using the 'parallel-tests' option should now either run automake with
+ the '--add-missing' option, or manually copy the 'test-driver' script
+ into their tree. The second, and more important, implication is that
+ now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
+ no longer be used to define a test runner, and the command specified
+ in LOG_COMPILER (and _LOG_COMPILER) must be a *real* executable
+ program or script. For example, this is still a valid usage (albeit
+ a little contorted):
+
+ TESTS_ENVIRONMENT = \
+ if test -n '$(STRICT_TESTS)'; then \
+ maybe_errexit='-e'; \
+ else \
+ maybe_errexit=''; \
+ fi;
+ LOG_COMPILER = $(SHELL) $$maybe_errexit
+
+ OTOH, this is no longer a valid usage:
+
+ TESTS_ENVIRONMENT = \
+ $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
+
+ neither is this:
+
+ TESTS_ENVIRONMENT = \
+ run_with_perl_or_shell () \
+ { \
+ if grep -q '^#!.*perl' $$1; then
+ $(PERL) $$1; \
+ else \
+ $(SHELL) $$1; \
+ fi; \
+ }
+ LOG_COMPILER = run_with_perl_or_shell
+
+ - The package authors can now use customary testsuite drivers within
+ the framework provided by the 'parallel-tests' testsuite harness.
+ Consistently with the existing syntax, this can be done by defining
+ special makefile variables 'LOG_DRIVER' and '_LOG_DRIVER'.
+
+ - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
+ to redirect/define file descriptors used by the test scripts.
+
+ - The parallel-tests harness generates now, in addition the '.log' files
+ holding the output produced by the test scripts, a new set of '.trs'
+ files, holding "metadata" derived by the execution of the test scripts;
+ among such metadata are the outcomes of the test cases run by a script.
+
+ - Initial and still experimental support for the TAP test protocol is
+ now provided.
+
+* Changes to Yacc and Lex support:
+
+ - C source and header files derived from non-distributed Yacc and/or
+ Lex sources are now removed by a simple "make clean" (while they were
+ previously removed only by "make maintainer-clean").
+
+ - Slightly backward-incompatible change, relevant only for use of Yacc
+ with C++: the extensions of the header files produced by the Yacc
+ rules are now modelled after the extension of the corresponding
+ sources. For example, yacc files named "foo.y++" and "bar.yy" will
+ produce header files named "foo.h++" and "bar.hh" respectively, where
+ they would have previously produced header files named simply "foo.h"
+ and "bar.h". This change offers better compatibility with 'bison -o'.
+
+* Miscellaneous changes:
+
+ - The AM_PROG_VALAC macro now causes configure to exit with status 77,
+ rather than 1, if the vala compiler found is too old.
+
+ - The build system of Automake itself now avoids the use of make
+ recursion as much as possible.
+
+ - Automake now prefers to quote 'like this' or "like this", rather
+ than `like this', in diagnostic message and generated Makefiles,
+ to accommodate the new GNU Coding Standards recommendations.
+
+ - Automake has a new option '--print-libdir' that prints the path of the
+ directory containing the Automake-provided scripts and data files.
+
+ - The 'dist' and 'dist-all' targets now can run compressors in parallel.
+
+ - The rules to create pdf, dvi and ps output from Texinfo files now
+ works better with modern 'texi2dvi' script, by explicitly passing
+ it the '--clean' option to ensure stray auxiliary files are not
+ left to clutter the build directory.
+
+ - Automake can now generate silenced rules for texinfo outputs.
+
+ - Some auxiliary files that are automatically distributed by Automake
+ (e.g., 'install-sh', or the 'depcomp' script for packages compiling
+ C sources) might now be listed in the DIST_COMMON variable in many
+ Makefile.in files, rather than in the top-level one.
+
+ - Messages of types warning or error from 'automake' and 'aclocal'
+ are now prefixed with the respective type, and presence of -Werror
+ is noted.
+
+ - Automake's early configure-time sanity check now tries to avoid
+ sleeping for a second, which slowed down cached configure runs
+ noticeably. In that case, it will check back at the end of the
+ configure script to ensure that at least one second has passed, to
+ avoid time stamp issues with makefile rules rerunning autotools
+ programs.
+
+ - The warnings in the category 'extra-portability' are now enabled by
+ '-Wall'. In previous versions, one has to use '-Wextra-portability'
+ to enable them.
+
+Bugs fixed in 1.12:
+
+ - Various minor bugfixes for recent or long-standing bugs.
+
+* Bugs introduced by 1.11:
+
+ - The AM_COND_IF macro also works if the shell expression for the
+ conditional is no longer valid for the condition.
+
+ - The automake-provided parallel testsuite harness no longer fails
+ with BSD make used in parallel mode when there are test scripts in
+ a subdirectory, like in:
+
+ TESTS = sub/foo.test sub/bar.test
+
+* Long-standing bugs:
+
+ - Automake's own build system finally have a real "installcheck" target.
+
+ - Vala-related cleanup rules are now more complete, and work better in
+ a VPATH setup.
+
+ - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
+ now automatically distributed also if the directory of the auxiliary
+ files coincides with the top-level directory.
+
+ - Automake now detects the presence of the '-d' flag in the various
+ '*YFLAGS' variables even when their definitions involve indirections
+ through other variables, such as in:
+ foo_opts = -d
+ AM_YFLAGS = $(foo_opts)
+
+ - Automake now complains if a '*YFLAGS' variable has any conditional
+ content, not only a conditional definition.
+
+ - Explicit enabling and/or disabling of Automake warning categories
+ through the '-W...' options now always takes precedence over the
+ implicit warning level implied by Automake strictness (foreign, gnu
+ or gnits), regardless of the order in which such strictness and
+ warning flags appear. For example, a setting like:
+ AUTOMAKE_OPTIONS = -Wall --foreign
+ will cause the warnings in category 'portability' to be enabled, even
+ if those warnings are by default disabled in 'foreign' strictness.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bugs fixed in 1.11.5:
+
+* Bugs introduced by 1.11.3:
+
+ - Vala files with '.vapi' extension are now recognized and handled
+ correctly again. See automake bug#11222.
+
+ - Vala support work again for projects that contain some program
+ built from '.vala' (and possibly '.c') sources and some other
+ program built from '.c' sources *only*. See automake bug#11229.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.11.4:
+
+* Miscellaneous changes:
+
+ - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
+ symbol index) modifiers as well as the "s" action, as the symbol index
+ is created unconditionally by Microsoft lib. Also, the "q" (quick)
+ action is now a synonym for "r" (replace). Also, the script has been
+ ignoring the "v" (verbose) modifier already since Automake 1.11.3.
+
+ - When the 'compile' script is used to wrap MSVC, it now accepts an
+ optional space between the -I, -L and -l options and their respective
+ arguments, for better POSIX compliance.
+
+ - There is an initial, experimental support for automatic dependency
+ tracking with tcc (the Tiny C Compiler). Its associated depmode is
+ currently recognized as "icc" (but this and other details are likely
+ to change in future versions).
+
+ - Automatic dependency tracking now works also with the IBM XL C/C++
+ compilers, thanks to the new new depmode 'xlc'.
+
+Bugs fixed in 1.11.4:
+
+* Bugs introduced by 1.11.2:
+
+ - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
+ no longer cause spurious failures upon "make install".
+
+ - The user can now instruct the 'uninstall-info' rule not to update
+ the '${infodir}/dir' file by exporting the environment variable
+ 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
+ with how the 'install-info' rule operates since automake 1.11.2.
+
+* Long-standing bugs:
+
+ - It is now possible for a foo_SOURCES variable to hold Vala sources
+ together with C header files, as well as with sources and headers for
+ other supported languages (e.g., C++). Previously, only mixing C and
+ Vala sources was supported.
+
+ - If "aclocal --install" is used, and the first directory specified with
+ '-I' is non-existent, aclocal will now create it before trying to copy
+ files in it.
+
+ - An empty declaration of a "foo_PRIMARY" no longer cause the generated
+ install rules to create an empty $(foodir) directory; for example, if
+ Makefile.am contains something like:
+
+ pkglibexec_SCRIPTS =
+ if FALSE
+ pkglibexec_SCRIPTS += bar.sh
+ endif
+
+ the $(pkglibexec) directory will not be created upon "make install".
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.11.3:
+
+* Miscellaneous changes:
+
+ - Automake's own build system is more silent by default, making use of
+ the 'silent-rules' option.
+
+ - The master copy of the 'gnupload' script is now maintained in gnulib,
+ not in automake.
+
+ - The 'missing' script no longer tries to wrap calls to 'tar'.
+
+ - "make dist" no longer wraps 'tar' invocations with the 'missing'
+ script. Similarly, the obsolescent variable '$(AMTAR)' (which you
+ shouldn't be using BTW ;-) no longer invokes the 'missing' script
+ to wrap tar, but simply invokes the 'tar' program itself.
+ The TAR environment variable overrides.
+
+ - "make dist" can now create lzip-compressed tarballs.
+
+ - In the Automake info documentation, the Top node and the nodes about
+ the invocation of the automake and aclocal programs have been renamed;
+ now, calling "info automake" will open the Top node, while calling
+ "info automake-invocation" and "info aclocal-invocation" will access
+ the nodes about the invocation of respectively automake and aclocal.
+
+ - Automake is now distributed as a gzip-compressed and an xz-compressed
+ tarball. Previously, bzip2 was used instead of xz.
+
+ - The last relics of Python 1.5 support have been removed from the
+ AM_PATH_PYTHON macro.
+
+ - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
+ and adds them to the normal list of dependencies, but without
+ overwriting the foo_DEPENDENCIES variable, which is normally computed
+ by automake.
+
+Bugs fixed in 1.11.3:
+
+* Bugs introduced by 1.11.2:
+
+ - Automake now correctly recognizes the prefix/primary combination
+ 'pkglibexec_SCRIPTS' as valid.
+
+ - The parallel-tests harness no longer trips on sed implementations
+ with stricter limits on the length of input lines (problem seen at
+ least on Solaris 8).
+
+* Long-standing bugs:
+
+ - The "deleted header file problem" for *.am files is avoided by stub
+ rules. This allows 'make' to trigger a rerun of 'automake' also if
+ some previously needed '.am' file has been removed.
+
+ - The 'silent-rules' option now generates working makefiles even
+ for the uncommon 'make' implementations that do not support the
+ nested-variables extension to POSIX 2008. For such 'make'
+ implementations, whether a build is silent is determined at
+ configure time, and cannot be overridden at make time with
+ "make V=0" or "make V=1".
+
+ - Vala support now works better in VPATH setups.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.11.2:
+
+* Changes to aclocal:
+
+ - The `--acdir' option is deprecated. Now you should use the new options
+ `--automake-acdir' and `--system-acdir' instead.
+
+ - The `ACLOCAL_PATH' environment variable is now interpreted as a
+ colon-separated list of additional directories to search after the
+ automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
+ and before the system acdir (by default ${prefix}/share/aclocal).
+
+* Miscellaneous changes:
+
+ - The Automake support for automatic de-ANSI-fication has been
+ deprecated. It will probably be removed in the next major Automake
+ release (1.12).
+
+ - The `lzma' compression scheme and associated automake option `dist-lzma'
+ is obsoleted by `xz' and `dist-xz' due to upstream changes.
+
+ - You may adjust the compression options used in dist-xz and dist-bzip2.
+ The default is now merely -e for xz, but still -9 for bzip; you may
+ specify a different level via the XZ_OPT and BZIP2 envvars respectively.
+ E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
+
+ - The `compile' script now converts some options for MSVC for a better
+ user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
+
+ - The py-compile script now accepts empty arguments passed to the options
+ `--destdir' and `--basedir', and complains about unrecognized options.
+ Moreover, a non-option argument or a special `--' argument terminates
+ the list of options.
+
+ - A developer that needs to pass specific flags to configure at "make
+ distcheck" time can now, and indeed is advised to, do so by defining
+ the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
+ instead of the old DISTCHECK_CONFIGURE_FLAGS.
+ The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
+ user; still, the old Makefile.am files that used to define it will
+ still continue to work as before.
+
+ - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
+ 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
+ This new macro is required for LIBRARIES and LTLIBRARIES when automake
+ is run with -Wextra-portability and -Werror.
+
+ - When using DejaGnu-based testsuites, the user can extend the `site.exp'
+ file generated by automake-provided rules by defining the special make
+ variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
+
+ - The `install-info' rule can now be instructed not to create/update
+ the `${infodir}/dir' file, by exporting the new environment variable
+ `AM_UPDATE_INFO_DIR' to the value "no".
+
+Bugs fixed in 1.11.2:
+
+* Bugs introduced by 1.11:
+
+ - The parallel-tests driver no longer produces erroneous results with
+ Tru64/OSF 5.1 sh upon unreadable log files.
+
+ - The `parallel-tests' test driver does not report spurious successes
+ when used with concurrent FreeBSD make (e.g., "make check -j3").
+
+ - When the parallel-tests driver is in use, automake now explicitly
+ rejects invalid entries and conditional contents in TEST_EXTENSIONS,
+ instead of issuing confusing and apparently unrelated error messages
+ (e.g., "non-POSIX variable name", "bad characters in variable name",
+ or "redefinition of TEST_EXTENSIONS), or even, in some situations,
+ silently producing broken `Makefile.in' files.
+
+ - The `silent-rules' option now truly silences all compile rules, even
+ when dependency tracking is disabled. Also, when `silent-rules' is
+ not used, `make' output no longer contains spurious backslash-only
+ lines, thus once again matching what Automake did before 1.11.
+
+ - The AM_COND_IF macro also works if the shell expression for the
+ conditional is no longer valid for the condition.
+
+* Long-standing bugs:
+
+ - The order of Yacc and Lex flags is fixed to be consistent with other
+ languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
+ $(LFLAGS), so that the user variables override the developer variables.
+
+ - "make distcheck" now correctly complains also when "make uninstall"
+ leaves one and only one file installed in $(prefix).
+
+ - A "make uninstall" issued before a "make install", or after a mere
+ "make install-data" or a mere "make install-exec" does not spuriously
+ fail anymore.
+
+ - Automake now warns about more primary/directory invalid combinations,
+ such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
+
+ - Rules generated by Automake now try harder to not change any files when
+ `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
+ Yacc source files and the rule to update config.h.
+
+ - Several scripts and the parallel-tests testsuite driver now exit with
+ the right exit status upon receiving a signal.
+
+ - A per-Makefile.am setting of -Werror does not erroneously carry over
+ to the handling of other Makefile.am files.
+
+ - The code for automatic dependency tracking works around a Solaris
+ make bug triggered by sources containing repeated slashes when the
+ `subdir-objects' option was used.
+
+ - The makedepend and hp depmodes now work better with VPATH builds.
+
+ - Java sources specified with check_JAVA are no longer compiled for
+ "make all", but only for "make check".
+
+ - An usage like "java_JAVA = foo.java" will now cause Automake to warn
+ and error out if `javadir' is undefined, instead of silently producing
+ a broken Makefile.in.
+
+ - aclocal and automake now honour the configure-time definitions of
+ AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
+
+ - The `install-info' recipe no longer tries to guess whether the
+ `install-info' program is from Debian or from GNU, and adaptively
+ change its behaviour; this has proven to be frail and easy to
+ regress.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bugs fixed in 1.11.1:
+
+ - Lots of minor bugfixes.
+
+* Bugs introduced by 1.11:
+
+ - The `parallel-tests' test driver works around a GNU make 3.80 bug with
+ trailing white space in the test list (`TESTS = foo $(EMPTY)').
+
+* Long standing bugs:
+
+ - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
+ even if the `--prefix' argument pointed outside of a system directory.
+ AM_PATH_PYTHON has been fixed to ignore the value returned from python's
+ `get_python_lib' function if it points outside the configured prefix,
+ unless the `--prefix' argument was either `/usr' or below `/System'.
+
+ - The testsuite does not try to change the mode of `ltmain.sh' files from
+ a Libtool installation (symlinked to test directories) any more.
+
+ - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
+ tools are preferred in a cross-compile setup.
+
+ - The distribution is tarred up with mode 755 now by the `dist*' targets.
+ This fixes a race condition where untrusted users could modify files
+ in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
+ build directory was world-searchable. This is CVE-2009-4029.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.11:
+
+* Version requirements:
+
+ - Autoconf 2.62 or greater is required.
+
+* Changes to aclocal:
+
+ - The autoconf version check implemented by aclocal in aclocal.m4
+ (and new in Automake 1.10) is degraded to a warning. This helps
+ in the common case where the Autoconf versions used are compatible.
+
+* Changes to automake:
+
+ - The automake program can run multiple threads for creating most
+ Makefile.in files concurrently, if at least Perl 5.7.2 is available
+ with interpreter-based threads enabled. Set the environment variable
+ AUTOMAKE_JOBS to the maximum number of threads to use, in order to
+ enable this experimental feature.
+
+* Changes to Libtool support:
+
+ - Libtool generic flags are now passed to the install and uninstall
+ modes as well.
+
+ - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
+ config.lt is removed correctly now.
+
+* Languages changes:
+
+ - subdir-object mode works now with Fortran (F77, FC, preprocessed
+ Fortran, and Ratfor).
+
+ - For files with extension .f90, .f95, .f03, or .f08, the flag
+ $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
+
+ - Files with extension .sx are also treated as preprocessed assembler.
+
+ - The default source file extension (.c) can be overridden with
+ AM_DEFAULT_SOURCE_EXT now.
+
+ - Python 3.0 is supported now, Python releases prior to 2.0 are no
+ longer supported.
+
+ - AM_PATH_PYTHON honors python's idea about the site directory.
+
+ - There is initial support for the Vala programming language, when using
+ Vala 0.7.0 or later.
+
+* Miscellaneous changes:
+
+ - Automake development is done in a git repository on Savannah now, see
+
+ https://git.sv.gnu.org/gitweb/?p=automake.git
+
+ A read-only CVS mirror is provided at
+
+ cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
+ checkout -d automake HEAD
+
+ - "make dist" can now create xz-compressed tarballs,
+ as well as (deprecated?) lzma-compressed tarballs.
+
+ - `automake --add-missing' will by default install the GPLv3 file as
+ COPYING if it is missing. It will also warn that the license file
+ should be added to source control. Note that Automake will never
+ overwrite an existing COPYING file, even when the `--force-missing'
+ option is used.
+
+ - The manual is now distributed under the terms of the GNU FDL 1.3.
+
+ - Automake ships and installs man pages for automake and aclocal now.
+
+ - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
+
+ - install-sh supports -C, which does not update the installed file
+ (and its time stamps) if the contents did not change.
+
+ - The `gnupload' script has been revamped.
+
+ - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
+
+ - The targets `install' and `uninstall' are more efficient now, in that
+ for example multiple files from one Automake variable such as
+ `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
+ invocation if they do not have to be renamed.
+
+ Both install and uninstall may sometimes enter (`cd' into) the target
+ installation directory now, when no build-local scripts are used.
+
+ Both install and uninstall do not fail anymore but do nothing if an
+ installation directory variable like `bindir' is set to the empty string.
+
+ For built-in rules, `make install' now fails reliably if installation
+ of a file failed. Conversely, `make uninstall' even succeeds when
+ issued multiple times.
+
+ These changes may need some adjustments from users: For example,
+ some `install' programs refuse to install multiple copies of the
+ same file in one invocation, so you may need to remove duplicate
+ entries from file lists.
+
+ Also, within one set of files, say, nobase_data_DATA, the order of
+ installation may be changed, or even unstable among different hosts,
+ due to the use of associative arrays in awk. The increased use of
+ awk matches a similar move in Autoconf to provide for better scaling.
+
+ Further, most undocumented per-rule install command variables such as
+ binSCRIPT_INSTALL have been removed because they are not needed any
+ more. Packages which use them should be using the appropriate one of
+ INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
+ counterpart, depending on the type of files and the need for automatic
+ target directory creation.
+
+ - The "deleted header file problem" for *.m4 files is avoided by
+ stub rules. This allows `make' to trigger a rerun of `aclocal'
+ also if some previously needed macro file has been removed.
+
+ - Rebuild rules now also work for a removed `subdir/Makefile.in' in
+ an otherwise up to date tree.
+
+ - The `color-tests' option causes colored test result output on terminals.
+
+ - The `parallel-tests' option enables a new test driver that allows for
+ parallel test execution, inter-test dependencies, lazy test execution
+ for unit-testing, re-testing only failed tests, and formatted result output
+ as RST (reStructuredText) and HTML. Enabling this option may require some
+ changes to your test suite setup; see the manual for details.
+
+ - The `silent-rules' option enables Linux kernel-style silent build output.
+ This option requires the widely supported but non-POSIX `make' feature
+ of recursive variable expansion, so do not use it if your package needs
+ to build with `make' implementations that do not support it.
+
+ To enable less verbose build output, the developer has to use the Automake
+ option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
+ macro. The user may then set the default verbosity by passing the
+ `--enable-silent-rules' option to `configure'. At `make' run time, this
+ default may be overridden using `make V=0' for less verbose, and `make V=1'
+ for backward-compatible verbose output.
+
+ - New prefix `notrans_' for manpages which should not be transformed
+ by --program-transform.
+
+ - New macro AM_COND_IF for conditional evaluation and conditional
+ config files.
+
+ - For AC_CONFIG_LINKS, if source and destination are equal, do not
+ remove the file in a non-VPATH build. Such setups work with Autoconf
+ 2.62 or newer.
+
+ - AM_MAINTAINER_MODE now allows for an optional argument specifying
+ the default setting.
+
+ - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
+ useful especially for multi-line values.
+
+ - Automake's early configure-time sanity check now diagnoses an
+ unsafe absolute source directory name and makes configure fail.
+
+ - The Automake macros and rules cope better with whitespace in the
+ current directory name, as long as the relative path to `configure'
+ does not contain whitespace. To this end, the values of `$(MISSING)'
+ and `$(install_sh)' may contain suitable quoting, and their expansion
+ might need `eval'uation if used outside of a makefile. These
+ undocumented variables may be used in several documented macros such
+ as $(AUTOCONF) or $(MAKEINFO).
+
+Bugs fixed in 1.11:
+
+* Long-standing bugs:
+
+ - Fix aix dependency tracking for libtool objects.
+
+ - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
+ unnecessary use of the `compile' script.
+
+ - For nobase_*_LTLIBRARIES with nonempty directory components, the
+ correct `-rpath' argument is used now.
+
+ - `config.status --file=Makefile depfiles' now also works with the
+ extra quoting used internally by Autoconf 2.62 and newer
+ (it used to work only without the `--file=' bit).
+
+ - The `missing' script works better with versioned tool names.
+
+ - Semantics for `missing help2man' have been revamped:
+
+ Previously, if `help2man' was not present, `missing help2man' would have
+ the following semantics: if some man page was out of date but present, then
+ a warning would be printed, but the exit status was 0. If the man page was
+ not present at all, then `missing' would create a replacement man page
+ containing an error message, and exit with a status of 2. This does not play
+ well with `make': the next run will see this particular man page as being up
+ to date, and will only error out on the next generated man page, if any;
+ repeat until all pages are done. This was not desirable.
+
+ These are the new semantics: if some man page is not present, and help2man
+ is not either, then `missing' will warn and generate the replacement page
+ containing the error message, but exit successfully. However, `make dist'
+ will ensure that no such bogus man pages are packaged into a tarball.
+
+ - Targets provided by automake behave better with `make -n', in that they
+ take care not to create files.
+
+ - `config.status Makefile... depfiles' works fine again in the presence of
+ disabled dependency tracking.
+
+ - The default no-op recursive rules for these targets also work with BSD make
+ now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
+
+ - `make distcheck' works also when both a directory and some file below it
+ have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
+
+ - Texinfo dvi, ps, pdf, and html output files are not removed upon
+ `make mostlyclean' any more; only the LaTeX by-products are.
+
+ - Renamed objects also work with the `subdir-objects' option and
+ source file languages which Automake does not know itself.
+
+ - `automake' now correctly complains about variable assignments which are
+ preceded by a comment, extend over multiple lines with backslash-escaped
+ newlines, and end in a comment sign. Previous versions would silently
+ and wrongly ignore such assignments completely.
+
+* Bugs introduced by 1.10:
+
+ - Fix output of dummy dependency files in presence of post-processed
+ Makefile.in's again, but also cope with long lines.
+
+ - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
+ that have been declared as programs in the same Makefile.
+ This is for consistency with the analogous change to TESTS in 1.10.
+
+ - Fix order of standard includes to again be `-I. -I$(srcdir)',
+ followed by directories containing config headers.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.10:
+
+* Version requirements:
+
+ - Autoconf 2.60 or greater is required.
+
+ - Perl 5.6 or greater is required.
+
+* Changes to aclocal:
+
+ - aclocal now also supports -Wmumble and -Wno-mumble options.
+
+ - `dirlist' entries (for the aclocal search path) may use shell
+ wildcards such as `*', `?', or `[...]'.
+
+ - aclocal supports an --install option that will cause system-wide
+ third-party macros to be installed in the local directory
+ specified with the first -I flag. This option also uses #serial
+ lines in M4 files to upgrade local macros.
+
+ The new aclocal options --dry-run and --diff help to review changes
+ before they are installed.
+
+ - aclocal now outputs an autoconf version check in aclocal.m4 in
+ projects using automake.
+
+ For a few years, automake and aclocal have been calling autoconf
+ (or its underlying engine autom4te) to accurately retrieve the
+ data they need from configure.ac and its siblings. Doing so can
+ only work if all autotools use the same version of autoconf. For
+ instance a Makefile.in generated by automake for one version of
+ autoconf may stop working if configure is regenerated with another
+ version of autoconf, and vice versa.
+
+ This new version check ensures that the whole build system has
+ been generated using the same autoconf version.
+
+* Support for new Autoconf macros:
+
+ - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
+
+ - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
+ $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
+ in different directories. However, only one instance of such a
+ library objects directory is supported.
+
+* Change to Libtool support:
+
+ - Libtool generic flags (those that go before the --mode=MODE option)
+ can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
+
+* Yacc and Lex changes:
+
+ - The rebuild rules for distributed Yacc and Lex output will avoid
+ overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
+ is not enabled.
+
+ - ylwrap is now always used for lex and yacc source files,
+ regardless of whether there is more than one source per directory.
+
+* Languages changes:
+
+ - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
+ AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
+ tracking, unlike non-preprocessed assembler (*.s).
+
+ - subdir-object mode works now with Assembler. Automake assumes
+ that the compiler understands `-c -o'.
+
+ - Preprocessed assembler (*.S) compilation now also honors
+ $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
+
+ - Improved support for Objective C:
+ - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
+ - A new section of the manual documents the support.
+
+ - New support for Unified Parallel C:
+ - AM_PROG_UPC looks for a UPC compiler.
+ - A new section of the manual documents the support.
+
+ - Per-target flags are now correctly handled in link rules.
+
+ For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
+ for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
+ preferred AM_CFLAGS over maude_CFLAGS while linking, and they
+ used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
+
+ The fix for compiler flags (i.e., using maude_CFLAGS instead of
+ AM_CFLAGS) should not hurt any package since that is how _CFLAGS
+ is expected to work (and actually works during compilation).
+
+ However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
+ "in addition to" breaks backward compatibility with older versions.
+ If your package used both variables, as in
+
+ AM_LDFLAGS = common flags
+ bin_PROGRAMS = a b c
+ a_LDFLAGS = more flags
+ ...
+
+ and assumed *_LDFLAGS would sum up, you should rewrite it as
+
+ AM_LDFLAGS = common flags
+ bin_PROGRAMS = a b c
+ a_LDFLAGS = $(AM_LDFLAGS) more flags
+ ...
+
+ This new behavior of *_LDFLAGS is more coherent with other
+ per-target variables, and the way *_LDFLAGS variables were
+ considered internally.
+
+* New installation targets:
+
+ - New targets mandated by GNU Coding Standards:
+ install-dvi
+ install-html
+ install-ps
+ install-pdf
+ By default they will only install Texinfo manuals.
+ You can customize them with *-local variants:
+ install-dvi-local
+ install-html-local
+ install-ps-local
+ install-pdf-local
+
+ - The undocumented recursive target `uninstall-info' no longer exists.
+ (`uninstall' is in charge of removing all possible documentation
+ flavors, including optional formats such as dvi, ps, or info even
+ when `no-installinfo' is used.)
+
+* Miscellaneous changes:
+
+ - Automake no longer complains if input files for AC_CONFIG_FILES
+ are specified using shell variables.
+
+ - clean, distribution, or rebuild rules are normally disabled for
+ inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
+ AC_CONFIG_LINK specified using shell variables. However, if these
+ variables are used as ${VAR}, and AC_SUBSTed, then Automake will
+ be able to output rules anyway.
+ (See the Automake documentation for AC_CONFIG_FILES.)
+
+ - $(EXEEXT) is automatically appended to filenames of TESTS
+ that have been declared as programs in the same Makefile.
+ This is mostly useful when some check_PROGRAMS are listed in TESTS.
+
+ - `-Wportability' has finally been turned on by default for `gnu' and
+ `gnits' strictness. This means, automake will complain about %-rules
+ or $(GNU Make functions) unless you switch to `foreign' strictness or
+ use `-Wno-portability'.
+
+ - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
+ $(MKDIR_P) instead of $(mkdir_p) to create directories. The
+ $(mkdir_p) variable is still defined (to the same value as
+ $(MKDIR_P)) but should be considered obsolete. If you are using
+ $(mkdir_p) in some of your rules, please plan to update them to
+ $(MKDIR_P) at some point.
+
+ - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
+ They still work in this release, but may be withdrawn in a future one.
+
+ - Inline compilation rules for gcc3-style dependency tracking are
+ more readable.
+
+ - Automake installs a "Hello World!" example package in $(docdir).
+ This example is used throughout the new "Autotools Introduction"
+ chapter of the manual.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.9:
+
+* Makefile.in bloat reduction:
+
+ - Inference rules are used to compile sources in subdirectories when
+ the `subdir-objects' option is used and no per-target flags are
+ used. This should reduce the size of some projects a lot, because
+ Automake used to output an explicit rule for each such object in
+ the past.
+
+ - Automake no longer outputs three rules (.o, .obj, .lo) for each
+ object that must be built with explicit rules. It just outputs
+ the rules required to build the kind of object considered: either
+ the two .o and .obj rules for usual objects, or the .lo rule for
+ libtool objects.
+
+* Change to Libtool support:
+
+ - Libtool tags are used with libtool versions that support them.
+ (I.e., with Libtool 1.5 or greater.)
+
+ - Automake is now able to handle setups where a libtool library is
+ conditionally installed in different directories, as in
+
+ if COND
+ lib_LTLIBRARIES = liba.la
+ else
+ pkglib_LTLIBRARIES = liba.la
+ endif
+ liba_la_SOURCES = ...
+
+* Changes to aclocal:
+
+ - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
+ really evaluated, before it decides to include them in aclocal.m4.
+ This solves nasty problems with conditional redefinitions of
+ Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
+ *.m4 files to be included in any project using these macros.
+ (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
+ most famous instance of this bug.)
+
+ - Do not complain about missing conditionally AC_REQUIREd macros
+ that are not actually used. In 1.8.x aclocal would correctly
+ determine which of these macros were really needed (and include
+ only these in the package); unfortunately it would also require
+ all of them to be present in order to run. This created
+ situations were aclocal would not work on a tarball distributing
+ all the macros it uses. For instance running aclocal on a project
+ containing only the subset of the Gettext macros in use by the
+ project did not work, because gettext conditionally requires other
+ macros.
+
+* Portability improvements:
+
+ - Tar format can be chosen with the new options tar-v7, tar-ustar, and
+ tar-pax. The new option filename-length-max=99 helps diagnosing
+ filenames that are too long for tar-v7. (PR/414)
+
+ - Variables augmented with `+=' are now automatically flattened (i.e.,
+ trailing backslashes removed) and then wrapped around 80 columns
+ (adding trailing backslashes). In previous versions, a long series
+ of
+ VAR += value1
+ VAR += value2
+ VAR += value3
+ ...
+ would result in a single-line definition of VAR that could possibly
+ exceed the maximum line length of some make implementations.
+
+ Non-augmented variables are still output as they are defined in
+ the Makefile.am.
+
+* Miscellaneous:
+
+ - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
+ Works the same as the old Fortran 77 implementation; just replace
+ F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
+ Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
+
+ - Support for conditional _LISP.
+
+ - Support for conditional -hook and -local rules (PR/428).
+
+ - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
+
+ - Automake will not write any Makefile.ins after the first error it
+ encounters. The previous Makefile.ins (if any) will be left in
+ place. (Warnings will not prevent output, but remember they can
+ be turned into errors with -Werror.)
+
+ - The restriction that SUBDIRS must contain direct children is gone.
+ Do not abuse.
+
+ - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
+ It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bugs fixed in 1.8.5:
+
+* Long-standing bugs:
+
+ - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
+ so that `make distclean' and `make maintainer-clean' can work.
+
+ - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
+
+ - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
+
+ - Polish diagnostic when no input file is found.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bugs fixed in 1.8.4:
+
+* Long-standing bugs:
+
+ - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
+ overridden by the user.
+
+ - Honor PATH_SEPARATOR in various places of the Automake package, for
+ the sake of OS/2.
+
+ - Adjust dependency tracking mode detection to ICC 8.0's new output.
+ (PR/416)
+
+ - Fix install-sh so it can install the `mv' binary... using `mv'.
+
+ - Fix tru64 dependency tracking for libtool objects.
+
+ - Work around Exuberant Ctags when creating a TAGS files in a directory
+ without files to scan but with subdirectories to include.
+
+* Bugs introduced by 1.8:
+
+ - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
+ not defined in the same conditions as the _LDADD that uses it.
+
+ - Do not warn when JAVAROOT is overridden, this is legitimate.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bugs fixed in 1.8.3:
+
+* Long-standing bugs:
+
+ - Quote filenames in installation rules, in case $DESTDIR, $prefix,
+ or any of the other *dir variables contain a space.
+
+ Please note that Automake does not and cannot support spaces in
+ filenames that are involved during the build. This change affects
+ only installation paths, so that `make install' does not bomb out
+ in packages configured with
+ ./configure --prefix '/c/Program Files'
+
+ - Fix the depfiles output so it works with GNU sed (<4.1) even when
+ POSIXLY_CORRECT is set.
+
+ - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
+ since Autoconf 2.54, which defines LIBOBJS itself.
+
+ - Fix a potential (but unlikely) race condition in parallel elisp
+ builds. (Introduced in 1.7.3.)
+
+ - Do not assume that users override _DEPENDENCIES in all conditions
+ where Automake will try to define them.
+
+ - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
+ Solaris 8's `mkdir -p' is not thread-safe and can break parallel
+ builds.
+
+ This fix also affects the $(mkdir_p) variable defined since
+ Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
+ mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
+
+ - Secure temporary directory creation in `make distcheck'. (PR/413)
+
+ - Do not generate two build rules for `parser.h' when the
+ parser appears in two different conditionals.
+
+ - Work around a Solaris 8 /bin/sh bug in the test for dependency
+ checking. Usually ./configure will not pick this shell; so this
+ fix only helps cases where the shell is forced to /bin/sh.
+
+* Bugs introduced by 1.8:
+
+ - In some situations (hand-written `m4_include's), aclocal would
+ call the `File::Spec->rel2abs' method, which was only introduced
+ in Perl 5.6. This new version reestablish support Perl 5.005.
+
+ It is likely that the next major Automake releases will require at
+ least Perl 5.6. Consider upgrading your development environment
+ if you are still using the five-year-old Perl 5.005.
+
+ - Automake would sometimes fail to define rules for targets listed
+ in variables defined in multiple conditions. For instance on
+ if C1
+ bin_PROGRAMS = a
+ else
+ bin_PROGRAMS = b
+ endif
+ it would define only the `a.$(OBJEXT): a.c' rule and omit the
+ `b.$(OBJEXT): b.c' rule.
+
+* New sections in manual:
+
+ - Third-Party Makefiles: how to interface third party Makefiles.
+ - Upgrading: upgrading packages to newer Automake versions.
+ - Multiple Outputs: handling tools that produce many outputs.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bug fixed in 1.8.2:
+
+* A (well known) portability bug slipped in the changes made to
+ install-sh in Automake 1.8.1. The broken install-sh would refuse to
+ install anything on Tru64.
+
+* Fix install rules for conditionally built python files. (This never
+ really worked.)
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bug fixed in 1.8.1:
+
+* Bugs introduced by 1.8:
+
+ - Fix Config.pm import error with old Perl versions (at least
+ 5.005_03). One symptom is that aclocal could not find its macro
+ directory.
+
+ - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
+ created by `make install' are always world readable, even if the
+ installer happens to have an overly restrictive umask (e.g. 077).
+ This was a mistake and has been reverted. There are at least two
+ reasons why we must not use `-m 0755':
+ - it causes special bits like SGID to be ignored,
+ - it may be too restrictive (some setups expect 775 directories).
+
+ - Fix aclocal to honor definitions located in files which have been
+ m4_included manually. aclocal 1.8 had been updated to check
+ m4_included files for new requirements, but forgot that these
+ m4_included files can also provide new definitions.
+
+ Note that if you have such a setup, we recommend you get rid of
+ it. In the past, there was a reason to m4_include files manually:
+ aclocal used to duplicate entire M4 files into aclocal.m4, even
+ files that were distributed. Some packages were therefore
+ m4_including the distributed file directly, and playing some
+ tricks to ensure aclocal would not copy that file to aclocal.m4,
+ in order to limit the amount of duplication. Since aclocal 1.8.x
+ will precisely output m4_includes for local M4 files, we recommend
+ that you clean up your setup, removing all manual m4_includes and
+ letting aclocal output them.
+
+ - Output detailed menus in the Info version if the Automake manual,
+ so that Emacs can locate the indexes.
+
+ - configure.ac and configure were listed twice in DIST_COMMON (an
+ internal variable where Automake lists configury files to
+ distribute). This was harmless, but unaesthetic.
+
+ - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
+ This was an issue only in the Automake package itself, not in
+ its output.
+
+ - Automake assumed that all AC_CONFIG_LINKS arguments had the form
+ DEST:SRC. This was wrong, as some packages do
+ AC_CONFIG_LINKS($computedlinks). This version no longer abort in
+ that situation.
+
+ - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
+ argument. This caused two kinds of failures:
+ - Rules installing data in a conditionally defined directory
+ failed when that directory was undefined. In this case no
+ argument was supplied.
+ - `make installdirs' failed, because several directories were
+ passed to $(mkdir_p). This was an issue only on platform
+ were $(mkdir_p) is implemented with `install-sh -d'.
+ $(mkdir_p) as been changed to accept 0 or more arguments, as
+ mkinstalldirs did.
+
+* Long-standing bugs:
+
+ - Fix an unexpected diagnostic occurring when users attempt
+ to override some internal variables that Automake appends to.
+
+ - aclocal now scans configure.ac for macro definitions (PR/319).
+
+ - Fix a portability issue with OSF1/Tru64 Make. If a directory
+ distributes files which are outside itself (this usually occurs
+ when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
+ from a parent package), then `make distcheck' fails due to an
+ optimization performed by OSF1/Tru64 Make in its VPATH handling.
+ (tests/subpkg2.test failure)
+
+ - Fix another portability issue with Sun and OSF1/Tru64 Make.
+ In a VPATH-build configuration, `make install' would install
+ nobase_ files to wrong locations.
+
+ - Fix a Perl `uninitialized value' diagnostic occurring when
+ automake complains that a Texinfo file does not have a
+ @setfilename statement.
+
+ - Erase config.status.lineno during `make distclean'. This file
+ can be created by config.status. Automake already knew about
+ configure.lineno, but forgot config.status.lineno.
+
+ - Distribute all files, even those which are built and installed
+ conditionally. This change affects files listed in conditionally
+ defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
+ as well as those listed in conditionally defined dist_*_DATA,
+ dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
+
+ - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
+ doesn't conform to POSIX.
+
+ - Normalize help strings for configure variables and options added
+ by Automake macros.
+
+* Anticipation:
+
+ - Check for python2.4 in AM_PATH_PYTHON.
+
+* Spurious failures in test suite:
+
+ - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
+ tests/ltconv.test: fix failures with CVS Libtool.
+ - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
+ - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
+ fix failures with old Texinfo versions.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New in 1.8:
+
+* Meta-News
+
+ - The NEWS file is more verbose.
+
+* Requirements
+
+ - Autoconf 2.58 or greater is required.
+
+* New features
+
+ - Default source file names in the absence of a _SOURCES declaration
+ are made by removing any target extension before appending `.c', so
+ to make the libtool module `foo.la' from `foo.c', you only need to
+ do this:
+
+ lib_LTLIBRARIES = foo.la
+ foo_la_LDFLAGS = -module
+
+ For backward compatibility, foo_la.c will be used instead of
+ foo.c if this file exists or is the explicit target of a rule.
+ However -Wobsolete will warn about this deprecated naming.
+
+ - AR's `cru' flags are now set in a global ARFLAGS variable instead
+ of being hard-coded in each $(AR) invocation, so they can be
+ substituted from configure.ac. This has been requested by people
+ dealing with non-POSIX ar implementations.
+
+ - New warning option: -Woverride. This will warn about any user
+ target or variable definitions which override Automake
+ definitions.
+
+ - Texinfo rules back up and restore info files when makeinfo fails.
+
+ - Texinfo rules now support the `html' target.
+ Running this requires Texinfo 4.0 or greater.
+
+ `html' is a new recursive target, so if your package mixes
+ hand-crafted `Makefile.in's with Automake-generated
+ `Makefile.in's, you should adjust the former to support (or
+ ignore) this target so that `make html' recurses successfully. If
+ you had a custom `html' rule in your `Makefile.am', it's better to
+ rename it as `html-local', otherwise your rule will override
+ Automake's new rule (you can check that by running `automake
+ -Woverride') and that will stop the recursion to subdirectories.
+
+ Last but not least, this `html' rule is declared PHONY, even when
+ overridden. Fortunately, it appears that few packages use a
+ non-PHONY `html' rule.
+
+ - Any file which is m4_included from configure.ac will appear as a
+ configure and Makefile.in dependency, and will be automatically
+ distributed.
+
+ - The rules for rebuilding Makefiles and Makefile.ins will now
+ rebuild all Makefiles and all Makefile.ins at once when one of
+ configure's dependencies has changed. This is considerably faster
+ than previous implementations, where config.status and automake
+ were run separately in each directory (this still happens when you
+ change a Makefile.am locally, without touching configure.ac or
+ friends). Doing this also solves a longstanding issue: these
+ rebuild rules failed to work when adding new directories to the
+ tree, forcing you to run automake manually.
+
+ - For similar reasons, the rules to rebuild configure,
+ config.status, and aclocal.m4 are now defined in all directories.
+ Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
+ CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
+ should better define them in all directories. This is easily done
+ using an AC_SUBST (make sure you prefix these dependencies with
+ $(top_srcdir) since this variable will appear at different
+ levels of the build tree).
+
+ - aclocal will now use `m4_include' instead of copying local m4
+ files into aclocal.m4. (Local m4 files are those you ship with
+ your project, other files will be copied as usual.)
+
+ Because m4_included files are automatically distributed, it means
+ for most projects there is no point in EXTRA_DISTing the list of
+ m4 files which are used. (You can probably get rid of
+ m4/Makefile.am if you had one.)
+
+ - aclocal will avoid touching aclocal.m4 when possible, so that
+ Autom4te's cache isn't needlessly invalidated. This behavior can
+ be switched off with the new `--force' option.
+
+ - aclocal now uses Autoconf's --trace to detect macros which are
+ actually used and will no longer include unused macros simply
+ because they where mentioned. This was often the case for macros
+ called conditionally.
+
+ - New options no-dist and no-dist-gzip.
+
+ - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
+ py-compile, and ylwrap, now all understand --version and --help.
+
+ - Automake will now recognize AC_CONFIG_LINKS so far as removing created
+ links as part of the distclean target and including source files in
+ distributions.
+
+ - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
+ argument. The latter can be used to override the default behavior
+ (which is to abort).
+
+ - Automake will exit with $? = 63 on version mismatch. (So does
+ Autoconf 2.58) missing knows this, and in this case it will
+ emulate the tools as if they were absent. Because older versions
+ of Automake and Autoconf did not use this exit code, this change
+ will only be useful in projects generated with future versions of
+ these tools.
+
+ - When using AC_CONFIG_FILES with multiple input files, Automake
+ generates the first ".in" input file for which a ".am" exists.
+ (Former versions would try to use only the first input file.)
+
+ - lisp_DATA is now allowed. If you are using the empty ELCFILES
+ idiom to disable byte-compilation of lisp_LISP files, it is
+ recommended that you switch to using lisp_DATA. Note that
+ this is not strictly equivalent: lisp_DATA will install elisp
+ files even if emacs is not installed, while *_LISP do not
+ install anything unless emacs is found.
+
+ - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
+ available. This selection is achieved through the Makefile
+ variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
+ `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
+ `$(install_sh) -m 0755 -d'.
+
+* Obsolete features
+
+ - Because `mkdir -p' is available on most platforms, and we can use
+ `install-sh -d' when it is not, the use of the mkinstalldirs
+ script is being phased out. `automake --add-missing' no longer
+ installs it, and if you remove mkinstalldirs from your package,
+ automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
+
+ Gettext 0.12.1 still requires mkinstalldirs. Fortunately
+ gettextize and autopoint will install it when needed. Automake
+ will continue to define the $(mkinstalldirs) and to distribute
+ mkinstalldirs when this script is in the source tree.
+
+ - AM_PROG_CC_STDC is now empty. The content of this macro was
+ merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
+ should adjust it to use $ac_cv_prog_cc_stdc instead. (This
+ renaming should be safe, even if you have to support several,
+ versions of Automake, because AC_PROG_CC defines this variable
+ since Autoconf 2.54.)
+
+ - Some users where using the undocumented ACLOCAL_M4_SOURCES
+ variable to override the aclocal.m4 dependencies computed
+ (inaccurately) by older versions of Automake. Because Automake
+ now tracks configure's m4 dependencies accurately (see m4_include
+ above), the use of ACLOCAL_M4_SOURCES should be considered
+ obsolete and will be flagged as such when running `automake
+ -Wobsolete'.
+
+* Bug fixes
+
+ - Defining programs conditionally using Automake conditionals no
+ longer leads to a combinatorial explosion. The following
+ construct used to be troublesome when used with dozens of
+ conditions.
+
+ bin_PROGRAMS = a
+ if COND1
+ bin_PROGRAMS += a1
+ endif
+ if COND2
+ bin_PROGRAMS += a2
+ endif
+ if COND3
+ bin_PROGRAMS += a3
+ endif
+ ...
+
+ Likewise for _SOURCES, _LDADD, and _LIBADD variables.
+
+ - Due to implementation constraints, previous versions of Automake
+ proscribed multiple conditional definitions of some variables
+ like bin_PROGRAMS:
+
+ if COND1
+ bin_PROGRAMS = a1
+ endif
+ if COND2
+ bin_PROGRAMS = a2
+ endif
+
+ All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
+ This restriction has been lifted, and these variables now
+ support multiple conditional definitions as do other variables.
+
+ - Cleanup the definitions of $(distdir) and $(top_distdir).
+ $(top_distdir) now points to the root of the distribution
+ directory created during `make dist', as it did in Automake 1.4,
+ not to the root of the build tree as it did in intervening
+ versions. Furthermore these two variables are now only defined in
+ the top level Makefile, and passed to sub-directories when running
+ `make dist'.
+
+ - The --no-force option now correctly checks the Makefile.in's
+ dependencies before deciding not to update it.
+
+ - Do not assume that make files are called Makefile in cleaning rules.
+
+ - Update .info files in the source tree, not in the build tree. This
+ is what the GNU Coding Standard recommend. Only Automake 1.7.x
+ used to update these files in the build tree (previous versions did
+ it in the source tree too), and it caused several problems, varying
+ from mere annoyance to portability issues.
+
+ - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
+ when --add-missing and --force-missing are used. For backward
+ compatibility --add-missing will continue to install COPYING (in
+ `gnu' strictness) when none of these three files exist, but this
+ use is deprecated: you should better choose a license yourself and
+ install it once for all in your source tree (and in your code
+ management system).
+
+ - Fix ylwrap so that it does not overwrite header files that haven't
+ changed, as the inline rule already does.
+
+ - User-defined rules override automake-defined rules for the same
+ targets, even when rules do not have commands. This is not new
+ (and was documented), however some of the automake-generated
+ rules have escaped this principle in former Automake versions.
+ Rules for the following targets are affected by this fix:
+
+ clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
+ info, info-am, install-data-am, install-exec-am, install-info,
+ install-info-am, install-man, installcheck-am, maintainer-clean,
+ maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
+ ps, ps-am, uninstall-am, uninstall-info, uninstall-man
+
+ Practically it means that an attempt to supplement the dependencies
+ of some target, as in
+
+ clean: my-clean-rule
+
+ will now *silently override* the automake definition of the
+ rule for this target. Running `automake -Woverride' will diagnose
+ all such overriding definitions.
+
+ It should be noted that almost all of these targets support a *-local
+ variant that is meant to supplement the automake-defined rule
+ (See node `Extending' in the manual). The above rule should
+ be rewritten as
+
+ clean-local: my-clean-rule
+
+ These *-local targets have been documented since at least
+ Automake 1.2, so you should not fear the change if you have
+ to support multiple automake versions.
+
+* Miscellaneous
+
+ - The Automake manual is now distributed under the terms of the GNU FDL.
+
+ - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
+
+ - core dumps are no longer removed by the cleaning rules. There are
+ at least three reasons for this:
+ 1. These files should not be created by any build step,
+ so their removal do not fit any of the cleaning rules.
+ Actually, they may be precious to the developer.
+ 2. If such file is created during a build, then it's clearly a
+ bug Automake should not hide. Not removing the file will
+ cause `make distcheck' to complain about its presence.
+ 3. Operating systems have different naming conventions for
+ core dump files. A core file on one system might be a
+ completely legitimate data file on another system.
+
+ - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
+ defined by Automake. This means that any definition in the
+ environment will be used, unless overridden in the Makefile.am or
+ on the command line. The old behavior, where these variables were
+ defined empty in each Makefile, can be obtained by AC_SUBSTing or
+ AC_ARG_VARing each variable from configure.ac.
+
+ - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
+ documented. (The is not a new feature, these variables have
+ been there since at least Automake 1.4.)
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Bugs fixed in 1.7.9:
+* Fix install-strip to work with nobase_ binaries.
+* Fix renaming of #line directives in ylwrap.
+* Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
+
+Bugs fixed in 1.7.8:
+* Remove spurious blank lines in cleaning rules introduced in 1.7.7.
+* Fix detection of Debian's install-info, broken since version 1.5.
+ (Debian bug #213524).
+* Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
+ This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
+
+Bugs fixed in 1.7.7:
+* The implementation of automake's --no-force option is unreliable,
+ so this option is ignored in this version. A real fix will appear in
+ Automake 1.8. (Debian Bug #206299)
+* AM_PATH_PYTHON: really check the whole list of interpreters if no
+ argument is given. (PR/399)
+* Do not warn about leading `_' in variable names, even with -Wportability.
+* Support user redefinitions of TEXINFO_TEX.
+* depcomp: support AIX Compiler version 6.
+* Fix missing rebuilds during `make dist' with BSD make.
+ (Could produce tarballs containing out-of-date files.)
+* Resurrect multilib support.
+* Noteworthy manual updates:
+ - Extending aclocal: how to write m4 macros that won't trigger warnings
+ with Automake 1.8.
+ - A Shared Library: Rewrite and split into subsections.
+
+Bugs fixed in 1.7.6:
+* Fix depcomp's icc mode for ICC 7.1.
+* Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
+* Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
+* Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
+* Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
+* Remove Latin-1 characters from elisp-comp.
+* Update the manual's @dircategory to match the Free Software Directory.
+
+Bugs fixed in 1.7.5:
+* Update install-sh's license to remove an advertising clause.
+ (Debian bug #191717)
+* Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
+ that caused invalid Makefile.ins to be generated.
+* Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
+* New FAQ entry: renamed objects.
+
+Bugs fixed in 1.7.4:
+* Tweak the TAGS rule to support Exuberant Ctags (in addition to
+ the Emacs implementation)
+* Fix output of aclocal.m4 dependencies in subdirectories.
+* Use `mv -f' instead of `mv' in fastdep rules.
+* Upgrade mdate-sh to work on OS/2.
+* Don't byte-compile elisp files when ELCFILES is set empty.
+ (this documented feature was broken by 1.7.3)
+* Diagnose trailing backslashes on last line of Makefile.am.
+* Diagnose whitespace following trailing backslashes.
+* Multiple tests are now correctly supported in DEJATOOL. (PR/388)
+* Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
+ Makefiles. (PR/389)
+* `make install' will build `BUILT_SOURCES' first.
+* Minor documentation fixes.
+
+Bugs fixed in 1.7.3:
+* Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
+* Query distutils for `pythondir' and `pythonexecdir', instead of
+ using an hardcoded path. This should allow builds on 64-bit
+ distributions that usually use lib64/ instead of lib/.
+* AM_PATH_PYTHON will also search for python2.3.
+* elisp files are now built all at once instead of one by one. Besides
+ incurring a speed-up, this is required to support interdependent elisp files.
+* Support for DJGPP:
+ - `make distcheck' will now work in `_inst/' and `_build' instead
+ of `=inst/' and `=build/'
+ - use `_dirstamp' when the file-system doesn't support `.dirstamp'
+ - install/uninstall `*.i[0-9][0-9]'-style info files
+ - more changes that affect only the Automake package (not its output)
+* Fix some incompatibilities with upcoming perl-5.10.
+* Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
+ PACKAGE and VERSION.
+* depcomp fixes:
+ - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
+ is troublesome with gcc and Solaris compilers. (PR/385)
+ - makedepend mode: work with Libtool. (PR/385 too)
+ - support for ICC.
+* better support for unusual gettext setups, such as multiple po/ directories
+ (PR/381):
+ - Flag missing po/ and intl/ directories as warnings, not errors.
+ - Disable these warnings if po/ does not exist.
+* Noteworthy manual updates:
+ - New FAQ chapter.
+ - Document how AC_CONFIG_AUX_DIR interacts with missing files.
+ (Debian Bug #39542)
+ - Document `AM_YFLAGS = -d'. (PR/382)
+
+Bugs fixed in 1.7.2:
+* Fix installation and uninstallation of Info files built in subdirectories.
+* Do not run `./configure --with-included-gettext' during `make distcheck'
+ if AM_GNU_GETTEXT([external]) is used.
+* Correctly uninstall renamed man pages.
+* Do not strip escaped newline in variables defined in one condition
+ and augmented in another condition.
+* Fix ansi2knr rules for LIBOBJS sources.
+* Clean all known Texinfo index files, not only those which appear to
+ be used, because we cannot know which indexes are used in included files.
+ (PR/375, Debian Bug #168671)
+* Honor only the first @setfilename seen in a Texinfo file.
+* Treat "required file X not found" diagnostics as errors (exit status 1).
+* Don't complain that a required file is not found when it is a Makefile
+ target. (PR/357)
+* Don't use single suffix inference rules when building `.info'-less
+ Info files, for the sake of Solaris make.
+* The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
+* Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
+* Warn about multiple inference rules when -Wportability is used. (PR/372)
+* Fix building of deansified files from subdirectories. (PR/370)
+* Add missing `fi' in the .c->.obj rules.
+* Improve install-sh to work even when names contain spaces or certain
+ (but not all) shell metachars.
+* Fix the following spurious failures in the test suite:
+ depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
+* Noteworthy manual updates:
+ - Augment the section about BUILT_SOURCES.
+ - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
+
+Bugs fixed in 1.7.1:
+* Honor `ansi2knr' for files built in subdirectories, or using per-targets
+ flags.
+* Aclocal should now recognize macro names containing parentheses, e.g.
+ AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
+* Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
+ (Debian Bug#153697)
+* Install Python files even if they were built. (PR/369)
+* Have stamp-vti dependent upon configure instead of configure.ac, as the
+ version might not be defined in the latter. (PR/358)
+* Reorder arguments passed to a couple of commands, so things works
+ when POSIXLY_CORRECT=1.
+* Fix a regex that can cause Perl to segfault on large input.
+ (Debian Bug#162583)
+* Fix distribution of packages that have some sources defined conditionally,
+ as in the `Conditional compilation using Automake conditionals' example
+ of the manual.
+* Fix spurious test suite failures on IRIX.
+* Don't report a required variable as undefined if it has been
+ defined conditionally for the "right" conditions.
+* Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
+ `make distcheck' fails.
+* Fix distribution of included Makefile fragment, so we don't create
+ spurious directories in the distribution. (PR/366)
+* Don't complain that a target lacks `.$(EXEEXT)' when it has it.
+
+New in 1.7:
+* Autoconf 2.54 is required.
+* `aclocal' and `automake' will no longer warn about obsolete
+ configure macros. This is done by `autoconf -Wobsolete'.
+* AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
+ AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
+ supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
+ and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
+ `configure.ac' for you.
+* Support for per-program and per-library `_CPPFLAGS'.
+* New `ctags' target (builds CTAGS files).
+* Support for -Wmumble and -Wno-mumble, where mumble is a warning category
+ (see `automake --help' or the manual for a list of them).
+* Honor the WARNINGS environment variable.
+* Omit the call to depcomp when using gcc3: call the compiler directly.
+* A new option, std-options, tests that programs support --help and --version
+ when `make installcheck' is run. This is enabled by --gnits.
+* Texinfo rules now support the `ps' and `pdf' targets.
+* Info files are now created in the build directory, not the source directory.
+* info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
+ or greater).
+* `make distcheck' will enforce DESTDIR support by attempting
+ a DESTDIR install.
+* `+=' can be used in conditionals, even if the augmented variable
+ was defined for another condition.
+* Makefile fragments (inserted with `include') are always distributed.
+* Use Autoconf's --trace interface to inspect configure.ac and get
+ a more accurate view of it.
+* Add support for extending aclocal's default macro search path
+ using a `dirlist' file within the aclocal directory.
+* automake --output-dir is deprecated.
+* The part of the distcheck target that checks whether uninstall actually
+ removes all installed files has been moved to a separate target,
+ distuninstallcheck, so it can be overridden easily.
+* Many bug fixes.
+
+New in 1.6.3:
+* Support for AM_INIT_GETTEXT([external])
+* Bug fixes, including:
+ - Fix Automake's own `make install' so it works even if `ln' doesn't.
+ - nobase_ programs and scripts honor --program-transform correctly.
+ - Erase configure.lineno during `make distclean'.
+ - Erase YACC and LEX outputs during `make maintainer-clean'.
+
+New in 1.6.2:
+* Many bug fixes, including:
+ - Requiring the current version works.
+ - Fix "$@" portability issues (for Zsh).
+ - Fix output of dummy dependency files in presence of post-processed
+ Makefile.in's.
+ - Don't compute dependencies in background to avoid races with libtool.
+ - Fix handling of _OBJECTS variables for targets sharing source variables.
+ - Check dependency mode for Java when AM_PROG_GCJ is used.
+
+New in 1.6.1:
+* automake --output-dir is deprecated
+* Many bug fixes, including:
+ - Don't choke on AM_LDFLAGS definitions.
+ - Clean libtool objects from subdirectories.
+ - Allow configure variables with reserved suffix and unknown prefix
+ (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
+ - Fix the definition of AUTOMAKE and ACLOCAL in configure.
+
+New in 1.6:
+* Autoconf 2.52 is required.
+* automake no longer run libtoolize.
+ This is the job of autoreconf (from GNU Autoconf).
+* `dist' generates all the archive flavors, as did `dist-all'.
+* `dist-gzip' generates the Gzip tar file only.
+* Combining Automake Makefile conditionals no longer lead to a combinatorial
+ explosion. Makefile.in's keep a reasonable size.
+* AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
+ are no longer shipped, since Autoconf 2.52 provides them (both as AM_
+ and AC_).
+* `#line' of Lex and Yacc files are properly set.
+* EXTRA_DIST can contain generated directories.
+* Support for dot-less extensions in suffix rules.
+* The part of the distcheck target that checks whether distclean actually
+ cleans all built files has been moved to a separate target, distcleancheck,
+ so it can be overridden easily.
+* `make distcheck' will pass additional options defined in
+ $(DISTCHECK_CONFIGURE_FLAGS) to configure.
+* Fixed CDPATH portability problems, in particular for MacOS X.
+* Fixed handling of nobase_ targets.
+* Fixed support of implicit rules leading to .lo objects.
+* Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
+* Added uninstall-hook target
+* `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
+ You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
+ (Note that "pkgname" is not "tarname", see the manual for details.)
+ It is also possible to pass a list of global Automake options as
+ first argument to this new form of AM_INIT_AUTOMAKE.
+* Compiler-based assembler is now called `CCAS'; people expected `AS'
+ to be a real assembler.
+* AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
+ AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
+* aclocal and automake are also installed with the version number
+ appended, and some of the install directory names have changed.
+ This lets you have multiple versions installed simultaneously.
+* Support for parsers and lexers in subdirectories.
+
+New in 1.5:
+* Support for `configure.ac'.
+* Support for `else COND', `endif COND' and negated conditions `!COND'.
+* `make dist-all' is much faster.
+* Allows '@' AC_SUBSTs in macro names.
+* Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
+* User-side dependency tracking. Developers no longer need GNU make
+* Python support
+* Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
+* Most files are correctly handled if they appear in subdirs
+ For instance, a _DATA file can appear in a subdir
+* GNU tar is no longer required for `make dist'
+* Added support for `dist_' and `nodist_' prefixes
+* Added support for `nobase_' prefix
+* Compiled Java support
+* Support for per-executable and per-library compilation flags
+* Many bug fixes
+
+New in 1.4:
+* Added support for the Fortran 77 programming language.
+* Re-indexed the Automake Texinfo manual.
+* Added `AM_FOOFLAGS' variable for each compiler invocation;
+ e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
+* Support for latest autoconf, including support for objext
+* Can now put `.' in SUBDIRS to control build order
+* `include' command and `+=' support for macro assignment
+* Dependency tracking no long susceptible to deleted header file problem
+* Maintainer mode now a conditional. @MAINT@ is now an anachronism.
+* Bug fixes
+
+New in 1.3:
+* Bug fixes
+* Better Cygwin32 support
+* Support for suffix rules with _SOURCES variables
+* New options `readme-alpha' and `check-news'; Gnits mode sets these
+* @LEXLIB@ no longer required when lex source seen
+ Lex support in `missing', and new lex macro. Update your missing script.
+* Built-in support for assembly
+* aclocal gives error if `AM_' macro not found
+* Passed YFLAGS, not YACCFLAGS, to yacc
+* AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
+* Dependencies computed as a side effect of compilation
+* Preliminary support for Java
+* DESTDIR support at "make install" time
+* Improved ansi2knr support; you must use the latest ansi2knr.c (included)
+
+New in 1.2:
+* Bug fixes
+* Better DejaGnu support
+* Added no-installinfo option
+* Added Emacs Lisp support
+* Added --no-force option
+* Included `aclocal' program
+* Automake will now generate rules to regenerate aclocal.m4, if appropriate
+* Now uses `AM_' macro names everywhere
+* ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
+ ansi2knr now works correctly on K&R sources
+* Better C++, yacc, lex support
+* Will compute _DEPENDENCIES variables automatically if not supplied
+* Will interpolate $(...) and ${...} when examining contents of a variable
+* .deps files now in build directory, not source directory; dependency
+ handling generally rewritten
+* DATA, MANS and BUILT_SOURCES no longer included in distribution
+* can now put config.h into a subdir
+* Added dist-all target
+* Support for install-info program (see texinfo 3.9)
+* Support for "yacc -d"
+* configure substitutions are automatically discovered and included
+ in generated Makefile.in
+* Special --cygnus mode
+* OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
+ when making distribution. Some dependencies are auto-ignored.
+* Changed how libraries are specified in _LIBRARIES variable
+* Full libtool support, from Gord Matzigkeit
+* No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
+ AM_CONFIG_HEADER handles it automatically
+* Texinfo output files no longer need .info extension
+* Added `missing' support
+* Cygwin32 support
+* Conditionals in Makefile.am, from Ian Taylor
+
+New in 1.0:
+* Bug fixes
+* distcheck target runs install and installcheck targets
+* Added preliminary support for DejaGnu.
+
+New in 0.33:
+* More bug fixes
+* More checking
+* More libtool fixes from Gord Matzigkeit; libtool support is still
+ preliminary however
+* Added support for jm_MAINTAINER_MODE
+* dist-zip support
+* New "distcheck" target
+
+New in 0.32:
+* Many bug fixes
+* mkinstalldirs and mdate-sh now appear in directory specified by
+ AC_CONFIG_AUX_DIR.
+* Removed DIST_SUBDIRS, DIST_OTHER
+* AC_ARG_PROGRAM only required when an actual program exists
+* dist-hook target now run before distribution packaged up; idea from
+ Dieter Baron. Other hooks exist, too.
+* Preliminary (unfinished) support for libtool
+* Added short option names.
+* Better "dist" support when gluing together multiple packages
+
+New in 0.31:
+* Bug fixes
+* Documentation updates (many from François Pinard)
+* strictness `normal' now renamed to `foreign'
+* Renamed --install-missing to --add-missing
+* Now handles AC_CONFIG_AUX_DIR
+* Now handles TESTS macro
+* DIST_OTHER renamed to EXTRA_DIST
+* DIST_SUBDIRS is deprecated
+* @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
+* Better error messages in many cases
+* Program names are canonicalized
+* Added "check" prefix; from Gord Matzigkeit
+
+New in 0.30:
+* Bug fixes
+* configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
+* Beginnings of a test suite
+* Automatically adds -I options for $(srcdir), ".", and path to config.h
+* Doesn't print anything when running
+* Beginnings of MAINT_CHARSET support
+* Can specify version in AUTOMAKE_OPTIONS
+* Most errors recognizable by Emacs' M-x next-error
+* Added --verbose option
+* All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
+ configure-generated names
+* Required macros now distributed in aclocal.m4
+* New documentation
+* --strictness=gnu is default
+
+New in 0.29:
+* Many bug fixes
+* More sophisticated configure.in scanning; now understands ALLOCA and
+ LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
+* TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
+* CONFIG_HEADER variable now obsolete
+* Can handle multiple Texinfo sources
+* Allow hierarchies deeper than 2. From Gord Matzigkeit.
+* HEADERS variable no longer needed; now can put .h files directly into
+ foo_SOURCES variable.
+* Automake automatically rebuilds files listed in AC_OUTPUT. The
+ corresponding ".in" files are included in the distribution.
+
+New in 0.28:
+* Added --gnu and --gnits options
+* More standards checking
+* Bug fixes
+* Cleaned up 'dist' targets
+* Added AUTOMAKE_OPTIONS variable and several options
+* Now scans configure.in to get some information (preliminary)
+
+New in 0.27:
+* Works with Perl 4 again
+
+New in 0.26:
+* Added --install-missing option.
+* Pretty-prints generated macros and rules
+* Comments in Makefile.am are placed more intelligently in Makefile.in
+* Generates .PHONY target
+* Rule or macro in Makefile.am now overrides contents of Automake file
+* Substantial cleanups from François Pinard
+
+New in 0.25:
+* Bug fixes.
+* Works with Perl 4 again.
+
+New in 0.24:
+* New uniform naming scheme.
+* --strictness option
+* Works with Perl 5
+* '.c' files corresponding to '.y' or '.l' files are automatically
+ distributed.
+* Many bug fixes and cleanups
+
+New in 0.23:
+* Allow objects to be conditionally included in libraries via lib_LIBADD.
+
+New in 0.22:
+* Bug fixes in 'clean' code.
+* Now generates 'installdirs' target.
+* man page installation reworked.
+* 'make dist' no longer re-creates all Makefile.in's.
+
+New in 0.21:
+* Reimplemented in Perl
+* Added --amdir option (for debugging)
+* Texinfo support cleaned up.
+* Automatic de-ANSI-fication cleaned up.
+* Cleaned up 'clean' targets.
+
+New in 0.20:
+* Automatic dependency tracking
+* More documentation
+* New variables DATA and PACKAGEDATA
+* SCRIPTS installed using $(INSTALL_SCRIPT)
+* No longer uses double-colon rules
+* Bug fixes
+* Changes in advance of internationalization
+
+-----
+
+Copyright (C) 1995-2021 Free Software Foundation, Inc.
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see .
diff --git a/openocd-win/openocd/distro-info/licenses/automake-1.16.5/NEWS-2.0 b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/NEWS-2.0
new file mode 100644
index 0000000..5c56aa6
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/NEWS-2.0
@@ -0,0 +1,97 @@
+This file (NEWS-2.0) lists several incompatibilities planned for a
+future Automake 2.0 release.
+
+However, the (few) current Automake maintainers have insufficient interest
+and energy to pursue the 2.0 release. We have not even reviewed all
+existing bugs. New maintainers are needed! For more information about
+helping with Automake development:
+https://lists.gnu.org/archive/html/automake/2021-03/msg00018.html
+
+Therefore, there is no ETA for Automake 2.0, but it is not likely to be
+any time soon. So moving these future issues to a separate file seemed
+warranted. For more info, see the ./PLANS/ directory.
+
+
+* WARNING: Future backward-incompatibilities!
+
+ - Makefile recipes generated by Automake 2.0 will expect to use an
+ 'rm' program that doesn't complain when called without any non-option
+ argument if the '-f' option is given (so that commands like "rm -f"
+ and "rm -rf" will act as a no-op, instead of raising usage errors).
+ This behavior of 'rm' is very widespread in the wild, and it will be
+ required in the next POSIX version:
+
+
+
+ Accordingly, AM_INIT_AUTOMAKE now expands some shell code that checks
+ that the default 'rm' program in PATH satisfies this requirement,
+ aborting the configure process if this is not the case. For the
+ moment, it's still possible to force the configuration process to
+ succeed even with a broken 'rm', but that will no longer be the case
+ for Automake 2.0.
+
+ - Automake 2.0 will require Autoconf 2.71 or later. Exact
+ dependencies are unknowable at ths time.
+
+ - Automake 2.0 will drop support for the long-deprecated 'configure.in'
+ name for the Autoconf input file. You are advised to start using the
+ recommended name 'configure.ac' instead, ASAP.
+
+ - The ACLOCAL_AMFLAGS special make variable will be fully deprecated in
+ Automake 2.0: it will raise warnings in the "obsolete" category (but
+ still no hard error of course, for compatibilities with the many, many
+ packages that still relies on that variable). You are advised to
+ start relying on the new Automake support for AC_CONFIG_MACRO_DIRS
+ instead (which was introduced in Automake 1.13).
+
+ - Automake 2.0 will remove support for automatic dependency tracking
+ with the SGI C/C++ compilers on IRIX. The SGI depmode has been
+ reported broken "in the wild" already, and we don't think investing
+ time in debugging and fixing is worthwhile, especially considering
+ that SGI has last updated those compilers in 2006, and retired
+ support for them in December 2013:
+
+
+ - Automake 2.0 will remove support for MS-DOS and Windows 95/98/ME
+ (support for them was offered by relying on the DJGPP project).
+ Note however that both Cygwin and MSYS/MinGW on modern Windows
+ versions will continue to be fully supported.
+
+ - Automake-provided scripts and makefile recipes might (finally!)
+ start assuming a POSIX shell in Automake 2.0. There still is no
+ certainty about this though: we'd first like to wait and see
+ whether future Autoconf versions will be enhanced to guarantee
+ that such a shell is always found and provided by the checks in
+ ./configure.
+
+ In 2020, config.guess was changed by its then-maintainer to require
+ $(...); the ensuing bug reports and maintenance hassle
+ (unfortunately the changes have not been reverted) are a convincing
+ argument that we should not require a POSIX shell until Solaris 10,
+ at least, is completely gone from the world.
+
+ - Starting from Automake 2.0, third-party m4 files located in the
+ system-wide aclocal directory, as well as in any directory listed
+ in the ACLOCAL_PATH environment variable, will take precedence
+ over "built-in" Automake macros. For example (assuming Automake
+ is installed in the /usr/local hierarchy), a definition of the
+ AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
+ should take precedence over the same-named automake-provided macro
+ (defined in '/usr/local/share/aclocal-2.0/vala.m4').
+
+-----
+
+Copyright (C) 1995-2021 Free Software Foundation, Inc.
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see .
diff --git a/openocd-win/openocd/distro-info/licenses/automake-1.16.5/README b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/README
new file mode 100644
index 0000000..c9d0a9e
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/README
@@ -0,0 +1,68 @@
+This is Automake, a Makefile generator. It aims to be portable and
+to conform to the GNU Coding Standards for Makefile variables and
+targets.
+
+See the INSTALL file for detailed information about how to configure
+and install Automake.
+
+Automake is a Perl script. The input files are called Makefile.am.
+The output files are called Makefile.in; they are intended for use
+with Autoconf. Automake requires certain things to be done in your
+configure.ac.
+
+Automake comes with extensive documentation; please refer to it for
+more details about its purpose, features, and usage patterns.
+
+This package also includes the "aclocal" program, whose purpose is
+to generate an 'aclocal.m4' based on the contents of 'configure.ac'.
+It is useful as an extensible, maintainable mechanism for augmenting
+autoconf. It is intended that other package authors will write m4
+macros which can be automatically used by aclocal. The documentation
+for aclocal is currently found in the Automake manual.
+
+Automake has a test suite. Use "make check" to run it. For more
+information, see the file t/README.
+
+Automake's home page:
+
+ https://www.gnu.org/software/automake/
+
+Automake has three mailing lists:
+
+ * automake@gnu.org
+ For general discussions of Automake and its interactions with other
+ configuration/portability tools like Autoconf or Libtool.
+
+ * bug-automake@gnu.org
+ Where to send bug reports and feature requests.
+
+ * automake-patches@gnu.org
+ Where to send patches, and discuss the automake development process
+ and the design of new features.
+
+To see the archives of these lists, or to (un)subscribe to them,
+refer to .
+
+New releases are announced to autotools-announce@gnu.org. If you want to
+be informed, subscribe to that list by following the instructions at
+.
+
+For any copyright year range specified as YYYY-ZZZZ in this package,
+the range specifies every single year in that closed interval.
+
+-----
+
+Copyright (C) 1994-2021 Free Software Foundation, Inc.
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see .
diff --git a/openocd-win/openocd/distro-info/licenses/automake-1.16.5/THANKS b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/THANKS
new file mode 100644
index 0000000..965f280
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/automake-1.16.5/THANKS
@@ -0,0 +1,462 @@
+Automake was originally written by David J. MacKenzie .
+It would not be what it is today without the invaluable help of these
+people:
+
+Adam J. Richter adam@yggdrasil.com
+Adam Mercer ramercer@gmail.com
+Adam Sampson ats@offog.org
+Adrian Bunk bunk@fs.tum.de
+Aharon Robbins arnold@skeeve.com
+Akim Demaille akim@gnu.org
+Alan Modra amodra@bigpond.net.au
+Alex Hornby alex@anvil.co.uk
+Alex Unleashed unledev@gmail.com
+Alexander Mai st002279@hrzpub.tu-darmstadt.de
+Alexander Martens alexander.martens@gtd.es
+Alexander V. Lukyanov lav@yars.free.net
+Alexander Turbov zaufi@sendmail.ru
+Alexandre Duret-Lutz duret_g@epita.fr
+Alexey Mahotkin alexm@hsys.msk.ru
+Alfred M. Szmidt ams@gnu.org
+Allison Karlitskaya allison.karlitskaya@redhat.com
+Andrea Urbani matfanjol@mail.com
+Andreas Bergmeier lcid-fire@gmx.net
+Andreas Buening andreas.buening@nexgo.de
+Andreas Köhler andi5.py@gmx.net
+Andreas Schwab schwab@suse.de
+Andrew Cagney cagney@tpgi.com.au
+Andrew Eikum aeikum@codeweavers.com
+Andrew Suffield asuffield@debian.org
+Andris Pavenis pavenis@lanet.lv
+Andy Wingo wingo@pobox.com
+Angus Leeming a.leeming@ic.ac.uk
+Anthony Green green@cygnus.com
+Antonio Diaz Diaz ant_diaz@teleline.es
+Arkadiusz Miskiewicz misiek@pld.ORG.PL
+Art Haas ahaas@neosoft.com
+Arto C. Nirkko anirkko@insel.ch
+Assar Westerlund assar@sics.se
+Axel Belinfante Axel.Belinfante@cs.utwente.nl
+Bas Wijnen shevek@fmf.nl
+Ben Pfaff blp@cs.standford.edu
+Benoit Sigoure tsuna@lrde.epita.fr
+Bernard Giroud bernard.giroud@creditlyonnais.ch
+Bernard Urban Bernard.Urban@meteo.fr
+Bernd Jendrissek berndfoobar@users.sourceforge.net
+Bert Wesarg bert.wesarg@googlemail.com
+Bill Currie bcurrie@tssc.co.nz
+Bill Davidson bill@kayhay.com
+Bill Fenner fenner@parc.xerox.com
+Bob Friesenhahn bfriesen@simple.dallas.tx.us
+Bob Proulx rwp@hprwp.fc.hp.com
+Bob Rossi bob@brasko.net
+Bobby Jack bobbykjack@yahoo.co.uk
+Boris Kolpackov boris@codesynthesis.com
+Braden N. McDaniel braden@endoframe.com
+Brandon Black blblack@gmail.com
+Brendan O'Dea bod@debian.org
+Brian Cameron Brian.Cameron@Sun.COM
+Brian Ford ford@vss.fsi.com
+Brian Gough bjg@network-theory.co.uk
+Brian Jones cbj@nortel.net
+Bruce Korb bkorb@gnu.org
+Bruno Haible haible@ilog.fr
+Carnë Draug carandraug+dev@gmail.com
+Carsten Lohrke carlo@gentoo.org
+Charles Wilson cwilson@ece.gatech.edu
+Chris Hoogendyk hoogendyk@bio.umass.edu
+Chris Pickett chris.pickett@mail.mcgill.ca
+Chris Provenzano proven@io.proven.org
+Christian Cornelssen ccorn@cs.tu-berlin.de
+Christina Gratorp christina.gratorp@gmail.com
+Claudio Fontana sick_soul@yahoo.it
+Clifford Wolf clifford@clifford.at
+Colin Watson cjwatson@ubuntu.com
+Colomban Wendling lists.ban@herbesfolles.org
+Dagobert Michelsen dam@opencsw.org
+Daiki Ueno ueno@unixuser.org
+Dalibor Topic robilad@kaffe.org
+danbp danpb@nospam.postmaster.co.uk
+Daniel Jacobowitz drow@false.org
+Daniel Kahn Gillmor dkg@fifthhorseman.net
+Daniel Richard G. skunk@iskunk.org
+Debarshi Ray rishi@gnu.org
+Dave Brolley brolley@redhat.com
+Dave Goodell goodell@mcs.anl.gov
+Dave Hart davehart@gmail.com
+Dave Korn dave.korn.cygwin@googlemail.com
+Dave Morrison dave@bnl.gov
+David A. Swierczek swiercze@mr.med.ge.com
+David A. Wheeler dwheeler@dwheeler.com
+David Byron dbyron@dbyron.com
+David Fang fang@csl.cornell.edu
+Davyd Madeley davyd@fugro-fsi.com.au
+David Pashley david@davidpashley.com
+David Wohlferd dw@limegreensocks.com
+David Zaroski cz253@cleveland.Freenet.Edu
+Dean Povey dpovey@wedgetail.com
+Dennis J. Linse Dennis.J.Linse@SAIC.com
+Dennis Schridde devurandom@gmx.net
+Derek R. Price derek.price@openavenue.com
+Diab Jerius djerius@cfa.harvard.edu
+Didier Cassirame faded@free.fr
+Diego Elio Pettenò flameeyes@flameeyes.eu
+Dieter Baron dillo@stieltjes.smc.univie.ac.at
+Dieter Jurzitza DJurzitza@harmanbecker.com
+Дилян Палаузов dilyan.palauzov@aegee.org
+Dirk Mueller josef.moellers@suse.com
+Dimitri Papadopoulos dimitri.papadopoulos@gmail.com
+Dmitry Mikhin dmitrym@acres.com.au
+Dmitry V. Levin ldv@altlinux.org
+Doug Evans devans@cygnus.com
+Duncan Gibson duncan@thermal.esa.int
+Dilyan Palauzov dilyan.palauzov@aegee.org
+Ed Hartnett ed@unidata.ucar.edu
+Eleftherios Gkioulekas lf@amath.washington.edu
+Elena A. Vengerova helen@oktetlabs.ru
+Elmar Hoffmann elho@elho.net
+Elrond Elrond@Wunder-Nett.org
+Enrico Scholz enrico.scholz@informatik.tu-chemnitz.de
+Erez Zadok ezk@cs.columbia.edu
+Eric Bavier bavier@cray.com
+Eric Blake eblake@redhat.com
+Eric Dorland eric@debian.org
+Eric Magnien emagnien@club-internet.fr
+Eric Siegerman erics_97@pobox.com
+Eric Sunshine sunshine@sunshineco.com
+Erick Branderhorst branderh@iaehv.nl
+Erik Lindahl E.Lindahl@chem.rug.nl
+Esben Haabendal Soerensen bart@kom.aau.dk
+Ezra Peisach epeisach@MED-XTAL.BU.EDU
+Fabian Alenius fabian.alenius@gmail.com
+Federico Simoncelli fsimonce@redhat.com
+Felix Salfelder felix@salfelder.org
+Felix Yan felixonmars@archlinux.org
+Flavien Astraud flav42@yahoo.fr
+Florian Briegel briegel@zone42.de
+Francesco Salvestrini salvestrini@gmail.com
+François Pinard pinard@iro.umontreal.ca
+Fred Fish fnf@ninemoons.com
+Ganesan Rajagopal rganesan@novell.com
+Garrett D'Amore garrett@qualcomm.com
+Garth Corral garthc@inktomi.com
+Gary V Vaughan gvaughan@oranda.demon.co.uk
+Gavin Smith gavinsmith0123@gmail.com
+Geoffrey Keating geoffk@apple.com
+Glenn Amerine glenn@pie.mhsc.org
+Gord Matzigkeit gord@gnu.ai.mit.edu
+Gordon Sadler gbsadler1@lcisp.com
+Graham Reitz grahamreitz@me.com
+Greg A. Woods woods@most.weird.com
+Greg Schafer gschafer@zip.com.au
+Guido Draheim guidod@gmx.de
+Guillermo Ontañón gontanonext@pandasoftware.es
+Gustavo Carneiro gjc@inescporto.pt
+Gwenole Beauchesne gbeauchesne@mandrakesoft.com
+H.J. Lu hjl@lucon.org
+H.Merijn Brand h.m.brand@hccnet.nl
+Hans Ulrich Niedermann hun@n-dimensional.de
+Hanspeter Niederstrasser fink@snaggledworks.com
+Harald Dunkel harald@CoWare.com
+Harlan Stenn Harlan.Stenn@pfcs.com
+He Li tippa000@yahoo.com
+Henrik Frystyk Nielsen frystyk@w3.org
+Hib Eris hib@hiberis.nl
+Hilko Bengen bengen@debian.org
+Holger Hans Peter Freyther holger@freyther.de
+Ian Lance Taylor ian@cygnus.com
+Ignacy Gawedzki i@lri.fr
+Илья Н. Голубев gin@mo.msk.ru
+Imacat imacat@mail.imacat.idv.tw
+Infirit infirit@gmail.com
+Inoue inoue@ainet.or.jp
+Jack Kelly jack@jackkelly.name
+Jacob Bachmeyer jcb@gnu.org
+James Amundson amundson@users.sourceforge.net
+James Bostock james.bostock@gmail.com
+James Henstridge james@daa.com.au
+James R. Van Zandt jrv@vanzandt.mv.com
+James Youngman jay@gnu.org
+Jan Engelhardt jengelh@medozas.de
+Janos Farkas chexum@shadow.banki.hu
+Jared Davis abiword@aiksaurus.com
+Jason DeVinney jasondevinney@gmail.com
+Jason Duell jcduell@lbl.gov
+Jason Molenda crash@cygnus.co.jp
+Javier Jardón jjardon@gnome.org
+Jeff Bailey Jbailey@phn.ca
+Jeff A. Daily jeff.daily@pnl.gov
+Jeff Garzik jgarzik@pobox.com
+Jeff Squyres jsquyres@lam-mpi.org
+Jens Elkner elkner@imsgroup.de
+Jens Krüger jens_krueger@physik.tu-muenchen.de
+Jens Petersen petersen@redhat.com
+Jeremy Nimmer jwnimmer@alum.mit.edu
+Jerome Lovy jlovy@multimania.com
+Jerome Santini santini@chambord.univ-orleans.fr
+Jesse Chisholm jesse@ctc.volant.org
+Jim Meyering meyering@na-net.ornl.gov
+Joakim Tjernlund Joakim.Tjernlund@transmode.se
+Jochen Kuepper jochen@uni-duesseldorf.de
+Joel N. Weber II nemo@koa.iolani.honolulu.hi.us
+Joerg-Martin Schwarz jms@jms.prima.ruhr.de
+Johan Dahlin jdahlin@async.com.br
+Johan Danielsson joda@pdc.kth.se
+Johan Kristensen johankristensen@gmail.com
+Johannes Nicolai johannes.nicolai@student.hpi.uni-potsdam.de
+John Calcote john.calcote@gmail.com
+John F Trudeau JohnTrudeau@firsthealth.com
+John Pierce hawkfan@pyrotechnics.com
+John Ratliff autoconf@technoplaza.net
+John R. Cary cary@txcorp.com
+John W. Coomes jcoomes@eng.Sun.COM
+Jonathan L Peyton jonathan.l.peyton@intel.com
+Jonathan Nieder jrnieder@gmail.com
+Joseph S. Myers joseph@codesourcery.com
+Josh MacDonald jmacd@cs.berkeley.edu
+Joshua Cowan jcowan@jcowan.reslife.okstate.edu
+Joshua Root jmr@macports.org
+js pendry js.pendry@msdw.com
+Juergen A. Erhard jae@laden.ilk.de
+Juergen Keil jk@tools.de
+Juergen Leising juergen.leising@gmx.de
+Julien Sopena julien.sopena@lip6.fr
+Jürg Billeter j@bitron.ch
+Karl Berry kb@cs.umb.edu
+Karl Heuer kwzh@gnu.org
+Kelley Cook kcook@gcc.gnu.org
+Kent Boortz kent@mysql.com
+Kevin Dalley kevin@aimnet.com
+Kevin P. Fleming. kpfleming@cox.net
+Kevin Ryde user42@zip.com.au
+Kevin Street street@iname.com
+Klaus Reichl Klaus.Reichl@alcatel.at
+Krzysztof Żelechowski giecrilj@stegny.2a.pl
+L. Peter Deutsch ghost@aladdin.com
+Ladislav Strojil Ladislav.Strojil@seznam.cz
+Larry Daniel larry@larrybrucedaniel.com
+Larry Jones larry.jones@sdrc.com
+Lars Hecking lhecking@nmrc.ucc.ie
+Lars J. Aas larsa@sim.no
+Laurent Morichetti laurentm@cup.hp.com
+Leo Davis ldavis@fonix.com
+Leonardo Boiko leoboiko@conectiva.com.br
+Libor Bukata libor.bukata@oracle.com
+Loulou Pouchet loulou@lrde.epita.fr
+Ludovic Courtès ludo@gnu.org
+Lukas Fleischer lfleischer@lfos.de
+Luo Yi luoyi.ly@gmail.com
+Maciej Stachowiak mstachow@mit.edu
+Maciej W. Rozycki macro@ds2.pg.gda.pl
+Manu Rouat emmanuel.rouat@wanadoo.fr
+Marc Herbert marc.herbert@intel.com
+Marcus Brinkmann Marcus.Brinkmann@ruhr-uni-bochum.de
+Marcus G. Daniels mgd@ute.santafe.edu
+Marius Vollmer mvo@zagadka.ping.de
+Marc-Antoine Perennou Marc-Antoine@Perennou.com
+Mark D. Baushke mdb@cvshome.org
+Mark Eichin eichin@cygnus.com
+Mark Elbrecht snowball3@bigfoot.com
+Mark Galassi rosalia@nis.lanl.gov
+Mark Mitchell mark@codesourcery.com
+Mark Phillips msp@nortelnetworks.com
+Markku Rossi mtr@ngs.fi
+Markus Duft Markus.Duft@salomon.at
+Markus F.X.J. Oberhumer k3040e4@wildsau.idv-edu.uni-linz.ac.at
+Martin Bravenboer martin@cs.uu.nl
+Martin Frydl martin@idoox.com
+Martin Waitz tali@admingilde.org
+Mathias Doreille doreille@smr.ch
+Mathias Froehlich M.Froehlich@science-computing.de
+Mathias Hasselmann mathias.hasselmann@gmx.de
+Matt Burgess matthew@linuxfromscratch.org
+Matt Leach mleach@cygnus.com
+Matthew D. Langston langston@SLAC.Stanford.EDU
+Matthias Andree matthias.andree@gmx.de
+Matthias Clasen clasen@mathematik.uni-freiburg.de
+Matthias Klose doko@ubuntu.com
+Matthieu Baerts matttbe@glx-dock.org
+Max Horn max@quendi.de
+Maxim Sinev good@goods.ru
+Maynard Johnson maynardj@us.ibm.com
+Merijn de Jonge M.de.Jonge@cwi.nl
+Michael Brantley Michael-Brantley@deshaw.com
+Michael Daniels mdaniels@rim.com
+Michael Hofmann mhofma@googlemail.com
+Michael Ploujnikov ploujj@gmail.com
+Michael Zucchi notzed@gmail.com
+Michel de Ruiter mdruiter@cs.vu.nl
+Mike Castle dalgoda@ix.netcom.com
+Mike Frysinger vapier@gentoo.org
+Mike Nolta mrnolta@princeton.edu
+Miles Bader miles@ccs.mt.nec.co.jp
+Miloslav Trmac trmac@popelka.ms.mff.cuni.cz
+Miodrag Vallat miodrag@ifrance.com
+Mirko Streckenbach strecken@infosun.fmi.uni-passau.de
+Miro Hroncok miro@hroncok.cz
+Miroslaw Dobrzanski-Neumann mne@mosaic-ag.com
+Morten Eriksen mortene@sim.no
+Motoyuki Kasahara m-kasahr@sra.co.jp
+Nathanael Nerode neroden@twcny.rr.com
+Nelson H. F. Beebe beebe@math.utah.edu
+Nicholas Wourms nwourms@netscape.net
+Nick Bowler nbowler@elliptictech.com
+Nick Brown brownn@brocade.com
+Nick Gasson nick@nickg.me.uk
+Nicola Fontana ntd@entidi.it
+Nicolas Joly njoly@pasteur.fr
+Nicolas Thiery nthiery@Icare.mines.edu
+NightStrike nightstrike@gmail.com
+Nik A. Melchior nam1@cse.wustl.edu
+Nikolai Weibull now@bitwi.se
+NISHIDA Keisuke knishida@nn.iij4u.or.jp
+Noah Friedman friedman@gnu.ai.mit.edu
+Norman Gray norman@astro.gla.ac.uk
+Nyul Laszlo nyul@sol.cc.u-szeged.hu
+OKUJI Yoshinori okuji@kuicr.kyoto-u.ac.jp
+Olivier Fourdan fourdan@cena.fr
+Olivier Louchart-Fletcher olivier@zipworld.com.au
+Olly Betts olly@muscat.co.uk
+Oren Ben-Kiki oren@ben-kiki.org
+Owen Taylor otaylor@redhat.com
+Panther Martin mrsmiley98@lycos.com
+Patrick Welche prlw1@newn.cam.ac.uk
+Patrik Weiskircher me@justp.at
+Paul Berrevoets paul@swi.com
+Paul D. Smith psmith@BayNetworks.COM
+Paul Eggert eggert@twinsun.com
+Paul Jarc prj@po.cwru.edu
+Paul Lunau temp@lunau.me.uk
+Paul Martinolich martinol@datasync.com
+Paul Osmialowski pawel.osmialowski@arm.com
+Paul Thomas PTHOMAS@novell.com
+Pavel Raiskup praiskup@redhat.com
+Pavel Roskin pavel_roskin@geocities.com
+Pavel Sanda ps@twin.jikos.cz
+Per Bothner bothner@cygnus.com
+Per Cederqvist ceder@lysator.liu.se
+Per Oyvind Hvidsten poeh@enter.vg
+Peter Breitenlohner peb@mppmu.mpg.de
+Peter Eisentraut peter_e@gmx.net
+Peter Gavin pgavin@debaser.kicks-ass.org
+Peter Hutterer peter.hutterer@who-t.net
+Peter Johansson trojkan@gmail.com
+Peter Mattis petm@scam.XCF.Berkeley.EDU
+Peter Muir iyhi@yahoo.com
+Peter O'Gorman peter@pogma.com
+Peter Rosin peda@lysator.liu.se
+Peter Seiderer seiderer123@ciselant.de
+Petr Hracek phracek@redhat.com
+Petter Reinholdtsen pere@hungry.com
+Petteri Räty betelgeuse@gentoo.org
+Phil Edwards phil@jaj.com
+Phil Nelson phil@cs.wwu.edu
+Philip Fong pwlfong@users.sourceforge.net
+Philip S Tellis philip@ncst.ernet.in
+Philipp A. Hartmann philipp.hartmann@offis.de
+Пухальский Юрий Андреевич pooh@cryptopro.ru
+Quentin Glidic sardemff7+gnu@sardemff7.net
+Rainer Orth ro@techfak.uni-bielefeld.de
+Rafael Laboissiere laboissiere@psy.mpg.de
+Rainer Tammer tammer@tammer.net
+Raja R Harinath harinath@cs.umn.edu
+Ralf Corsepius ralf.corsepius@gmail.com
+Ralf Menzel menzel@ls6.cs.uni-dortmund.de
+Ralf Wildenhues Ralf.Wildenhues@gmx.de
+Ralph Schleicher rs@purple.UL.BaWue.DE
+Ramón García Fernández ramon@jl1.quim.ucm.es
+Reuben Thomas rrt@sc3d.org
+Rich Wales richw@webcom.com
+Richard Boulton richard@tartarus.org
+Richard Dawe rich@phekda.freeserve.co.uk
+Richard W.M. Jones rjones@redhat.com
+Rob Savoye rob@cygnus.com
+Robert Bihlmeyer robbe@orcus.priv.at
+Robert Boehne rboehne@ricardo-us.com
+Robert Collins robert.collins@itdomain.com.au
+Robert Menteer reetnem@mac.com
+Robert Swafford robert.swafford@l-3com.com
+Robert Wanamaker rlw@nycap.rr.com
+Roberto Bagnara bagnara@cs.unipr.it
+Roman Fietze roman.fietze@telemotive.de
+Ronald Copley ronald.copley@gmail.com
+Ronald Landheer ronald@landheer.com
+Roumen Petrov bugtrack@roumenpetrov.info
+Russ Allbery rra@stanford.edu
+Rusty Ballinger rusty@rlyeh.engr.sgi.com
+Ryan Lortie desrt@desrt.ca
+Ryan T. Sammartino ryants@shaw.ca
+Sam Hocevar sam@zoy.org
+Sam Sirlin sam@kalessin.jpl.nasa.gov
+Sam Steingold sds@gnu.org
+Samuel Tardieu sam@rfc1149.net
+Samy Mahmoudi samy.mahmoudi@gmail.com
+Sander Niemeijer niemeijer@science-and-technology.nl
+Santiago Vila sanvila@unex.es
+Scott James Remnant scott@netsplit.com
+Sébastien Wilmet swilmet@gnome.org
+Sergey Poznyakoff gray@gnu.org.ua
+Sergey Vlasov vsu@mivlgu.murom.ru
+Seth Alves alves@hungry.com
+Shannon L. Brown slbrow@sandia.gov
+Shuhei Amakawa sa264@cam.ac.uk
+Shigio Yamaguchi shigio@tamacom.com
+Simon Josefsson jas@extundo.com
+Simon Richter sjr@debian.org
+Stefan Nordhausen nordhaus@informatik.hu-berlin.de
+Stefano Lattarini stefano.lattarini@gmail.com
+Stepan Kasal kasal@math.cas.cz
+Steve M. Robbins steve@nyongwa.montreal.qc.ca
+Steve Goetze goetze@dovetail.com
+Steven Drake sbd@NetBSD.org
+Steven G. Johnson stevenj@alum.mit.edu
+Sven Verdoolaege skimo@kotnet.org
+Tamara L. Dahlgren dahlgren1@llnl.gov
+Tatu Ylonen ylo@ssh.fi
+Teun Burgers burgers@ecn.nl
+The Crimson Binome steve@nyongwa.montreal.qc.ca
+Theodoros V. Kalamatianos thkala@gmail.com
+Thien-Thi Nguyen ttn@glug.org
+Thomas Fitzsimmons fitzsim@redhat.com
+Thomas Gagne tgagne@ix.netcom.com
+Thomas Jahns jahns@dkrz.de
+Thomas Klausner tk@giga.or.at
+Thomas Morgan tmorgan@pobox.com
+Thomas Schwinge tschwinge@gnu.org
+Thomas Tanner tanner@ffii.org
+Toralf Förster toralf.foerster@gmx.de
+Tim Goodwin tjg@star.le.ac.uk
+Tim Landscheidt tim@tim-landscheidt.de
+Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu
+Tim Retout diocles@debian.org
+Tim Rice tim@multitalents.net
+Tim Van Holder tim.van.holder@pandora.be
+Tobias Hansen thansen@debian.org
+Toshio Kuratomi toshio@tiki-lounge.com
+Tom Epperly tepperly@llnl.gov
+Tom Rini tom_rini@mentor.com
+Ulrich Drepper drepper@gnu.ai.mit.edu
+Ulrich Eckhardt eckhardt@satorlaser.com
+Václav Haisman V.Haisman@sh.cvut.cz
+Václav Zeman vhaisman@gmail.com
+Vadim Zeitlin Vadim.zeitlin@dptmaths.ens-cachan.fr
+Vasyl Khalak basiliomail@gmail.com
+Vincent Lefevre vincent@vinc17.org
+Vladimir Serbinenko phcoder@gmail.com
+Volker Boerchers vboerchers@tecon.de
+Weiller Ronfini weillerronfini@yahoo.com.br
+Werner John john@oswf.de
+Werner Koch wk@isil.d.shuttle.de
+Werner Lemberg wl@gnu.org
+William Pursell bill.pursell@gmail.com
+William S Fulton wsf@fultondesigns.co.uk
+Yann Droneaud ydroneaud@meuh.eu.org
+Younes Younes younes@cs.tu-berlin.de
+Zack Weinberg zackw@panix.com
+Zbigniew Jędrzejewski-Szmek zbyszek@in.waw.pl
+Zoltan Rado z.rado@chello.hu
+
+;; Local Variables:
+;; mode: text
+;; coding: utf-8
+;; End:
diff --git a/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/AUTHORS.txt b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/AUTHORS.txt
new file mode 100644
index 0000000..7193d71
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/AUTHORS.txt
@@ -0,0 +1,18 @@
+
+HIDAPI Authors:
+
+Alan Ott :
+ Original Author and Maintainer
+ Linux, Windows, and Mac implementations
+
+Ludovic Rousseau :
+ Formatting for Doxygen documentation
+ Bug fixes
+ Correctness fixes
+
+libusb/hidapi Team:
+ Development/maintainance since June 4th 2019
+
+For a comprehensive list of contributions, see the commit list at github:
+ https://github.com/libusb/hidapi/graphs/contributors
+
diff --git a/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-bsd.txt b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-bsd.txt
new file mode 100644
index 0000000..538cdf9
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-bsd.txt
@@ -0,0 +1,26 @@
+Copyright (c) 2010, Alan Ott, Signal 11 Software
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ * Neither the name of Signal 11 Software nor the names of its
+ contributors may be used to endorse or promote products derived from
+ this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
diff --git a/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-gpl3.txt b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-gpl3.txt
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-gpl3.txt
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ Copyright (C)
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+.
diff --git a/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-orig.txt b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-orig.txt
new file mode 100644
index 0000000..e3f3380
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE-orig.txt
@@ -0,0 +1,9 @@
+ HIDAPI - Multi-Platform library for
+ communication with HID devices.
+
+ Copyright 2009, Alan Ott, Signal 11 Software.
+ All Rights Reserved.
+
+ This software may be used by anyone for any reason so
+ long as the copyright notice in the source files
+ remains intact.
diff --git a/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE.txt b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE.txt
new file mode 100644
index 0000000..e1676d4
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/LICENSE.txt
@@ -0,0 +1,13 @@
+HIDAPI can be used under one of three licenses.
+
+1. The GNU General Public License, version 3.0, in LICENSE-gpl3.txt
+2. A BSD-Style License, in LICENSE-bsd.txt.
+3. The more liberal original HIDAPI license. LICENSE-orig.txt
+
+The license chosen is at the discretion of the user of HIDAPI. For example:
+1. An author of GPL software would likely use HIDAPI under the terms of the
+GPL.
+
+2. An author of commercial closed-source software would likely use HIDAPI
+under the terms of the BSD-style license or the original HIDAPI license.
+
diff --git a/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/README.md b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/README.md
new file mode 100644
index 0000000..257b9f3
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/hidapi-hidapi-0.14.0/README.md
@@ -0,0 +1,196 @@
+## HIDAPI library for Windows, Linux, FreeBSD and macOS
+
+| CI instance | Status |
+|----------------------|--------|
+| `Linux/macOS/Windows (master)` | [](https://github.com/libusb/hidapi/actions/workflows/builds.yml?query=branch%3Amaster) |
+| `Windows (master)` | [](https://ci.appveyor.com/project/libusb/hidapi/branch/master) |
+| `BSD, last build (branch/PR)` | [](https://builds.sr.ht/~z3ntu/hidapi) |
+| `Coverity Scan (last)` |  |
+
+HIDAPI is a multi-platform library which allows an application to interface
+with USB and Bluetooth HID-Class devices on Windows, Linux, FreeBSD, and macOS.
+HIDAPI can be either built as a shared library (`.so`, `.dll` or `.dylib`) or
+can be embedded directly into a target application by adding a _single source_
+file (per platform) and a single header.
+See [remarks](BUILD.md#embedding-hidapi-directly-into-your-source-tree) on embedding _directly_ into your build system.
+
+HIDAPI library was originally developed by Alan Ott ([signal11](https://github.com/signal11)).
+
+It was moved to [libusb/hidapi](https://github.com/libusb/hidapi) on June 4th, 2019, in order to merge important bugfixes and continue development of the library.
+
+## Table of Contents
+
+* [About](#about)
+ * [Test GUI](#test-gui)
+ * [Console Test App](#console-test-app)
+* [What Does the API Look Like?](#what-does-the-api-look-like)
+* [License](#license)
+* [Installing HIDAPI](#installing-hidapi)
+* [Build from Source](#build-from-source)
+
+
+## About
+
+### HIDAPI has four back-ends:
+* Windows (using `hid.dll`)
+* Linux/hidraw (using the Kernel's hidraw driver)
+* libusb (using libusb-1.0 - Linux/BSD/other UNIX-like systems)
+* macOS (using IOHidManager)
+
+On Linux, either the hidraw or the libusb back-end can be used. There are
+tradeoffs, and the functionality supported is slightly different. Both are
+built by default. It is up to the application linking to hidapi to choose
+the backend at link time by linking to either `libhidapi-libusb` or
+`libhidapi-hidraw`.
+
+Note that you will need to install an udev rule file with your application
+for unprivileged users to be able to access HID devices with hidapi. Refer
+to the [69-hid.rules](udev/69-hid.rules) file in the `udev` directory
+for an example.
+
+#### __Linux/hidraw__ (`linux/hid.c`):
+
+This back-end uses the hidraw interface in the Linux kernel, and supports
+both USB and Bluetooth HID devices. It requires kernel version at least 2.6.39
+to build. In addition, it will only communicate with devices which have hidraw
+nodes associated with them.
+Keyboards, mice, and some other devices which are blacklisted from having
+hidraw nodes will not work. Fortunately, for nearly all the uses of hidraw,
+this is not a problem.
+
+#### __Linux/FreeBSD/libusb__ (`libusb/hid.c`):
+
+This back-end uses libusb-1.0 to communicate directly to a USB device. This
+back-end will of course not work with Bluetooth devices.
+
+### Test GUI
+
+HIDAPI also comes with a Test GUI. The Test GUI is cross-platform and uses
+Fox Toolkit . It will build on every platform
+which HIDAPI supports. Since it relies on a 3rd party library, building it
+is optional but it is useful when debugging hardware.
+
+NOTE: Test GUI based on Fox Toolkit is not actively developed nor supported
+by HIDAPI team. It is kept as a historical artifact. It may even work sometime
+or on some platforms, but it is not going to get any new features or bugfixes.
+
+Instructions for installing Fox-Toolkit on each platform is not provided.
+Make sure to use Fox-Toolkit v1.6 if you choose to use it.
+
+### Console Test App
+
+If you want to play around with your HID device before starting
+any development with HIDAPI and using a GUI app is not an option for you, you may try [`hidapitester`](https://github.com/todbot/hidapitester).
+
+This app has a console interface for most of the features supported
+by HIDAPI library.
+
+## What Does the API Look Like?
+
+The API provides the most commonly used HID functions including sending
+and receiving of input, output, and feature reports. The sample program,
+which communicates with a heavily hacked up version of the Microchip USB
+Generic HID sample looks like this (with error checking removed for
+simplicity):
+
+**Warning: Only run the code you understand, and only when it conforms to the
+device spec. Writing data (`hid_write`) at random to your HID devices can break them.**
+
+```c
+#include // printf
+#include // wchar_t
+
+#include
+
+#define MAX_STR 255
+
+int main(int argc, char* argv[])
+{
+ int res;
+ unsigned char buf[65];
+ wchar_t wstr[MAX_STR];
+ hid_device *handle;
+ int i;
+
+ // Initialize the hidapi library
+ res = hid_init();
+
+ // Open the device using the VID, PID,
+ // and optionally the Serial number.
+ handle = hid_open(0x4d8, 0x3f, NULL);
+ if (!handle) {
+ printf("Unable to open device\n");
+ hid_exit();
+ return 1;
+ }
+
+ // Read the Manufacturer String
+ res = hid_get_manufacturer_string(handle, wstr, MAX_STR);
+ printf("Manufacturer String: %ls\n", wstr);
+
+ // Read the Product String
+ res = hid_get_product_string(handle, wstr, MAX_STR);
+ printf("Product String: %ls\n", wstr);
+
+ // Read the Serial Number String
+ res = hid_get_serial_number_string(handle, wstr, MAX_STR);
+ printf("Serial Number String: (%d) %ls\n", wstr[0], wstr);
+
+ // Read Indexed String 1
+ res = hid_get_indexed_string(handle, 1, wstr, MAX_STR);
+ printf("Indexed String 1: %ls\n", wstr);
+
+ // Toggle LED (cmd 0x80). The first byte is the report number (0x0).
+ buf[0] = 0x0;
+ buf[1] = 0x80;
+ res = hid_write(handle, buf, 65);
+
+ // Request state (cmd 0x81). The first byte is the report number (0x0).
+ buf[0] = 0x0;
+ buf[1] = 0x81;
+ res = hid_write(handle, buf, 65);
+
+ // Read requested state
+ res = hid_read(handle, buf, 65);
+
+ // Print out the returned buffer.
+ for (i = 0; i < 4; i++)
+ printf("buf[%d]: %d\n", i, buf[i]);
+
+ // Close the device
+ hid_close(handle);
+
+ // Finalize the hidapi library
+ res = hid_exit();
+
+ return 0;
+}
+```
+
+You can also use [hidtest/test.c](hidtest/test.c)
+as a starting point for your applications.
+
+
+## License
+
+HIDAPI may be used by one of three licenses as outlined in [LICENSE.txt](LICENSE.txt).
+
+## Installing HIDAPI
+
+If you want to build your own application that uses HID devices with HIDAPI,
+you need to get HIDAPI development package.
+
+Depending on what your development environment is, HIDAPI likely to be provided
+by your package manager.
+
+For instance on Ubuntu, HIDAPI is available via APT:
+```sh
+sudo apt install libhidapi-dev
+```
+
+HIDAPI package name for other systems/package managers may differ.
+Check the documentation/package list of your package manager.
+
+## Build from Source
+
+Check [BUILD.md](BUILD.md) for details.
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/AUTHORS b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/AUTHORS
new file mode 100644
index 0000000..e8f5a69
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/AUTHORS
@@ -0,0 +1,91 @@
+Main developers:
+
+ Intra2net AG
+
+Contributors in alphabetical order,
+see Changelog for full details:
+
+ Adam Malinowski
+ Alain Abbas
+ Alex Harford
+ Alexander Lehmann
+ Anders Larsen
+ Andrei Errapart
+ Andrew John Rogers
+ Arnim Läuger
+ Aurelien Jarno
+ Benjamin Vanheuverzwijn
+ Chris Morgan
+ Chris Zeh
+ Claudio Lanconelli
+ Clifford Wolf
+ Dan Dedrick
+ Daniel Kirkham
+ David Challis
+ Davide Michelizza
+ Denis Sirotkin
+ Diego Elio Pettenò
+ Emil
+ Eneas U de Queiroz
+ Eric Schott
+ Eugene Hutorny
+ Evan Nemerson
+ Evgeny Sinelnikov
+ Fabrice Fontaine
+ Fahrzin Hemmati
+ Flynn Marquardt
+ Forest Crossman
+ Frank Dana
+ Holger Mößinger
+ Ian Abbott
+ Jared Boone
+ Jarkko Sonninen
+ Jean-Daniel Merkli
+ Jochen Sprickerhof
+ Joe Zbiciak
+ Jon Beniston
+ Jordan Rupprecht
+ Juergen Beisert
+ Lorenz Moesenlechner
+ Marek Vavruša
+ Marius Kintel
+ Mark Hämmerling
+ Matthias Janke
+ Matthias Kranz
+ Matthias Richter
+ Matthijs ten Berge
+ Max
+ Maxwell Dreytser
+ Michel Zou
+ Mike Frysinger
+ Nathael Pajani
+ Nathan Fraser
+ Oleg Seiljus
+ Paul Fertser
+ Pawel Jewstafjew
+ Peter Holik
+ Raphael Assenat
+ Richard Shaw
+ Robby McKilliam
+ Robert Cox
+ Robin Haberkorn
+ Rodney Sinclair
+ Rogier Wolff
+ Rolf Fiedler
+ Roman Lapin
+ Salvador Eduardo Tropea
+ Stephan Linz
+ Steven Turner
+ Tarek Heiland
+ Thilo Schulz
+ Thimo Eichstaedt
+ Thomas Fischl
+ Thomas Klose
+ Tim Ansell
+ Tom Saunders
+ Uwe Bonnes
+ Vladimir Yakovlev
+ Wilfried Holzke
+ Xiaofan Chen
+ Yegor Yefremov
+ Yi-Shin Li
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING-CMAKE-SCRIPTS b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING-CMAKE-SCRIPTS
new file mode 100644
index 0000000..4b41776
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING-CMAKE-SCRIPTS
@@ -0,0 +1,22 @@
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+1. Redistributions of source code must retain the copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. The name of the author may not be used to endorse or promote products
+ derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING.GPL b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING.GPL
new file mode 100644
index 0000000..d511905
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING.GPL
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING.LIB b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING.LIB
new file mode 100644
index 0000000..5bc8fb2
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/COPYING.LIB
@@ -0,0 +1,481 @@
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the library GPL. It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Library General Public License, applies to some
+specially designated Free Software Foundation software, and to any
+other libraries whose authors decide to use it. You can use it for
+your libraries, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if
+you distribute copies of the library, or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link a program with the library, you must provide
+complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ Our method of protecting your rights has two steps: (1) copyright
+the library, and (2) offer you this license which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ Also, for each distributor's protection, we want to make certain
+that everyone understands that there is no warranty for this free
+library. If the library is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original
+version, so that any problems introduced by others will not reflect on
+the original authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that companies distributing free
+software will individually obtain patent licenses, thus in effect
+transforming the program into proprietary software. To prevent this,
+we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+ Most GNU software, including some libraries, is covered by the ordinary
+GNU General Public License, which was designed for utility programs. This
+license, the GNU Library General Public License, applies to certain
+designated libraries. This license is quite different from the ordinary
+one; be sure to read it in full, and don't assume that anything in it is
+the same as in the ordinary license.
+
+ The reason we have a separate public license for some libraries is that
+they blur the distinction we usually make between modifying or adding to a
+program and simply using it. Linking a program with a library, without
+changing the library, is in some sense simply using the library, and is
+analogous to running a utility program or application program. However, in
+a textual and legal sense, the linked executable is a combined work, a
+derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+ Because of this blurred distinction, using the ordinary General
+Public License for libraries did not effectively promote software
+sharing, because most developers did not use the libraries. We
+concluded that weaker conditions might promote sharing better.
+
+ However, unrestricted linking of non-free programs would deprive the
+users of those programs of all benefit from the free status of the
+libraries themselves. This Library General Public License is intended to
+permit developers of non-free programs to use free libraries, while
+preserving your freedom as a user of such programs to change the free
+libraries that are incorporated in them. (We have not seen how to achieve
+this as regards changes in header files, but we have achieved it as regards
+changes in the actual functions of the Library.) The hope is that this
+will lead to faster development of free libraries.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, while the latter only
+works together with the library.
+
+ Note that it is possible for a library to be covered by the ordinary
+General Public License rather than by this special one.
+
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library which
+contains a notice placed by the copyright holder or other authorized
+party saying it may be distributed under the terms of this Library
+General Public License (also called "this License"). Each licensee is
+addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also compile or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ c) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ d) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the source code distributed need not include anything that is normally
+distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Library General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Library General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ , 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/LICENSE b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/LICENSE
new file mode 100644
index 0000000..f1831c0
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/LICENSE
@@ -0,0 +1,25 @@
+The C library "libftdi1" is distributed under the
+GNU Library General Public License version 2.
+
+A copy of the GNU Library General Public License (LGPL) is included
+in this distribution, in the file COPYING.LIB.
+
+----------------------------------------------------------------------
+
+The C++ wrapper "ftdipp1" is distributed under the GNU General
+Public License version 2 (with a special exception described below).
+
+A copy of the GNU General Public License (GPL) is included
+in this distribution, in the file COPYING.GPL.
+
+As a special exception, if other files instantiate templates or use macros
+or inline functions from this file, or you compile this file and link it
+with other works to produce a work based on this file, this file
+does not by itself cause the resulting work to be covered
+by the GNU General Public License.
+
+However the source code for this file must still be made available
+in accordance with section (3) of the GNU General Public License.
+
+This exception does not invalidate any other reasons why a work based
+on this file might be covered by the GNU General Public License.
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README
new file mode 100644
index 0000000..c64f884
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README
@@ -0,0 +1,67 @@
+--------------------------------------------------------------------
+libftdi version 1.5
+--------------------------------------------------------------------
+
+libftdi - A library (using libusb) to talk to FTDI's UART/FIFO chips
+including the popular bitbang mode.
+
+The following chips are supported:
+* FT230X
+- FT4232H / FT2232H
+- FT232R / FT245R
+- FT2232L / FT2232D / FT2232C
+- FT232BM / FT245BM (and the BL/BQ variants)
+- FT8U232AM / FT8U245AM
+
+libftdi requires libusb 1.x.
+
+The AUTHORS file contains a list of all the people
+that made libftdi possible what it is today.
+
+Changes
+-------
+* Implement tc[io]flush methods & deprecate broken purge_buffers methods
+
+ Please check your code for ftdi_usb_purge_rx_buffer(),
+ ftdi_usb_purge_tx_buffer() and ftdi_usb_purge_buffers()
+ and migrate to the new ftdi_tc[io]flush() methods.
+
+ Old code will continue to function, but you'll get
+ a deprecation warning during compilation.
+
+* Add program to test buffer flush (purge) functionality
+* Add kernel driver auto attach/detach.
+ See new AUTO_DETACH_REATACH_SIO_MODULE option
+* Add ftdi_setflowctrl_xonxoff()
+* ftdi_eeprom / eeprom handling:
+ * Unify handling of all boolean eeprom flags
+ * Add device release number support
+ * Add channel_a_driver support for type xxR chips
+ * Add support for group0 drive levels on x232H chips
+ * Fix handling of high_current_drive parameter
+ * Fix inverted handling of VCP driver field for TYPE_R chips
+ * New --verbose option for eeprom decode operation
+* Add example code for async mode
+* Add SPDX license identifiers to the core library & ftdi_eeprom
+* Various python SWIG wrapper improvements
+* Various cmake file improvements
+* Fix small bugs in error code paths
+
+You'll find the newest version of libftdi at:
+https://www.intra2net.com/en/developer/libftdi
+
+
+Quick start
+-----------
+mkdir build
+cd build
+
+cmake -DCMAKE_INSTALL_PREFIX="/usr" ../
+make
+make install
+
+More verbose build instructions are in "README.build"
+
+--------------------------------------------------------------------
+www.intra2net.com 2003-2020 Intra2net AG
+--------------------------------------------------------------------
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README.build b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README.build
new file mode 100644
index 0000000..e130ca0
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README.build
@@ -0,0 +1,96 @@
+Here is a short tutorial on how to build libftdi git under
+Ubuntu 12.10, But it is similar on other Linux distros.
+
+1) Install the build tools
+sudo apt-get install build-essential (yum install make automake gcc gcc-c++ kernel-devel)
+sudo apt-get install git-core (yum install git)
+sudo apt-get install cmake (yum install cmake)
+sudo apt-get install doxygen (for building documentations) (yum install doxygen)
+
+2) Install dependencies
+sudo apt-get install libusb-1.0-devel (yum install libusb-devel)
+(if the system comes with older version like 1.0.8 or
+earlier, it is recommended you build libusbx-1.0.14 or later).
+
+sudo apt-get install libconfuse-dev (for ftdi-eeprom) (yum install libconfuse-devel)
+sudo apt-get install swig python-dev (for python bindings) (yum install swig python-devel)
+sudo apt-get install libboost-all-dev (for C++ binding and unit test) (yum install boost-devel)
+
+3) Clone the git repository
+mkdir libftdi
+cd libftdi
+git clone git://developer.intra2net.com/libftdi
+
+If you are building the release tar ball, just extract the source
+tar ball.
+
+4) Build the git source and install
+cd libftdi
+mkdir build
+cd build
+cmake -DCMAKE_INSTALL_PREFIX="/usr" ../
+make
+sudo make install
+
+5) carry out some tests
+cd examples
+
+mcuee@Ubuntu1210VM:~/Desktop/build/libftdi/libftdi/build/examples$
+./find_all_pp -v 0x0403 -p 0x6001
+Found devices ( VID: 0x403, PID: 0x6001 )
+------------------------------------------------
+FTDI (0x8730800): ftdi, usb serial converter, ftDEH51S (Open OK)
+FTDI (0x8730918): FTDI, FT232R USB UART, A8007Ub5 (Open OK)
+
+mcuee@Ubuntu1210VM:~/Desktop/build/libftdi/libftdi/build/examples$ ./eeprom
+2 FTDI devices found: Only Readout on EEPROM done. Use
+VID/PID/desc/serial to select device
+Decoded values of device 1:
+Chip type 1 ftdi_eeprom_size: 128
+0x000: 00 00 03 04 01 60 00 04 a0 16 08 00 10 01 94 0a .....`.. ........
+0x010: 9e 2a c8 12 0a 03 66 00 74 00 64 00 69 00 2a 03 .*....f. t.d.i.*.
+0x020: 75 00 73 00 62 00 20 00 73 00 65 00 72 00 69 00 u.s.b. . s.e.r.i.
+0x030: 61 00 6c 00 20 00 63 00 6f 00 6e 00 76 00 65 00 a.l. .c. o.n.v.e.
+0x040: 72 00 74 00 65 00 72 00 12 03 66 00 74 00 44 00 r.t.e.r. ..f.t.D.
+0x050: 45 00 48 00 35 00 31 00 53 00 02 03 00 00 00 00 E.H.5.1. S.......
+0x060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
+0x070: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 16 02 ........ ........
+VID: 0x0403
+PID: 0x6001
+Release: 0x0400
+Bus Powered: 44 mA USB Remote Wake Up
+Manufacturer: ftdi
+Product: usb serial converter
+Serial: ftDEH51S
+Checksum : 0216
+Enable Remote Wake Up
+PNP: 1
+Decoded values of device 2:
+Chip type 3 ftdi_eeprom_size: 128
+0x000: 00 40 03 04 01 60 00 00 a0 2d 08 00 00 00 98 0a .@...`.. .-......
+0x010: a2 20 c2 12 23 10 05 00 0a 03 46 00 54 00 44 00 . ..#... ..F.T.D.
+0x020: 49 00 20 03 46 00 54 00 32 00 33 00 32 00 52 00 I. .F.T. 2.3.2.R.
+0x030: 20 00 55 00 53 00 42 00 20 00 55 00 41 00 52 00 .U.S.B. .U.A.R.
+0x040: 54 00 12 03 41 00 38 00 30 00 30 00 37 00 55 00 T...A.8. 0.0.7.U.
+0x050: 62 00 35 00 c9 bf 1c 80 00 00 00 00 00 00 00 00 b.5..... ........
+0x060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
+0x070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0f 23 ........ .......#
+0x080: 2c 04 d3 fb 00 00 c9 bf 1c 80 42 00 00 00 00 00 ,....... ..B.....
+0x090: 00 00 00 00 00 00 00 00 38 41 32 52 4a 33 47 4f ........ 8A2RJ3GO
+VID: 0x0403
+PID: 0x6001
+Release: 0x0000
+Bus Powered: 90 mA USB Remote Wake Up
+Manufacturer: FTDI
+Product: FT232R USB UART
+Serial: A8007Ub5
+Checksum : 230f
+Internal EEPROM
+Enable Remote Wake Up
+PNP: 1
+Channel A has Mode UART VCP
+C0 Function: TXLED
+C1 Function: RXLED
+C2 Function: TXDEN
+C3 Function: PWREN
+C4 Function: SLEEP
diff --git a/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README.mingw b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README.mingw
new file mode 100644
index 0000000..5b9e65c
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libftdi1-1.5/README.mingw
@@ -0,0 +1,38 @@
+* How to cross compile libftdi-1.x for Windows? *
+ 1 - Prepare a pkg-config wrapper according to
+ https://autotools.io/pkgconfig/cross-compiling.html ,
+ additionally export PKG_CONFIG_ALLOW_SYSTEM_CFLAGS and
+ PKG_CONFIG_ALLOW_SYSTEM_LIBS.
+ 2 - Write a CMake toolchain file according to
+ http://www.vtk.org/Wiki/CmakeMingw . Change the path to your future sysroot.
+ 3 - Get libusb sources (either by cloning the git repo or by downloading a
+ tarball). Unpack, autogen.sh (when building from git), and configure like this:
+ ./configure --build=`./config.guess` --host=i686-w64-mingw32 \
+ --prefix=/usr --with-sysroot=$HOME/i686-w64-mingw32-root/
+ 4 - run
+ make install DESTDIR=$HOME/i686-w64-mingw32-root/
+ 5 - go to libftdi-1.x source directory and run
+ cmake -DCMAKE_TOOLCHAIN_FILE=~/Toolchain-mingw.cmake \
+ -DCMAKE_INSTALL_PREFIX="/usr" \
+ -DPKG_CONFIG_EXECUTABLE=`which i686-w64-mingw32-pkg-config`
+ 6 - run
+ make install DESTDIR=$HOME/i686-w64-mingw32-root/
+
+* How to run libftdi 1.x under Windows *
+
+On 26-Jan-2014, libusbx and libusb project were merged with the release
+of libusb-1.0.18 and now the project is called libusb.
+
+libusb Windows backend will need to rely on a proper driver to run.
+Please refer to the following wiki page for proper driver installation.
+https://github.com/libusb/libusb/wiki/Windows#wiki-How_to_use_libusb_on_Windows
+
+As of 26-Jan-2014, libusb Windows backend supports WinUSB,
+libusb0.sys and libusbk.sys driver. However, libusb's support of
+libusb0.sys and libusbk.sys is considered to be less mature than
+WinUSB. Therefore, WinUSB driver installation using Zadig
+is recommended.
+
+Take note once you replace the original FTDI driver with WinUSB driver,
+you can no longer use the functionality the original FTDI driver provides
+(eg. Virtual Serial Port or D2XX).
diff --git a/openocd-win/openocd/distro-info/licenses/libiconv-1.17/AUTHORS b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/AUTHORS
new file mode 100644
index 0000000..8bedd79
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/AUTHORS
@@ -0,0 +1 @@
+Bruno Haible
diff --git a/openocd-win/openocd/distro-info/licenses/libiconv-1.17/COPYING b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/COPYING
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/COPYING
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ Copyright (C)
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+.
diff --git a/openocd-win/openocd/distro-info/licenses/libiconv-1.17/COPYING.LIB b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/COPYING.LIB
new file mode 100644
index 0000000..4362b49
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/COPYING.LIB
@@ -0,0 +1,502 @@
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ c) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ d) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ e) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ , 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
diff --git a/openocd-win/openocd/distro-info/licenses/libiconv-1.17/DEPENDENCIES b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/DEPENDENCIES
new file mode 100644
index 0000000..748fb83
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/DEPENDENCIES
@@ -0,0 +1,76 @@
+The following packages should be installed before GNU libiconv is installed
+(runtime dependencies that are also build dependencies):
+
+None.
+
+
+The following packages should be installed when GNU libiconv is installed
+(runtime dependencies, but not build dependencies):
+
+None.
+
+
+The following should be installed when GNU libiconv is built, but are not
+needed later, once it is installed (build dependencies, but not runtime
+dependencies):
+
+* A C runtime, compiler, linker, etc.
+ + Mandatory.
+ Either the platform's native 'cc', or GCC 3.1 or newer.
+ + GCC Homepage:
+ https://gcc.gnu.org/
+ + Download:
+ https://ftp.gnu.org/gnu/gcc/
+
+* A 'make' utility.
+ + Mandatory.
+ Either the platform's native 'make' (for in-tree builds only),
+ or GNU Make 3.79.1 or newer.
+ + GNU Make Homepage:
+ https://www.gnu.org/software/make/
+ + Download:
+ https://ftp.gnu.org/gnu/make/
+
+* A shell
+ + Mandatory.
+ Either the platform's native 'sh', or Bash.
+ + Homepage:
+ https://www.gnu.org/software/bash/
+ + Download:
+ https://ftp.gnu.org/gnu/bash/
+
+* Core POSIX utilities, including:
+ [ basename cat chgrp chmod chown cp dd echo expand expr
+ false hostname install kill ln ls md5sum mkdir mkfifo
+ mknod mv printenv pwd rm rmdir sleep sort tee test touch
+ true uname
+ + Mandatory.
+ Either the platform's native utilities, or GNU coreutils.
+ + Homepage:
+ https://www.gnu.org/software/coreutils/
+ + Download:
+ https://ftp.gnu.org/gnu/coreutils/
+
+* The comparison utilities 'cmp' and 'diff'.
+ + Mandatory.
+ Either the platform's native utilities, or GNU diffutils.
+ + Homepage:
+ https://www.gnu.org/software/diffutils/
+ + Download:
+ https://ftp.gnu.org/gnu/diffutils/
+
+* Grep.
+ + Mandatory.
+ Either the platform's native grep, or GNU grep.
+ + Homepage:
+ https://www.gnu.org/software/grep/
+ + Download:
+ https://ftp.gnu.org/gnu/grep/
+
+* Awk.
+ + Mandatory.
+ Either the platform's native awk, mawk, or nawk, or GNU awk.
+ + Homepage:
+ https://www.gnu.org/software/gawk/
+ + Download:
+ https://ftp.gnu.org/gnu/gawk/
diff --git a/openocd-win/openocd/distro-info/licenses/libiconv-1.17/NEWS b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/NEWS
new file mode 100644
index 0000000..9d3cdfb
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/NEWS
@@ -0,0 +1,204 @@
+New in 1.17:
+* The libiconv library is now licensed under the LGPL version 2.1, instead of
+ the LGPL version 2.0. The iconv program continues to be licensed under GPL
+ version 3.
+* Added converters for many single-byte EBCDIC encodings:
+ IBM-{037,273,277,278,280,282,284,285,297,423,424,425,500,838,870,871,875},
+ IBM-{880,905,924,1025,1026,1047,1097,1112,1122,1123,1130,1132,1137,1140},
+ IBM-{1141,1142,1143,1144,1145,1146,1147,1148,1149,1153,1154,1155,1156,1157},
+ IBM-{1158,1160,1164,1165,1166,4971,12712,16804}.
+ They are available through the configure option '--enable-extra-encodings'.
+
+New in 1.16:
+* The preloadable library has been removed.
+
+New in 1.15:
+* The UTF-8 converter now rejects surrogates and out-of-range code points.
+* Added ISO-2022-JP-MS converter.
+* Updated the CP1255 converter to map one more character.
+* The functions now support strings longer than 2 GB.
+
+New in 1.14:
+* The 'iconv' program now produces its output as soon as it can. It no longer
+ unnecessarily waits for more input.
+* Updated the GB18030 converter to map 25 characters to code points that have
+ been to Unicode since 2000, rather than to code points in the Private Use
+ Area.
+* Updated the BIG5-HKSCS converter. The old BIG5-HKSCS converter is renamed to
+ BIG5-HKSCS:2004. A new converter BIG5-HKSCS:2008 is added. BIG5-HKSCS is now
+ an alias for BIG5-HKSCS:2008.
+* Fixed a bug in the conversion to wchar_t.
+* Fixed a small bug in the CP1258 converter.
+
+New in 1.13:
+* The library and the iconv program now understand platform dependent aliases,
+ for better compatibility with the platform's own iconv_open function.
+ Examples: "646" on Solaris, "iso88591" on HP-UX, "IBM-1252" on AIX.
+* For stateful encodings, when the input ends with a shift sequence followed
+ by invalid input, the iconv function now increments the input pointer past
+ the shift sequence before returning (size_t)(-1) with errno = EILSEQ. This
+ is also like GNU libc's iconv() behaves.
+* The library exports a new function iconv_open_into() that stores the
+ conversion descriptor in pre-allocated memory, rather than allocating fresh
+ memory for it.
+* Added CP1131 converter.
+
+New in 1.12:
+* The iconv program is now licensed under the GPL version 3, instead of the
+ GPL version 2. The libiconv library continues to be licensed under LGPL.
+* Added RK1048 converter.
+* On AIX, an existing system libiconv no longer causes setlocale() to fail.
+* Upgraded EUC-KR, JOHAB to include the Korean postal code sign.
+
+New in 1.11:
+* The iconv program has new options --unicode-subst, --byte-subst,
+ --widechar-subst that allow to specify substitutions for characters that
+ cannot be converted.
+* The iconv program now understands long options:
+ long option equivalent to
+ --from-code -f
+ --to-code -t
+ --list -l
+ --silent -s
+* The CP936 converter is now different from the GBK converter: it has changed
+ to include the Euro sign and private area characters. CP936 is no longer an
+ alias of GBK.
+* Updated GB18030 converter to include all private area characters.
+* Updated CP950 converter to include the Euro sign and private area characters.
+* Updated CP949 converter to include private area characters.
+* Updated the BIG5-HKSCS converter. The old BIG5-HKSCS converter is renamed to
+ BIG5-HKSCS:1999 and updated to Unicode 4. New converters BIG5-HKSCS:2001 and
+ BIG5-HKSCS:2004 are added. BIG5-HKSCS is now an alias for BIG5-HKSCS:2004.
+* Added a few irreversible mappings to the CP932 converter.
+* Tidy up the list of symbols exported from libiconv (assumes gcc >= 4.0).
+
+New in 1.10:
+* Added ISO-8859-11 converter.
+* Updated the ISO-8859-7 converter.
+* Added ATARIST converter, available through --enable-extra-encodings.
+* Added BIG5-2003 converter (experimental), available through
+ --enable-extra-encodings.
+* Updated EUC-TW converter to include the Euro sign.
+* The preloadable library has been renamed from libiconv_plug.so to
+ preloadable_libiconv.so.
+* Portability to mingw.
+
+New in 1.9:
+* Many more transliterations.
+* New configuration option --enable-relocatable. See the INSTALL.generic file
+ for details.
+
+New in 1.8:
+* The iconv program has new options -l, -c, -s.
+* The iconv program is internationalized.
+* Added C99 converter.
+* Added KOI8-T converter.
+* New configuration option --enable-extra-encodings that enables a bunch of
+ additional encodings; see the README for details.
+* Updated the ISO-8859-16 converter.
+* Upgraded BIG5-HKSCS, EUC-TW, ISO-2022-CN, ISO-2022-CN-EXT converters to
+ Unicode 3.2.
+* Upgraded EUC-KR, CP949, JOHAB converters to include the Euro sign.
+* Changed the ARMSCII-8 converter.
+* Extended the EUC-JP encoder so that YEN SIGN characters don't cause failures
+ in Shift_JIS to EUC-JP conversion.
+* The JAVA converter now handles characters outside the Unicode BMP correctly.
+* Fixed a bug in the CP1255, CP1258, TCVN decoders: The base characters of
+ combining characters could be dropped at the end of the conversion buffer.
+* Fixed a bug in the transliteration that could lead to excessive memory
+ allocations in libintl when transliteration was needed.
+* Portability to BSD/OS and SCO 3.2.5.
+
+New in 1.7:
+* Added UTF-32, UTF-32BE, UTF-32LE converters.
+* Changed CP1255, CP1258 and TCVN converters to handle combining characters.
+* Changed EUC-JP, SHIFT_JIS, CP932, ISO-2022-JP, ISO-2022-JP-2, ISO-2022-JP-1
+ converters to use fullwidth Yen sign instead of halfwidth Yen sign, and
+ fullwidth tilde instead of halfwidth tilde.
+* Upgraded EUC-TW, ISO-2022-CN, ISO-2022-CN-EXT converters to Unicode 3.1.
+* Changed the GB18030 converter to not reject unassigned and private-use
+ Unicode characters.
+* Fixed a bug in the byte order mark treatment of the UCS-4 decoder.
+* The manual pages are now distributed also in HTML format.
+
+New in 1.6:
+* The iconv program's -f and -t options are now optional.
+* Many more transliterations.
+* Added CP862 converter.
+* Changed the GB18030 converter.
+* Portability to DOS with DJGPP.
+
+New in 1.5:
+* Added an iconv(1) program.
+* New locale dependent encodings "char", "wchar_t".
+* Transliteration is now off by default. Use a //TRANSLIT suffix to enable it.
+* The JOHAB encoding is documented again.
+* Changed a few mappings in the CP950 converter.
+
+New in 1.4:
+* Added GB18030, BIG5HKSCS converters.
+* Portability to OS/2 with emx+gcc.
+
+New in 1.3:
+* Added UCS-2BE, UCS-2LE, UCS-4BE, UCS-4LE converters.
+* Fixed the definition of EILSEQ on SunOS4.
+* Fixed a build problem on OSF/1.
+* Support for building as a shared library on Woe32.
+
+New in 1.2:
+* Added UTF-16BE and UTF-16LE converters.
+* Changed the UTF-16 encoder.
+* Fixed the treatment of tab characters in the UTF-7 converter.
+* Fixed an internal error when output buffer was not large enough.
+
+New in 1.1:
+* Added ISO-8859-16 converter.
+* Added CP932 converter, a variant of SHIFT_JIS.
+* Added CP949 converter, a variant of EUC-KR.
+* Improved the ISO-2022-CN-EXT converter: It now covers the ISO-IR-165 range.
+* Updated the ISO-8859-8 conversion table.
+* The JOHAB encoding is deprecated and not documented any more.
+* Fixed two build problems: 1. "make -n check" failed. 2. When libiconv was
+ already installed, "make" failed.
+
+New in 1.0:
+* Added transliteration facilities.
+* Added a test suite.
+* Fixed the iconv(3) manual page and function: the return value was not
+ described correctly.
+* Fixed a bug in the CP1258 decoder: invalid bytes now yield EILSEQ instead of
+ U+FFFD.
+* Fixed a bug in the Georgian-PS encoder: accept U+00E6.
+* Fixed a bug in the EUC-JP encoder: reject 0x8E5C and 0x8E7E.
+* Fixed a bug in the KSC5601 and JOHAB converters: they recognized some Hangul
+ characters at some invalid code positions.
+* Fixed a bug in the EUC-TW decoder; it was severely broken.
+* Fixed a bug in the CP950 converter: it recognized a dubious BIG5 range.
+
+New in 0.3:
+* Reduced the size of the tables needed for the JOHAB converter.
+* Portability to Woe32.
+
+New in 0.2:
+* Added KOI8-RU, CP850, CP866, CP874, CP950, ISO-2022-CN-EXT, GBK and
+ ISO-2022-JP-1 converters.
+* Added MACINTOSH as an alias for MAC-ROMAN.
+* Added ASMO-708 as an alias for ISO-8859-6.
+* Added ELOT_928 as an alias for ISO-8859-7.
+* Improved the EUC-TW converter: Treat CNS 11643 plane 3.
+* Improved the ISO-2022-KR and EUC-KR converters: Hangul characters are
+ decomposed into Jamo when needed.
+* Improved the CP932 converter.
+* Updated the CP1133, MULELAO-1 and ARMSCII-8 mappings.
+* The EUC-JP and SHIFT_JIS converters now cover the user-defined range.
+* Fixed a possible buffer overrun in the JOHAB converter.
+* Fixed a bug in the UTF-7, ISO-2022-*, HZ decoders: a shift sequence a the
+ end of the input no longer gives an error.
+* The HZ encoder now always terminates its output in the ASCII state.
+* Use a perfect hash table for looking up the aliases.
+
+New in 0.1:
+* Portability to Linux/glibc-2.0.x, Linux/libc5, OSF/1, FreeBSD.
+* Fixed a bug in the EUC-JP decoder. Extended the ISO-2022-JP-2 converter.
+* Made TIS-620 mapping consistent with glibc-2.1.
+
diff --git a/openocd-win/openocd/distro-info/licenses/libiconv-1.17/README b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/README
new file mode 100644
index 0000000..e7375cb
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/README
@@ -0,0 +1,173 @@
+ GNU LIBICONV - character set conversion library
+
+This library provides an iconv() implementation, for use on systems which
+don't have one, or whose implementation cannot convert from/to Unicode.
+
+It provides support for the encodings:
+
+ European languages
+ ASCII, ISO-8859-{1,2,3,4,5,7,9,10,13,14,15,16},
+ KOI8-R, KOI8-U, KOI8-RU,
+ CP{1250,1251,1252,1253,1254,1257}, CP{850,866,1131},
+ Mac{Roman,CentralEurope,Iceland,Croatian,Romania},
+ Mac{Cyrillic,Ukraine,Greek,Turkish},
+ Macintosh
+ Semitic languages
+ ISO-8859-{6,8}, CP{1255,1256}, CP862, Mac{Hebrew,Arabic}
+ Japanese
+ EUC-JP, SHIFT_JIS, CP932, ISO-2022-JP, ISO-2022-JP-2, ISO-2022-JP-1,
+ ISO-2022-JP-MS
+ Chinese
+ EUC-CN, HZ, GBK, CP936, GB18030, EUC-TW, BIG5, CP950, BIG5-HKSCS,
+ BIG5-HKSCS:2004, BIG5-HKSCS:2001, BIG5-HKSCS:1999, ISO-2022-CN,
+ ISO-2022-CN-EXT
+ Korean
+ EUC-KR, CP949, ISO-2022-KR, JOHAB
+ Armenian
+ ARMSCII-8
+ Georgian
+ Georgian-Academy, Georgian-PS
+ Tajik
+ KOI8-T
+ Kazakh
+ PT154, RK1048
+ Thai
+ ISO-8859-11, TIS-620, CP874, MacThai
+ Laotian
+ MuleLao-1, CP1133
+ Vietnamese
+ VISCII, TCVN, CP1258
+ Platform specifics
+ HP-ROMAN8, NEXTSTEP
+ Full Unicode
+ UTF-8
+ UCS-2, UCS-2BE, UCS-2LE
+ UCS-4, UCS-4BE, UCS-4LE
+ UTF-16, UTF-16BE, UTF-16LE
+ UTF-32, UTF-32BE, UTF-32LE
+ UTF-7
+ C99, JAVA
+ Full Unicode, in terms of 'uint16_t' or 'uint32_t'
+ (with machine dependent endianness and alignment)
+ UCS-2-INTERNAL, UCS-4-INTERNAL
+ Locale dependent, in terms of 'char' or 'wchar_t'
+ (with machine dependent endianness and alignment, and with OS and
+ locale dependent semantics)
+ char, wchar_t
+ The empty encoding name "" is equivalent to "char": it denotes the
+ locale dependent character encoding.
+
+When configured with the option --enable-extra-encodings, it also provides
+support for a few extra encodings:
+
+ European languages
+ CP{437,737,775,852,853,855,857,858,860,861,863,865,869,1125}
+ Semitic languages
+ CP864
+ Japanese
+ EUC-JISX0213, Shift_JISX0213, ISO-2022-JP-3
+ Chinese
+ BIG5-2003 (experimental)
+ Turkmen
+ TDS565
+ Platform specifics
+ ATARIST, RISCOS-LATIN1
+ EBCDIC compatible (not ASCII compatible, very rarely used)
+ European languages
+ IBM-{037,273,277,278,280,282,284,285,297,423,500,870,871,875,880},
+ IBM-{905,924,1025,1026,1047,1112,1122,1123,1140,1141,1142,1143},
+ IBM-{1144,1145,1146,1147,1148,1149,1153,1154,1155,1156,1157,1158},
+ IBM-{1165,1166,4971}
+ Semitic languages
+ IBM-{424,425,12712,16804}
+ Persian
+ IBM-1097
+ Thai
+ IBM-{838,1160}
+ Laotian
+ IBM-1132
+ Vietnamese
+ IBM-{1130,1164}
+ Indic languages
+ IBM-1137
+
+It can convert from any of these encodings to any other, through Unicode
+conversion.
+
+It has also some limited support for transliteration, i.e. when a character
+cannot be represented in the target character set, it can be approximated
+through one or several similarly looking characters. Transliteration is
+activated when "//TRANSLIT" is appended to the target encoding name.
+
+libiconv is for you if your application needs to support multiple character
+encodings, but that support lacks from your system.
+
+
+Installation
+------------
+
+As usual for GNU packages:
+
+ $ ./configure --prefix=[[PREFIX]] where [[PREFIX]] is e.g. $HOME/local
+ $ make
+ $ make install
+
+After installing GNU libiconv for the first time, it is recommended to
+recompile and reinstall GNU gettext, so that it can take advantage of
+libiconv.
+
+On systems other than GNU/Linux, the iconv program will be internationalized
+only if GNU gettext has been built and installed before GNU libiconv. This
+means that the first time GNU libiconv is installed, we have a circular
+dependency between the GNU libiconv and GNU gettext packages, which can be
+resolved by building and installing either
+ - first libiconv, then gettext, then libiconv again,
+or (on systems supporting shared libraries, excluding AIX)
+ - first gettext, then libiconv, then gettext again.
+Recall that before building a package for the second time, you need to erase
+the traces of the first build by running "make distclean".
+
+This library installs:
+ - a library 'libiconv.so',
+ - a header file ''.
+
+To use it, simply #include and use the functions.
+
+To use it in a package that uses GNU autoconf and GNU automake:
+ - Use gnulib-tool to import the Gnulib module 'iconv'. It consists
+ of a couple of *.m4 files (iconv.m4 and its dependencies) and a
+ file 'build-aux/config.rpath'.
+ - Add to the link command line of libraries and executables that use
+ the functions the placeholder @LIBICONV@ (or, if using libtool for
+ the link, @LTLIBICONV@). In Makefile.am files, the right place for
+ these additions are the *_LDADD variables.
+
+
+Copyright
+---------
+
+The libiconv and libcharset _libraries_ and their header files are under LGPL,
+see file COPYING.LIB.
+
+The iconv _program_ and the documentation are under GPL, see file COPYING.
+
+
+Download
+--------
+
+ https://ftp.gnu.org/gnu/libiconv/libiconv-1.17.tar.gz
+
+Homepage
+--------
+
+ https://www.gnu.org/software/libiconv/
+
+Bug reports
+-----------
+
+Report bugs
+ - in the bug tracker at
+ - or by email to .
+
+
+Bruno Haible
diff --git a/openocd-win/openocd/distro-info/licenses/libiconv-1.17/THANKS b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/THANKS
new file mode 100644
index 0000000..a6f02ff
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libiconv-1.17/THANKS
@@ -0,0 +1,15 @@
+ Thanks to for
+
+Edmund Grimley Evans bug reports
+
+Taro Muraoka Woe32 DLL support
+
+Akira Hatakeyama OS/2 support
+
+Juan Manuel Guerrero
+ DOS/DJGPP support
+
+Hironori Sakamoto advice on EUC-JP and JISX0213
+
+Ken Lunde detailed information about GB18030
+
diff --git a/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/AUTHORS b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/AUTHORS
new file mode 100644
index 0000000..4e4904e
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/AUTHORS
@@ -0,0 +1,50 @@
+* GNU Libtool was conceived, designed and implemented by:
+
+ Gordon Matzigkeit gord@gnu.org
+
+* GNU Libtool's Dynamic Loader library (libltdl) was conceived,
+ designed and implemented by:
+
+ Thomas Tanner tanner@ffii.org
+
+* GNU Libtool and libltdl have previously been maintained, enhanced,
+ ported and otherwise advanced by:
+
+ Alexandre Oliva oliva@dcc.unicamp.br
+ Ossama Othman ossama@debian.org
+ Robert Boehne rboehne@ricardo-us.com
+ Scott James Remnant scott@netsplit.com
+ Peter O'Gorman peter@pogma.com
+ Ralf Wildenhues Ralf.Wildenhues@gmx.de
+ Gary V. Vaughan gary@vaughan.pe
+ Bob Friesenhahn bfriesen@simple.dallas.tx.us
+ Peter Rosin peda@lysator.liu.se
+ Noah Misch noah@cs.caltech.edu
+ Charles Wilson libtool@cwilson.fastmail.fm
+ Brooks Moses bmoses@google.com
+
+* GNU Libtool is currently being cajoled, bullied,
+ rewritten and otherwise dragged into the future by:
+
+ Alex Ameen alex.ameen.tx@gmail.com
+--
+ Copyright (C) 1996, 1998-2019, 2021-2022 Free Software Foundation,
+ Inc.
+
+ This file is part of GNU Libtool.
+
+GNU Libtool is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License as
+published by the Free Software Foundation; either version 2 of
+the License, or (at your option) any later version.
+
+GNU Libtool is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with GNU Libtool; see the file COPYING. If not, a copy
+can be downloaded from http://www.gnu.org/licenses/gpl.html,
+or obtained by writing to the Free Software Foundation, Inc.,
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
diff --git a/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/COPYING b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/COPYING
new file mode 100644
index 0000000..d159169
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/COPYING
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
diff --git a/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/NEWS b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/NEWS
new file mode 100644
index 0000000..ba99fbe
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/NEWS
@@ -0,0 +1,1251 @@
+NEWS - list of user-visible changes between releases of GNU Libtool
+
+* Noteworthy changes in release 2.4.7 (2022-03-16) [stable]
+
+** New features:
+
+ - Libtool script now supports (configure-time and runtime) ARFLAGS
+ variable, which obsoletes AR_FLAGS. This is due to naming conventions
+ among other *FLAGS and to be consistent with Automake's ARFLAGS.
+
+ - Gnulib testsuite is enabled and run during 'make check'.
+
+ - Support the Windows version of the Intel C Compiler (icl) in
+ libtool script.
+
+ - Pass '-fsanitize=*' flags for GCC and LLVM, and '-specs=*' for GCC
+ to linker.
+
+ - Pass '-Xassembler=*' and '-Wa,*' flag to compilers and linkers.
+
+ - The variable 'FILECMD' with default value of '/usr/bin/file' was used to
+ replace existing hard coded references to '/usr/bin/file'.
+
+ - Add MidnightBSD support.
+
+** Important incompatible changes:
+
+ - Libtool changed ARFLAGS/AR_FLAGS default from 'cru' to 'cr'.
+
+ - Do not pass '-pthread' to Solaris linker.
+
+ - 'libtool' and 'libtoolize' scripts now use '#! /usr/bin/env sh' shebang.
+ Previously '#! /bin/sh' was used, which presents challenges for
+ containerized environments.
+
+** Bug fixes:
+
+ - Fix significant slowdown of libtoolize for certain projects (regression
+ introduced in 2.4.3 release) caused by infinite m4 macro recursion.
+
+ - Mitigate the slowdown of libtool script (introduced in v2.4.3) caused by
+ increased number of calls to '$SED $sed_quote_subst' (bug#20006).
+
+ - Properly parse and export TLS symbols on AIX.
+
+ - Various bug fixes surrounding use of 'sed'.
+
+ - Darwin systems set proper "allow undefined" flag on OSX 11, and
+ PowerPC 10.5.
+
+ - Removed some deprecated tests related to 'Makefile.inc' files.
+
+* Noteworthy changes in release 2.4.6 (2015-02-15) [stable]
+
+** New features:
+
+ - LT_SYS_LIBRARY_PATH can be set in config.site, or at configure time
+ and persists correctly in the generated libtool script.
+
+** Bug fixes:
+
+ - Fix a race condition in ltdl dryrun test that would cause spurious
+ random failures of that test.
+
+ - LT_SYS_DLSEARCH_PATH is munged correctly.
+
+
+* Noteworthy changes in release 2.4.5 (2015-01-19) [stable]
+
+** New features:
+
+ - Libtoolize searches for the best available M4 on the user PATH at
+ runtime, rather than settling for the first one found.
+
+ - Support munging sys_lib_dlsearch_path_spec with LT_SYS_LIBRARY_PATH
+ environment variable.
+
+** Bug fixes:
+
+ - Bail out at configure time if the installed M4 is not sufficient
+ for the purposes of libtoolize.
+
+ - freebsd-elf library versioning was upgraded incorrectly in 2.4.4,
+ but now works properly again.
+
+ - Fix a 2.4.4 regression so that libltdl subprojects do not warn
+ about missing libltdl/libltdl directory as in prior releases.
+
+ - When using Sun C++ on Solaris or GNU/Linux we used to set libtool's
+ postdeps permanently, based on the contents of $CXX and $CXXFLAGS at
+ configure time, which was brittle and error-prone. Now, we no
+ longer check for a SunCC ABI at configure time, but augment the
+ postdeps at libtool time based on the current invocation flags on
+ each call.
+
+** Changes in supported systems or compilers:
+
+ - /usr/local prefixed rpaths are now added to the link-line on
+ ia64-hp-hpux*, because the default system runtime loader path does
+ not contain them.
+
+ - Previously, when using Sun C++ on Solaris or GNU/Linux, `-Cstd -Crun`
+ flags were added to $postdeps unless CXX or CXXFLAGS contained
+ `-library=stlport4`. Newer releases have added other compiler flags
+ that are also incompatible with `-Cstd -Crun`, so now we don't add
+ them if any of `-std=c++[0-9][0-9]`, `-library=stdcxx4` or
+ `-compat=g` were found in CXX or CXXFLAGS when the Sun C++ compiler
+ is detected.
+
+
+* Noteworthy changes in release 2.4.4 (2014-11-29) [stable]
+
+** New features:
+
+ - Libltdl maintains its own fork of argz, with macros and files in
+ the LT_ and lt__ namespaces (resp.) where they cannot clash with
+ client projects' use of gnulib argz.
+
+** Bug fixes:
+
+ - Installation of 'libtoolize' once again obeys '--program-prefix',
+ '--program-suffix' and '--program-transform-name' configure options.
+
+ - `libtoolize` doesn't remove any files that it can't reinstall,
+ including old versions of the snippet directory, and gnulib's
+ version of the argz module and supporting files.
+
+ - LT_FUNC_DLYSM_USCORE now works correctly on systems that don't
+ support self dlopen()ing.
+
+** Important incompatible changes:
+
+ - LT_LIB_DLLOAD no longer prepends -ldl or -ldld to LIBS, causing
+ duplicate occurrences in libltdl link lines. If you need to
+ add a library for dlopen() or shl_load() in your Makefile, then
+ use $(LIBADD_DLOPEN) or $(LIBADD_SHL_LOAD) respectively. If you
+ are using libltdl, this all happens automatically, and the only
+ difference you'll see is no more duplicated library names in the
+ verbose link line.
+
+** Changes in supported systems or compilers:
+
+ - Preliminary support for tcc on linux*. Although it already worked
+ sometimes in previous releases, making sure to set LD correctly now
+ avoids mis-matching GNU ld with tcc:
+
+ ./configure CC=tcc LD=tcc
+
+ - Added -os2dllname option to work around 8 character base name
+ limit on OS/2. The option has no effect on other systems.
+
+ - Support for DLL versioning, -export-symbols and -export-symbols-regex
+ on OS/2.
+
+ - Support filename-based shared library versioning on AIX. See manual
+ for details.
+
+
+* Noteworthy changes in release 2.4.3 (2014-10-27) [stable]
+
+** New features:
+
+ - Moved to gnulib release infrastructure.
+
+ - M4 is now used for scanning the M4 macros in your configure.ac that
+ 'libtoolize' looks at to determine what files you want, and where you
+ would like them installed. This means that you can compose your
+ version number or any other argument that Libtoolize needs to know at
+ M4 time using git-version-gen from gnulib, for example.
+
+ - Invoking 'libtoolize --ltdl' no longer maintains a separate autoconf
+ macro directory in the libltdl tree, but automatically adjusts the
+ installed libltdl configuration files to share whatever macro
+ directory is declared by the parent project. (Note: if you were
+ already sharing a macro directory with AC_CONFIG_MACRO_DIR(ltdl/m4)
+ or similar, that still works as does any other directory choice).
+
+ - Invoking 'libtoolize --ltdl' no longer maintains a separate auxiliary
+ scripts directory in the libltdl tree, but automatically adjusts the
+ installed libltdl configuration files to share whatever auxiliary
+ scripts directory is declared by the parent project. (Note: if you
+ were already sharing an auxiliary directory with subproject libltdl
+ using AC_CONFIG_AUX_DIR(ltdl/config) or similar, that still works as
+ does any other directory choice).
+
+ - The legacy tests have all been migrated to the Autotest harness.
+
+ - The Autotest testsuite can be run without the especially time consuming
+ tests with:
+
+ make check-local TESTSUITEFLAGS='-k "!expensive"'
+
+** Bug fixes:
+
+ - Fix a long-standing latent bug in autom4te include path for autotests
+ with VPATH builds.
+ - Fix a long-standing latent bug in libtoolize that could delete lines
+ from libltdl/Makefile.am in recursive mode due to underquoting in a
+ sed script.
+ - Fix a long-standing bug in libtoolize, by outputting the 'putting
+ auxiliary files in' header with 'libtoolize --ltdl --subproject'.
+ - Fix a long-standing bug in libtoolize subproject installation, by not
+ installing a set of autoconf macro files into the parent project if
+ there is no configure.ac present to use them.
+ - The libtoolize subproject mode selector is now named '--subproject'
+ and is equivalent to the implied '--subproject' mode when no other
+ mode is selected; '--standalone' never worked, and is no longer
+ accepted.
+ - Libtool and libtoolize no longer choke on paths with a comma in them.
+ - In the case where $SHELL does not have the same enhanced features
+ (e.g. the ability to parse 'var+=append') as $CONFIG_SHELL, libtool
+ will now correctly fallback to using only vanilla shell features
+ instead of failing with a parse at startup.
+ - Correctly recognize import libraries when Microsoft dumpbin is used
+ as the name lister and extend the dumpbin wrapper to find symbols
+ in import libraries using the -headers option of dumpbin. Also fix a
+ bug in the dumpbin wrapper that could lead to broken symbol listings
+ in some corner cases.
+ - Use the improved Microsoft dumpbin support to mend preloading of
+ import libraries for Microsoft Visual C/C++.
+ - No longer mangle module-definition (.def) files when feeding them to
+ the Microsoft Visual C/C++ linker via the -export-symbols argument to
+ the libtool script, thus matching how .def files are handled when
+ using GNU tools.
+ - Recognize more variants (e.g. those starting with a LIBRARY statement)
+ of module-definitions (.def) files when using them instead of a raw
+ list of symbols to export.
+ - Fix a long-standing bug when using libtoolize without automake; we
+ no longer remove install-sh with --force, since it's not a file
+ libtoolize will reinstall without --install..
+
+** Important incompatible changes:
+
+ - GNU M4 is required to run libtoolize in a directory with a
+ 'configure.ac' (or 'configure.in') that needs tracing to determine
+ what modes and directories have been specified.
+
+ - The use of the idiosyncratically named 'Makefile.inc' in nonrecursive
+ libltdl builds is deprecated, although it will be supported for one
+ more year or until the next release, whichever takes longer. Please
+ upgrade to the more standard naming of 'ltdl.mk' in keeping with other
+ GNU projects.
+
+ - libtoolize now behaves consistenty in respect of multiple directory
+ arguments to ACLOCAL_AMFLAGS and multiple invocations of AC_CONFIG-
+ _MACRO_DIRS, where the first directory is always selected. Previous
+ releases took the first ACLOCAL_AMFLAGS argument, but the last
+ invocation of AC_CONFIG_MACRO_DIRS.
+
+ - The libtoolize program now advises use of the new Autoconf
+ AC_CONFIG_MACRO_DIRS declaration. If you follow that advice, all
+ your developers will need at least autoconf-2.70 and automake-1.13
+ to rebootstrap your probject. If you still need to support
+ bootstrap with older Autotools, then you should add the following
+ to your configure.ac file:
+
+ m4_ifndef([AC_CONFIG_MACRO_DIRS],
+ [m4_define([AC_CONFIG_MACRO_DIRS],
+ m4_defn([AC_CONFIG_MACRO_DIR]))])
+
+ - Overhead of probing for a non-backslash crippled echo equivalent
+ during initialization of every script has been removed in favor of
+ trusting that "printf %s\n" works out of the box on all non-museum
+ host architectures. Manually setting ECHO appropriately in the
+ build environment will be necessary on some ancient architectures.
+
+** Changes in supported systems or compilers:
+
+ - Support for bitrig (*-*-bitrig*).
+
+ - Solaris 7 and earlier requires ECHO=/usr/ucb/echo in the build
+ environment, to build and use libtool.
+
+New in 2.4.2 2011-10-17: git version 2.4.1a, Libtool team:
+
+* New features:
+
+ - The --with-pic configure option now supports a list of comma-separated
+ package names. This can be used to build some static libraries with PIC
+ objects while building others with non-PIC objects.
+
+ - Initial support for Go, using the gccgo compiler.
+
+ - On Mac OS X .dylib is now tried as well as .so with
+ lt_dlopenext().
+
+* Bug fixes:
+
+ - The generic approximation of the command line length limit (when getconf is
+ not available) works again. Regression introduced in v2.2.6-39-g9c3d4d8.
+ - The bug that leaked developer tool paths into the release tarballs
+ from ./bootstrap is fixed.
+ - Improved support for the Cuda Compiler Driver (nvcc) on Darwin.
+ - For GCC LTO support, the -fuse-linker-plugin switch is now also removed
+ when computing compiler postdeps.
+
+* Important incompatible changes:
+
+ - The undocumented hardcode_libdir_flag_spec_ld tag variable has been
+ removed in favor of using hardcode_libdir_flag_spec with $wl set to empty.
+
+* Changes in supported systems or compilers:
+
+ - Fixes for gfortran on Darwin, XL Fortran on GNU/Linux.
+ - Support for FreeBSD 1.x (outdated since 1994) has been removed.
+
+New in 2.4 2010-09-22: git version 2.2.11a, Libtool team:
+
+* New features:
+
+ - Sysroot support. This allows you to build cross-compiled packages
+ with the same prefix that will be used on the destination machine,
+ and still find dependent libraries under the compiler's "sysroot".
+ Without sysroot support, paths internal to the build system may leak
+ into the product of the build.
+
+ Sysroot support is disabled unless the --with-sysroot configure
+ option is passed to configure, because .la files generated with
+ sysroot support will _not_ be usable in general with older Libtools.
+
+ - On non-cygwin Windows systems, we now lookup potential library
+ file names without regard to file name case.
+ - The old testsuite now uses the 'parallel-tests' Automake test driver
+ now for more concurrency and better test logging. For this, tests are
+ run in verbose mode by default now.
+
+* Important incompatible changes:
+
+ - Autoconf 2.62 and Automake 1.11.1 or newer are now required for
+ bootstrapping Libtool. For using Libtool in your own projects,
+ Autoconf 2.59 and Automake 1.9.6 should still work.
+ - The fix_srcfile_path variable has been replaced by a more thorough
+ mechanism triggered by the to_tool_file_cmd variable.
+
+* Changes in supported systems or compilers:
+
+ - Initial support for the Microsoft C/C++ Compiler, with help from
+ the compile script in unreleased Automake 1.12. Override the manifest
+ tool used to embed the manifest resource through the environment
+ variable MANIFEST_TOOL. Please note that the import library naming
+ has changed (from foo-2.lib to foo.dll.lib) from when the code lived
+ in its own git branch.
+ - Initial support for the NAG Fortran compiler on GNU/Linux.
+
+* Bug fixes:
+
+ - The 'check-interactive' and 'check-noninteractive' convenience make
+ targets now also work for the old testsuite.
+ - Warnings from Autoconf v2.67-36-g1e604ec about incomplete programs
+ passed to AC_*_IFELSE tests have been fixed.
+ - On IRIX, the test for -Wl,-exported_symbol now also works with gfortran.
+
+New in 2.2.10 2010-06-10: git version 2.2.9a, Libtool team:
+
+* New features:
+
+ - On non-cygwin Windows systems, we no longer try to lookup the POSIX
+ format path recorded in $libdir of a pseudo-library when looking up
+ the location of the library with the native tools.
+
+New in 2.2.8 2010-06-05: git version 2.2.7c, Libtool team:
+
+* No new features:
+
+ - Bumped version number and promoted 2.2.7b release candidate to a full
+ stable release.
+
+New in 2.2.7b 2010-05-20: git version 2.2.7a, Libtool team:
+
+* New features:
+
+ - Libtool ships and installs man pages for libtool and libtoolize now.
+ - New libtool command line flag --help-all.
+ - New libtool command line flag --no-silent (with alternate spelling
+ --no-quiet). This flag (re)enables the default informational messages,
+ but has no effect on so-called "verbose" output messages.
+ - New libtool command line flag --no-verbose, which disables only
+ the extra "verbose" output messages and has no effect on the
+ default informational messages.
+ - New convenience make targets 'check-noninteractive' to avoid long testsuite
+ runs on Windows with popup windows in the middle, and 'check-interactive'
+ for the complement set of tests.
+ - New link mode flag -bindir to specify the location for installed PE DLLs.
+ - Wrapper scripts and wrapper executables for programs linked against
+ uninstalled shared libraries now support command-line options --lt-debug
+ and --lt-dump-script.
+
+* Important incompatible changes:
+
+ - The wrapper command line option support described above introduces the
+ following incompatibility: the wrapper will remove any command line
+ options that begin with '--lt-*' from the argument list before launching
+ (uninstalled) programs. Any '--lt-*' option on the command line not
+ recognized by the wrapper will result in an error.
+ - The type of the symbol lists variables (lt_*_LTX_preloaded_symbols) has
+ been fixed in the manual and in a couple of tests to match the actual
+ implementation.
+
+* Changes in supported systems or compilers:
+
+ - Improved support for 64bit Windows (mingw64).
+ - Improved support for cegcc (Windows CE/PocketPC).
+ - Support for GNU/kOpenSolaris (kopensolaris*-gnu).
+ - Initial support for compilers on BlueGene BG/P.
+ - Improved support for Atari FreeMiNT.
+ - With binutils 2.19.50+, shared libraries can be built on AIX.
+ - Initial support for the Cuda Compiler Driver on GNU/Linux.
+ - Support for Haiku (i586-pc-haiku).
+ - Initial support for GCC link-time optimization (LTO) flags.
+
+* Bug fixes:
+
+ - Fix 2.2.6 regression that prevented using the libltdl macros together
+ with Autoconf 2.59 ('possibly undefined macro: LT_LIBEXT').
+ - Fix 2.2.4 regression that caused arguments with special characters
+ to be mangled by the compile wrapper for uninstalled programs on MinGW.
+ - libtool command line flag --verbose now also enables explicit
+ verbose output, in addition to its previous behavior of (re)enabling
+ only the default informational output. See New Features, --no-silent.
+ - Link tests are guarded by cache variables so they can be avoided for
+ bootstrapping purposes (e.g., when link tests are not possible).
+ - Argument mangling of execute mode has been improved (i.e., lessened).
+ - Fix 2.1b regression that caused nm to not be the default name lister.
+ The regression affected mainly (arguably broken) cross compiles.
+ - Fix long standing bug that caused compiler checks for Fortran and
+ C++ compilers to run twice.
+ - Link mode works around a parallel build failure on Darwin 9.6.0 due
+ to the 'ar' 'flock'ing an archive upon extraction, by protecting the
+ extraction of convenience archives with a lock.
+ - The Libtool macro files do not contain instances of __oline__ any more,
+ easing merges for configure scripts that are added to version control.
+ - Fix ancient bug where "-Wc," was turned into "$wl" (typically "-Wl,")
+ when using the compiler driver to link programs. Now "-Wc," is stripped
+ just as it is when linking libraries through the compiler driver.
+ - Symbol versioning works with the GNU gold linker now.
+ - Fixes for detection of shared library dependencies on MinGW systems.
+ - Fixed Sun compiler detection on Solaris with sunCC, sunf77 etc. names.
+
+* Miscellaneous changes:
+
+ - The manual is distributed under the terms of the GNU FDL 1.3 now.
+
+New in 2.2.6 2008-09-05: git version 2.2.5a, Libtool team:
+
+* New features:
+
+ - New lt_dloadvise_preload() call to set a hint that only preloadeded
+ modules can be opened.
+ - libtoolize no longer removes config.guess and config.sub, even when
+ --install is passed.
+
+* Changes in supported systems or compilers:
+
+ - Fixes for ifort on Darwin, and newer Intel compilers (icc 10, ifort 9)
+ on GNU/Linux.
+ - Fixes for cwrapper (cygwin/mingw) under -stdc=c99.
+ - Support cross compile of MinGW with Wine.
+ - Initial support for cegcc (Windows CE/PocketPC) cross compilation.
+ - Initial support for lf95 (Lahey Fortran 8.1) on GNU/Linux.
+
+* Bug fixes:
+
+ - Several testsuite issues have been fixed, thanks to user feedback.
+
+ - Fix 2.2 regression that caused argz symbols to be exported from
+ libltdl unrenamed on systems that do not have working argz.
+
+ - Revert "lt_dlopen(NULL) works on AIX again.". It was not the
+ correct fix.
+
+ - Diagnose '-L' arguments correctly.
+
+ - Libtool no longer tries to open devices as files in execute mode.
+
+ - Libtool no longer removes *.gcno profile information from GCC.
+
+New in 2.2.4: 2008-05-04: git version 2.2.3a, Libtool team:
+
+* New features:
+
+ - New libtoolize option --no-warn, for users that want to continue to
+ use old libtool style without being nagged.
+ - Options --debug, --no-warn, --quiet and --verbose can be passed to
+ libtoolize through the environment variable LIBTOOLIZE_OPTIONS, for
+ cleaner interaction between the user and libtoolize when called by
+ autoreconf.
+
+* Bug fixes:
+
+ - The documentation for lt_dlopenadvise showed the wrong type for
+ the lt_dladvise parameter.
+ - The public declarations for lt_dlhandle and lt_dladvise are now
+ incomplete struct types rather than void*, which means that nearly
+ all casting is eliminated allowing the compiler to provide more
+ type checking.
+ - libtoolize no longer reports up-to-date files that it would have
+ copied, unless --force is passed.
+ - No longer reports that lt~obsolete.m4 needs to be added to aclocal.m4
+ when it is already there.
+ - When 'aclocal' copied the libtool macros directly into 'aclocal.m4'
+ (i.e. AC_CONFIG_MACRO_DIR is not being used), libtoolize no longer
+ reports that all macros need to be added to 'aclocal.m4', and
+ diagnoses only the macro files that are missing or not up-to-date.
+ - libtoolize now advises use of AC_CONFIG_MACRO_DIR to keep matching
+ libtool macros in-tree where appropriate.
+ - libtoolize now advises use of 'ACLOCAL_AMFLAGS = -I m4' (or
+ equivalent) where appropriate, and errors out when ACLOCAL_AMFLAGS
+ names a different directory to AC_CONFIG_MACRO_DIR.
+
+New in 2.2.2: 2008-04-01: CVS version 2.2.1a, Libtool team:
+
+* New features:
+
+ - In compile mode, compiler output occurs in the user locale. This
+ feature has been present in 1.5.26 but not in 2.2.
+
+* Changes in supported systems or compilers:
+
+ - Initial shared library support for AmigaOS4 on powerpc.
+
+* Bug fixes:
+
+ - Fix 2.2 regression in libltdl that causes memory corruption upon
+ repeated 'lt_dlinit(); lt_dlexit()'.
+ - Fix 2.2 regression in libltdl that skipped the dlopen loader if
+ the system also supports other loaders (e.g., Cygwin, HP-UX).
+ - Fix 2.2 regression in that 'libtool --mode=execute CMD ARGS' does not
+ transform ARGS that do not look like shell or C wrappers of libtool
+ programs.
+ - Fix 2.2 regression that kept cross-compiling to w32 from working.
+ - Several testsuite issues have been fixed, thanks to user feedback.
+
+New in 2.2: 2008-03-01; CVS version 2.1c, Libtool team:
+
+* Bug fixes:
+
+ - argz.c, lt__dirent.c and lt__strl.c are correctly distributed with
+ parent projects using nonrecursive libltdl.
+ - libtoolize no longer tries to install libtool files when libltdl is
+ used in a non-autoconf parent package.
+ - Don't add the CXX tag to libtool when there is no C++ compiler, even
+ if AC_PROG_CXX sets a default g++ compiler where no such compiler
+ actually exists.
+ - make distcheck DISTCHECK_CONFIGURE_FLAGS=--disable-ltdl-install
+ works again.
+
+New in 2.1b: 2008-02-01; CVS version 2.1a, Libtool team:
+
+* Important incompatible changes and obsoleted features:
+
+ - Removed deprecated APIs from libltdl: lt_dlcaller_register,
+ lt_dlhandle_next, lt_dlhandle_find, lt_dlforeach, lt_dlmutex_register,
+ lt_dlmutex_lock, lt_dlmutex_unlock, lt_dlmutex_seterror,
+ lt_dlmutex_geterror, lt_dlmalloc, lt_dlrealloc, lt_dlfree.
+ - The Libtool and libltdl macros and the testsuite now assume a C89
+ environment, consequently do not test for headers such as string.h,
+ strings.h, memory.h any more.
+ - Fix regression in libltdl symbol exports on Cygwin. Side effect:
+ LT_GLOBAL_DATA and LT_SCOPE are now explicitly defined as
+ declspec(dllexport), bypassing auto-export logic on Cygwin.
+ This tracks existing behavior on MinGW.
+ - The libtool script has been optimized a bit for more modern shells.
+ This breaks use of the stdin file descriptor in libtool, and can
+ break if a different shell is used to execute the libtool script
+ than the one it was configured for.
+ - The macros AC_ENABLE_SHARED, AC_DISABLE_SHARED, AC_ENABLE_STATIC, and
+ AC_DISABLE_STATIC have been un-deprecated after deprecation in
+ 1.9b.
+ - The macro LT_WITH_LTDL has been renamed to LTDL_INIT.
+ - Fixed a branch-1-5/HEAD regression to only link uninstalled libraries
+ statically with '-static'. In order to compensate for this, there
+ is a new link flag '-static-libtool-libs' to provide the previous
+ '-static' semantics.
+
+* New features:
+
+ - Fix installation of libltdl so that it does not need Autoconf and
+ Automake installed, in order to be usable in another package. This
+ lifts the restrictions introduced in 1.9b.
+ - Default convenience or installable libltdl builds can optionally
+ be declared using new 'convenience' or 'installable' options to the
+ LTDL_INIT macro (as an alternative to individual LTDL_CONVENIENCE
+ or LTDL_INSTALLABLE invocations).
+ - New configure-time options to allow libltdl parent project builder
+ to choose between installed and shipped libltdl, when invoking
+ LTDL_INIT: --with-included-ltdl, --with-ltdl-include,
+ --with-ltdl-lib.
+ - New LT_CONFIG_LTDL_DIR macro to specify a different directory name
+ for a convenience libltdl.
+ - libtoolize has been completely overhauled.
+ - 'libtoolize --install' now also installs 'install-sh'.
+ - New libtoolize options: --non-recursive, --recursive, --subproject.
+ These options control the way libltdl is installed into a package by
+ libtoolize. The new recursive and non-recursive build modes for
+ libltdl don't require a subconfigure any more.
+ The Libtool package itself builds libltdl nonrecursively.
+ - The 'nonrecursive', 'recursive' and 'subproject' libltdl build
+ modes are given as LTDL_INIT options.
+ - New make variable LTDLDEPS for use in output_DEPENDENCIES.
+ - New multi-module-loader safe libltdl handle iteration APIs:
+ lt_dlhandle_iterate, lt_dlhandle_fetch, lt_dlhandle_map.
+ - New lt_dlinterface_register to maintain separation of concerns
+ between modules loaded by different libraries.
+ - New lt_dlopenadvise takes a new lt_dladvise type argument, which
+ lets the caller request local or global symbol visibility from the
+ module loader with lt_dladvise_local and lt_dladvise_global
+ respectively. If neither is given, or if lt_dlopen (or lt_dlopenext)
+ are called, then the system default module symbol visibility is used.
+ - The new lt_dladvise_init/lt_dladvise_destroy based APIs also allow
+ caller requests for a filename extension search with lt_dladvise_ext,
+ and for marking a module unloadable with lt_dladvise_resident.
+ - Allow shell special characters like '$' in source file names, but
+ not in object names, to enhance GCJ support.
+ - An entire new Autotest-based testsuite in addition to the old one.
+ Both testsuites have been made more useful for testing
+ cross-compilers. The new testsuite exposes many more issues, but
+ may also be a little rocky on exotic systems.
+ - In 1.9b, a new variable inherited_linker_flags has been added to the
+ libtool library files. This variable takes flags that should be
+ used by dependent libraries and programs, but that do not fit into
+ 'dependency_libs' for both clarity and backward-compatibility.
+
+* Changes in supported systems or compilers:
+
+ - Removed bitrotted support for xlc on Mac OS X.
+ - Detection of compiler wrappers distcc/ccache and $host_alias prefix.
+ - Basic support for PIE (position-independent executables).
+ - Support for DragonFly BSD, improved support for FreeBSD.
+ - Improved support for GNU/kFreeBSD and GNU/NetBSD.
+ - Support for Interix 3 (Windows SFU) and newer versions.
+ - Support for AIX 6.1.
+ - Improved support for UnixWare.
+ - Initial support for RDOS.
+ - Initial Support for FC (modern Fortran).
+ - Support for Portland Group compiler, the Sun compiler suite on GNU/Linux,
+ and initial support for the IBM compiler suite on GNU/Linux/ppc.
+ - Support for linux-dietlibc ('diet' as well as 'diet-dyn', separately).
+ - Building libltdl with a C++ compiler has been undusted.
+ - On (AIX?,) HP-UX, and OpenBSD, hardcoding has been changed to prefer
+ rpath over absolute dependent library names. This fixes DESTDIR
+ installs, among others, on the non-HP-UX/PA systems.
+ - Use of C++ templates together with shared libraries has been
+ improved on some systems and with some compilers, but is still
+ ongoing work. Feedback is desirable here.
+
+* Bug fixes:
+
+ - Fix libltdl on static platforms.
+ - Search paths with GCC on multilib systems like x86_64 have been fixed.
+ - Fixed a regression that prevented use of libltdl without autotools.
+ - Fix error with -version-info on systems with version_type=none, such
+ as BeOS.
+ - Fix symbol exporting for cases where command line length limits are
+ exceeded.
+ - Improve linking with C++ libraries on Solaris with Sun compiler.
+ - Fix installation of libraries that are required by installation
+ commands such as 'ln' or 'rm'.
+ - More robust parsing of mangled '.la' files inside libltdl, fixing a
+ possible overrun and a crash due to memory exhaustion.
+ - Fix compile command line for gcj on MinGW.
+ - Some configure variables have been renamed to fix caching:
+ lt_prog_compiler_pic_works to lt_cv_prog_compiler_pic_works
+ lt_prog_compiler_static_works to lt_cv_prog_compiler_static_works.
+ - Fix 1.9b regression: lt_dlopen(NULL) works on AIX again.
+ - Loads of smaller bug fixes.
+
+
+New in 1.9f: 2004-10-23; CVS version 1.9e, Libtool team:
+* Fix a regression in 1.9d, where ECHO was always set to 'echo' and the
+ backslash quoting tests were never run.
+* Fix a regression in 1.9d, where progpath was used for --no-reexec before it
+ was set.
+* Fix a regression in 1.9d, which required an installed automake to build the
+ bootstrapped tarball.
+* Fix hanging bug on MinGW.
+
+New in 1.9d: 2004-10-03; CVS version 1.9c, Libtool team:
+* If non-pic objects were not compiled, and libtool is called in link mode,
+ libtool no longer silently creates an empty archive, but rather falls
+ back to pic objects.
+* When compiling C glue code with $LTCC, libtool now saves the setting of
+ $compiler_flags from the C tag, and passes those flags to $LTCC.
+* libtool no longer dies when concurrently creating directories with
+ 'make -j' on multi-processor hosts.
+* Return type, and name parameter of lt_dlloader_remove are no longer
+ 'const'.
+* Name parameter of lt_dlloader_find is no longer 'const'.
+* The API for the slist ADT has been updated: slist_new has been replaced
+ by slist_box; slist_unbox and slist_sort are new; the footprint of
+ slist_remove and slist_fnid have changed; SListCallback and SListCompare
+ types have been exchanged. See libltdl/slist.c for documentation.
+* libltdl is C89 compatible again. lt_dlsymbol type removed, and lt_dlsymlist
+ structure changed to avoid using C99 flexible arrays.
+* Support self dlopening for executables on cygwin and mingw.
+* Improved support for linux-gnu/ia64.
+* Initial support for s390x-ibm-tpf.
+* Fixed some memory leaks in libltdl.
+* Improved support for OpenBSD (use rpath instead of hardcoding absolute
+ file names).
+
+New in 1.9b: 2004-08-29; CVS version 1.5a, Libtool team:
+* The /^_?LT_[A-Z_]+$/ namespace is now reserved for Libtool's own macros.
+ If you have any shell variables in this namespace they will need to be
+ renamed. If you have any macros in this namespace please rename them to
+ prevent any possible future clash with libtool supplied macros.
+* New LT_PREREQ macro for specifying minimum libtool requirement.
+* New LT_INIT interface replaces AC_PROG_LIBTOOL, AC_ENABLE_SHARED,
+ AC_DISABLE_SHARED, AC_ENABLE_STATIC, AC_DISABLE_STATIC,
+ AC_ENABLE_FAST_INSTALL, AC_DISABLE_FAST_INSTALL, AC_LIBTOOL_DLOPEN,
+ AC_LIBTOOL_WIN32_DLL and AC_LIBTOOL_PIC_MODE. Use autoupdate to modernise
+ your configure.ac files after installing this release.
+* New LT_LANG interface to enable libtool support for a specific language.
+* Language support is now only included if your configure.ac enables it,
+ either through a call to AC_PROG_CXX etc. or LT_LANG.
+* The libtool script will complain if it was built from mismatched ltmain.sh
+ and libtool m4 macro versions.
+* Like automake, libtoolize no longer installs config.guess and config.sub by
+ default. Use new --install option to get the old behaviour.
+* libtoolize no longer supports the --ltdl-tar option.
+* libtool script is now created by config.status. Instead of interrogating
+ './libtool' from configure.ac after calling AC_PROG_LIBTOOL, use the
+ variable names directly.
+* libltdl is no longer a self-contained package, and shares configury with
+ the top level directory now.
+* Shared objects (.lo) are no longer created when '-static' is passed in
+ compile mode.
+* New compile mode option '-shared' prevents creation of static objects (.o).
+* New link mode option '-shared' creates only shared libraries at link time.
+* If you configure libtool with --disable-shared (or if libtool does not
+ support shared libraries on your platform) trying to build a library using
+ '-shared' is a fatal error.
+* New link mode option '-weak' tells libtool when not to propagate dependency
+ libraries from dlpreopened modules.
+* libtoolize installs libtool.m4, (ltdl.m4 if used,) and various supporting
+ m4 definitions to AC_CONFIG_MACRO_DIR.
+* Mode inferrence removed, shorthand for choosing modes added.
+* Specifying -allow-undefined is now an error.
+* Speed up max_cmd_len check.
+* libltdl can now preopen modules from within a library, and libtool will
+ accept -dlpreopen options when linking either a shared library or a
+ convenience library.
+* New function in libltdl: lt_dlhandle_find provides access to module handles
+ by module name.
+* New function in libltdl: lt_dlpreload_open opens all preloaded modules.
+* libltdl no longer loads shared libraries with global symbol resolution,
+ this caused problems when the symbols were intended to be overriden further
+ up the stack; it is also not recommended practice.
+* New function in libltdl: lt_dlhandle_first, primes handle iterations (using
+ lt_dlhandle_next) to filter by module interface.
+* libltdl no longer tries to support multi-threaded programming with
+ lt_dlmutex_register(), which was unusable with POSIX threads anyway.
+ The symbols are deprecated but exported for backwards compatibility.
+* libltdl no longer uses lt_dlmalloc, lt_dlrealloc and lt_dlfree. The symbols
+ are still exported for backwards compatibility.
+* The lt_dlinfo struct has a new module field that can be used by dlloaders.
+* libltdl no longer supports pre-c89 compilers. Some of the pre89 portability
+ functions had compile time bugs in them anyway, so you guys can't have been
+ using it :-)
+* make install now deletes preexisting $prefix/share/libtool before installing
+ latest files.
+* Extracting symbols from an import library on cygwin and win32 now works.
+* Initial support for amigaos-ppc.
+* Improved support for OpenBSD.
+* Support for Intel C++ version 8.0.
+* New support for IBM's xlc and xlc++ on Mac OS X.
+* Finished support for QNX RTOS.
+* Bug fixes.
+
+New in 1.5.8: 2004-08-07; CVS version 1.5.7a, Libtool team:
+* Support for Intel C++ version 8.0.
+* Improved support for OpenBSD.
+* Support for xlc on Mac OS X.
+* Better support for zsh as /bin/sh.
+* Much faster check for command line length on all BSD systems.
+* Better Mac OS X/darwin support.
+* Bug Fixes.
+
+New in 1.5.6: 2004-04-11; CVS version 1.5.5a, Libtool team:
+* Installs libltdl files properly in $prefix/share/libtool/libltdl. 1.5.4
+ did not install them at all.
+* libltdl correctly guesses the extension for loadable modules again.
+
+New in 1.5.4: 2004-04-03; CVS version 1.5.3a, Libtool team:
+* Bug fixes.
+
+New in 1.5.2: 2004-01-25; CVS version 1.5.0a, Libtool team:
+* lt_dlrealloc is an official part of the libltdl API.
+* --tag, --silent and --debug options are preserved and reused when libtool
+ calls itself for relinking etc.
+* '-pthread' and similar options are honoured when linking shared libraries.
+* -no-suppress in compile mode shows compiler output for both PIC and non-PIC
+ object compilation.
+* New link mode option '-precious-files-regex' to prevent accidental removal
+ of files you want to keep, such as test coverage data, from the temporary
+ output directory.
+* Directories specified in /etc/ld.so.conf are no longer hardcoded on GNU/Linux.
+* Recognises the 'R' symbol type on Solaris so read-only symbols can be
+ exported.
+* Bug fixes.
+
+New in 1.5.1: 2003-??-??; CVS version 1.5.0a, Libtool team:
+* lt_dlrealloc is an official part of the libltdl API.
+* Bug fixes.
+
+New in 1.5: 2003-04-14; CVS version 1.4e, Libtool team:
+* First stable release of multi-language architecture.
+* libtool and libltdl support for Mac OS/X.
+* libltdl will now use cygwins dlopen API instead of always forcing
+ LoadLibrary.
+* Support auto-import patch to binutils on cygwin for much improved dll
+ support.
+* Bug fixes.
+
+New in 1.4.3: 2002-10-13; CVS version 1.4.2a, Robert Boehne:
+* The libltdl subdirectory now bootstraps correctly with Automake 1.5.
+* srcdir != builddir builds with Automake 1.5 work correctly.
+* Support for mips-compaq-nonstopux.
+* New command line argument, --preserve-dup-deps prevents removal of
+ duplicate dependent libraries.
+
+New in 1.4d: 2002-01-07; CVS version 1.4c, Libtool team:
+* Help strings display correctly again.
+* Better error messages when library linking fails.
+* Better error messages from libltdl when loading fails.
+* Better search path management in libltdl with 'lt_dlinsertsearchdir' call.
+* Support /lib/w32api in recent cygwin releases.
+* Support cross compilation to mingw.
+* Support for .rc files (Windows resource compiler).
+* Improved handling of mingw gcc.
+* Improved handling of $PATH with entries containing spaces.
+* Improved support for linking with gcc on aix4* and aix5*.
+* Improved support for GCC 3.0.
+* Initial support for QNX RTOS, UnixWare 7 and OpenUNIX 8.
+* Bug fixes to the OpenBSD port.
+* Bug fixes.
+
+New in 1.4.2: 2001-09-11; CVS version 1.4.1a, Gary V. Vaughan:
+* libltdl now builds on solaris again
+* diagnose and warn about not-quite-working combinations of gcc and
+ ld on solaris.
+* Improved OpenBSD support.
+* Improved cygwin support.
+* Bugfixes.
+
+New in 1.4.1: 2001-09-03; CVS version 1.4.0a, Libtool team:
+* Better error messages from libltdl when loading fails.
+* Don't leave here-doc files behind.
+* Improved support for OpenBSD.
+* Libtool will build with autoconf-2.50 and higher.
+* Plug memory management bugs in libltdl.
+* Prefer shl_load to dlopen for better operation on HP-UX.
+
+New in 1.4b: 2001-07-09; CVS version 1.4a, Libtool team:
+* Now bootstraps with autoconf-2.50 and automake-1.4-p4.
+* Always try to build at least a static lib, even if both static and
+ shared libs were disabled.
+* Full support for C++ compiler.
+* Support for GNU gcj compiler.
+* libltdl can now load all modules in a given path according to user
+ supplied criteria with 'lt_dlforeachfile' call.
+* Improved support for AIX ia64, djgpp, HPUX, hurd, OpenBSD, sco3.2*.
+* Internal mutex handling no longer has namespace clashes on NCR MP-RAS.
+* New pdemo and tagdemo tests.
+* Bug fixes.
+
+New in 1.4: 2001-04-25; CVS version 1.3e, Libtool team:
+* Support for aix5*.
+* Bugfixes.
+
+New in 1.3d: 2001-04-02; CVS version 1.3c, Libtool team:
+* ltconfig is no more. Generation of libtool happens directly from
+ the configure file.
+* Multithread safe with lt_dlmutex_register callback registration.
+* New -no-install flag to avoid the use of executable wrapper scripts.
+* New --with-pic, -prefer-pic and -prefer-non-pic flags to control
+ the generation of PIC/non-PIC code.
+* Support for hardcoding run-time paths (-R) into libraries.
+* Support -dlopen and -dlpreopen for libraries.
+* Libtool now allows you to link shared libraries against static code.
+* New functions in libltdl:
+ lt_dlgetinfo, lt_dlhandle_next and lt_dlforeach provide access to module
+ specific data in handles.
+ lt_dlcaller_register, lt_dlcaller_set_data and lt_dlcaller_get_data provide
+ management for user storage of per module data.
+ lt_dlloader_next, lt_dlloader_name, lt_dlloader_find, lt_dlloader_add and
+ lt_dlloader_remove can be used for adding new types of module loaders.
+ lt_dladderror, lt_dlseterror integrate user module loaders with lt_dlerror.
+* "-Xcompiler" and "-Wc," does now work in compile mode, too.
+* Support recent dlltool formats.
+* Start of support code for cross-compiling to win32.
+* libltdl can now be built as a dll with win32.
+* m4 macros needed to configure libltdl split out into libltdl/ltdl.m4.
+* New port to NEWS-OS Release 6.
+* Improved support for darwin (rhapsody), mingw32, NetBSD, Compaq Tru64 V5.0
+ and Digital Unix V4.*.
+* Initial support for ia64 linux.
+* Initial support for a.out freebsd shared libs.
+* Initial support for Paul Sokolovsky's pw32 POSIX over win32 layer.
+* Many bugfixes (especially in libltdl)
+
+New in 1.3b: 1999-07-02; CVS version 1.3a, Libtool team:
+* Complete inter-library dependencies support. It's now possible
+ to link libtool libraries against other libtool libraries.
+* Libtool is able to find already-installed libtool libraries,
+ even if they were moved out of their installation directory.
+* New "-Wc,flag" and "-Xcompiler flag" flags to pass flags
+ directly to the compiler
+* New "-Wl,flag" and "-Xlinker flag" flags to pass flags
+ directly to the linker
+* New "-no-fast-install" flag to selectively disable fast-install mode.
+* Support for installing stripped libraries using GNU strip (install -s).
+ Automake >= 1.5 will install stripped libraries with "make install-strip".
+* Allow linking shared libraries against static ones
+ on FreeBSD, GNU/Linux, GNU Hurd and Solaris
+* Support for linking DLLs on Win32
+* New 'clean' mode to delete uninstalled files.
+* New demos and tests
+* Various bugfixes
+
+New in 1.3.5: 2000-05-27, CVS version 1.3.4a, Libtool team:
+* Support for mac OS X (rhapsody).
+* Support for *-sequent-sysv4.
+* Support for Cygwin-1.1.0.
+* Support recent dlltool formats.
+* Bugfixes.
+
+New in 1.3.4: 1999-12-08, CVS version 1.3.3a, Libtool team:
+* Support for Compaq Tru64 V5.0.
+* Improved support for Digital Unix V4.*.
+* Improved support for NetBSD, FreeBSD and Unixware.
+* Many fine bugfixes.
+
+New in 1.3.3: 1999-07-02, CVS version 1.3.2a, Libtool team:
+* New '-dlpreopen force' flag to ensure that
+ lt_preloaded_symbols is always defined.
+* Work around self-dlclose bug in FreeBSD 3.1.
+* Expand convenience libraries when creating reloadable objects.
+* Do not forget to import -L flags of convenience libraries.
+* Do not pass -whole-archive or equivalent to symbol extractor.
+* Create directory to expand convenience libraries only when needed.
+* Improved support for Cygwin, DJGPP and NetBSD
+* Various bugfixes
+
+New in 1.3.2: 1999-05-26, CVS version 1.3.1a, Libtool team:
+* Avoid circular links of objects and libraries.
+* Look for dlerror when dlopen was found in -ldl (typo).
+* Disable shared libraries with broken GNU ld on Solaris.
+
+New in 1.3.1: 1999-05-21, CVS version 1.3.0a, Libtool team:
+* Documentation improvements; recommend automake users to insert libtool.m4
+ in acinclude.m4
+* AC_LIBLTDL_CONVENIENCE and AC_LIBLTDL_INSTALLABLE now set INCLTDL.
+* New port to NEC UX/4800.
+* cygwin-b20.1 passes all tests.
+* Slightly improved BeOS support.
+* Many AIX 4.3.2 test failures have gone.
+* Pass unknown -L arguments through to the linker (for -LANG:* support).
+* Close a security hole with mode 777 directory during libltdl installation.
+* Fixed the infamous 'ifelse' bug in libtool.m4
+
+New in 1.3: 1999-04-29, Libtool team:
+* This is just a summary of the changes since 1.2.
+ See the news of intermediate alpha releases below for details.
+* Support for convenience archives.
+* New maintainers. Anonymous CVS and home page at gnu.org.
+* Portable dlopening interface with libltdl, new -module flag.
+* Correctly link installed libtool libraries into programs and other
+ libtool libraries. Linking of uninstalled libtool libraries into
+ libraries is under development for 1.4.
+* Do not drop library dependencies on platforms that allow them.
+* Linking with uninstalled libraries no longer picks installed ones by
+ mistake.
+* Use libraries from the build tree when running uninstalled
+ executables (may require double linking).
+* Allow developers to optimize for build-tree executions.
+* Support -export-symbols-regex for controlled symbol exporting.
+* Support -R to hardcode directories in library search paths.
+* New ports, demos and tests. Lots of improvements and bug fixes.
+
+New in CVS version 1.2g, Libtool team:
+* AM_PROG_LIBTOOL is smaller and faster
+* AC_LIBTL_L_WIN32_DLL is required in configure.in for libtool to
+ attempt to build dlls on win32 hosts
+* Shared libraries on AmigaOS up to version 4 are now disabled
+ since they don't meet libtool's requirements for shared libraries
+* -L supports now relative directories
+* Libltdl has a new license: LGPL with a special exception
+* Libltdl can be used as stand-alone package
+* dlopen support for BeOS
+* Partial support for Motorola System V 4
+* Improved support for AIX, BeOS, Cygwin, DJGPP, DU, IRIX and HP/UX
+* Documentation updates
+* New tests
+* Bugfixes
+
+New in 1.2f: 1999-03-15; CVS version 1.2e, Libtool team:
+* libtool will correctly link uninstalled libraries into programs
+ and prefer uninstalled libraries to installed ones
+* Library paths that are in the system default run-time search path
+ are no longer hardcoded into executables.
+* New fast installation mode, which links the final executable
+ in order to avoid relinking during installation.
+ Programs in the build-tree are relinked when executed.
+* New AC_DISABLE_FAST_INSTALL macro to set the default for
+ the fast-install mode to disabled
+* New -export-symbols-regex flag, to export symbols selectively by
+ a regular expression
+* Support -R for specifying run-time path of programs and library dependencies
+* New -avoid-version option to avoid versioning for libraries
+* libtool module names no longer need to have a "lib" prefix
+ (requires automake 1.4).
+* New -thread-safe flag, to build thread-safe libraries
+* Major improvements in libltdl: API documentation, installable version,
+ support for module search paths, support for lt_dlopen(0),
+ can be embedded into packages as a tar file (libltdl.tar.gz),
+ dynamic buffer allocation and buffer overflow checks,
+ new macro LTDL_SET_PRELOADED_SYMBOLS() which must be used in the
+ main program, dynamic memory allocation functions are user-defineable
+* New AC_LIBLTDL_CONVENIENCE and AC_LIBLTDL_INSTALLABLE macros, to select
+ convenience and/or installable versions of libltdl.
+* libltdl is now built and installed unless --disable-ltdl-install
+* New "-dlopen self" flag for dlopening the executable itself
+* New AC_LIBTOOL_DLOPEN macro to check for dlopen support,
+ required if you use -dlopen or -dlpreopen
+* If libtool could not satisfy all dependencies of a module
+ it will only build a static version of it
+* dld_preloaded_symbols was renamed to lt_preloaded_symbols
+* Support for BeOS
+* Improved support for FreeBSD, AIX, IRIX, OSF, SysV 4.3, HP/UX, DJGPP
+ BSD/OS 4.x and NetBSD
+* In order for libtool to attempt to link a shared library (dll) on win32
+ platforms, you must pass the -no-undefined flag to libtool in link mode.
+* The path to GNU ld now works on cygwin-b18 to cygwin-b20.2 at least.
+* Support for IRIX library versioning.
+* New demos and tests
+* Various bugfixes
+
+New in 1.2d: 1998-12-16; CVS version 1.2c, Libtool team:
+* libtool will correctly link already-installed libraries into programs.
+* New -module flag, to create loadable modules.
+* New libltdl, a small library for portable dlopening of modules.
+ It is still undocumented, but you can already find some examples in:
+* New mdemo directory, with tests of -module and dlopening examples.
+ Be aware that libltdl is only known to work on a few platforms such as
+ GNU/Linux and Solaris2. Some mdemo tests are known to FAIL on several
+ other platforms; please ignore these failures by now (or work to fix
+ them :-).
+* Inter-library dependencies patch finally integrated, but there's
+ still much porting to do. See PORTING for details (some plans for the
+ future in mail/deplibs in the CVS tree).
+* New option -export-symbols to control symbol exporting when possible.
+* Fixed -export-dynamic problem with C++ programs in egcs 1.1.
+* New dlpreopen structure.
+* libtool now supports '-c -o' and subdirectories in sources and
+ target object names even in platforms whose compilers do not support
+ this. In this case, file locking occurs to avoid problems with
+ parallel builds.
+* New 'echo' variant that should fix most problems with long command
+ lines and broken printf programs.
+* Support for DG/UX, UnixWare 7.x and FreeBSD 3.0, and improved
+ support for Microsoft Windows
+* Various bugfixes
+* We now have anonymous CVS access to GNU libtool. CVSROOT is
+ :pserver:anoncvs@anoncvs.gnu.org:/gd/gnu/anoncvsroot. The password
+ is empty. The directory is libtool. Check our home-page at
+ http://www.gnu.org/software/libtool/libtool.html for details.
+* Alexandre Oliva, Thomas Tanner and Gary V. Vaughan have taken over
+ the maintenance of libtool.
+* Arguments to ltconfig have been changed to allow creation of a
+ libtool C program, totally unusable as of this release.
+
+New in 1.2b - 1998-07-01, Gordon Matzigkeit:
+* Libtool needs a new maintainer, since Gordon Matzigkeit has quit.
+ If you think you can do the job, send mail to bug-libtool@gnu.org.
+* Bug fixes.
+* Support for libtool convenience archives.
+
+New in 1.2a - 1998-04-19, Gordon Matzigkeit:
+* Bug fixes.
+* ltconfig accepts an '--output' option to specify the name of the
+ generated libtool.
+* New '--debug' flag to turn on shell script tracing for libtool,
+ libtoolize, and ltconfig.
+* Added 'libtool --config' to print out all configuration variables.
+* Support for *-*-hpux11*.
+
+New in 1.2 - 1998-03-20, Gordon Matzigkeit:
+* Minor bug fixes to provide a stable public release.
+* Libtool no longer cseses Solaris printf to barf due to silly
+ 2110-byte static buffers.
+
+New in 1.1 - 1998-03-08, Gordon Matzigkeit:
+* Bug fixes.
+* http://www.profitpress.com/libtool/ is libtool's homepage.
+* 'AM_PROG_LIBTOOL' supports turning shared or static libraries off
+ with the '--enable-shared=PKGS' and '--enable-static=PKGS' configure
+ flags. See (libtool)AM_PROG_LIBTOOL.
+* Use the 'AM_DISABLE_SHARED' or 'AM_DISABLE_STATIC' macros if you
+ wish to modify the default behaviour of 'AM_PROG_LIBTOOL' for your
+ package.
+* New rules for 'AM_PROG_LD' to use gcc's '-print-prog-name' flag in
+ order to find ld, if possible.
+* Suppress duplicate compiler output during 'compile' mode.
+* Deleted 'dlname' mode. Dlopen applications should only use the
+ runtime search method described in (libtool)Finding the dlname.
+* Experimental support for dynamically loaded modules, even on
+ static-only platforms, via new '-dlopen' and '-dlpreopen' link
+ flags.
+* 'compile' mode honours the '-static' flag to prevent libtool
+ from building PIC objects.
+* New 'execute' mode to support debugging uninstalled libtool
+ libraries and executables.
+* '-allow-undefined' is now the default. You can use '-no-undefined'
+ to declare that a shared library is completely self-contained.
+* Inter-library dependencies are automatically handled when linking
+ against an uninstalled '.la' file.
+* New '-all-static' flag to prevent any dynamic linking. The regular
+ '-static' flag now just prevents dynamic linking of libtool libraries.
+* New '-release' flag to encode release numbers into libtool
+ libraries. This breaks binary compatibility, but is useful for
+ libraries whose interfaces change very frequently. See
+ (libtool)Versioning.
+* The '-rpath' flag can be used to hardcode absolute directories when
+ linking executables using libtool.
+* New robust quoting code to handle any metacharacters passed in
+ arguments to libtool commands.
+* Full support for broken collect2 on AIX 3. Shared libraries
+ can now be built with all working versions of GCC on AIX.
+* Shell script speed optimizations for old and buggy /bin/sh systems,
+ such as HP-UX 9 and SunOS 4.1.4.
+* Maybe use '_libs' as a temporary libtool directory instead of '.libs'
+ in order to cope with MS-DOS filenames.
+* Portability fixes for Windows NT.
+* Refuse to create libtool libraries that don't begin with 'lib'.
+ This allows us to correctly handle OSes that don't have the 'lib'
+ prefix by default, such as OS/2.
+* Support for *-*-amigaos*, *-*-os2*, *-*-sysv4.2uw2*, and *-*-uts4*.
+
+New in 1.0 - 1997-07-08, Gordon Matzigkeit:
+* Bug fixes.
+* Better configuration test to find the system linker. The old test
+ was failing because people frequently install GNU ld, but don't
+ necessarily configure GCC to use it.
+* Automake support for Libtool now uses the LTLIBRARIES primary. See
+ the Automake documentation for more information.
+* Added new '--disable-static' flag to disable building static
+ libraries on platforms that have shared libs.
+* New '-allow-undefined' link flag to build shared libs that contain
+ references to unresolved symbols.
+* Removed all support for creating static-only libraries.
+* Basic support for dynamically loaded modules: new '-export-dynamic'
+ linking flag and corresponding 'dlname' mode.
+* New '--features' flag to display configured libtool attributes.
+* Added support for installing libtool objects, both in absolute and
+ relative directories.
+* Support *-*-linux-gnu* as an alias for *-*-linux*.
+* Support for *-*-openbsd* and *-*-freebsd3*.
+
+New in 0.9 - 1997-02-03, Gordon Matzigkeit:
+* Bug fixes.
+* The libtool demo now uses the libm cos(3) function, to demonstrate
+ inter-library dependencies.
+* The PLATFORMS file has been moved to doc/platforms.texi.
+
+New in 0.8 - 1997-01-26, Gordon Matzigkeit:
+* Bug fixes, and more documentation.
+* Basic support for other language compilers (C++, Fortran, and
+ preprocessed assembler).
+* Libtool is now more persistent when linking with the '-static'
+ flag fails.
+* New test for hardcoding system linkers, to verify that libtool
+ neither creates incorrect binaries, nor takes unnecessary
+ precautions while linking against uninstalled shared libraries.
+* For clarity, the demo subdirectory no longer uses ansi2knr, and has
+ been rewritten to avoid ANSI-only constructs.
+* Support for *-*-irix5, *-*-irix6*, and *-*-sco3.2v5*.
+
+New in 0.7 - 1996-12-08, Gordon Matzigkeit:
+* Total rewrite of libtool, along with a new model for library building.
+* Completely rewritten documentation for the new paradigm.
+* Sane handling of broken system linkers, such as the ones on AIX
+ and HP-UX.
+* configure mode is now a separate program, 'ltconfig'
+* The libinfo helper script has been incorporated into the main
+ libtool program.
+* Automatic mode guessing, based on the command line.
+* Full support for Automake 1.2 (including ansi2knr features).
+* Support to create reloadable objects using link mode.
+* Support for new '-static' linking flag.
+* Support for stripping libraries during installation.
+* Library version information is now passed on the command line, not
+ through a version file.
+
+Version 0.6 was never released.
+
+New in 0.5:
+* Disabled install-progs until next version, when it will be correctly
+ implemented.
+* Clearer library versioning documentation. See (libtool)Versioning.
+* Renamed gm_PROG_LIBTOOL to AM_PROG_LIBTOOL
+* Libtool now creates pseudo-objects named foo.lo and pseudo-archives named
+ libfoo.la instead of foo.o and libfoo.a. See the documentation.
+* libtool compile doesn't interfere with user CFLAGS if they don't
+ conflict with the current objtype. From Karl Berry.
+* Created new libinfo helper script.
+* libversion.in files are obsolete -- libtool uses libinfo to read the
+ new LIBINFO files.
+* Libtool is better at finding its config file and helper scripts.
+* Support for *-*-gnu*
+
+New in 0.4:
+* Bug fixes and new regression tests
+* On unsupported configurations, 'libtool configure' demotes OBJTYPES to
+ 'standard' instead of aborting
+* Added new object type, 't', for tcov(1) support
+* Support for *-*-aix3*, *-*-aix4*, *-*-hpux10*, *-*-osf3*, and *-*-solaris2*
+
+New in 0.3:
+* Bug fixes and new regression tests
+* Added new uninstall-libs mode
+* Added a host argument to configure mode
+* Fixed debugging/hyper-optimizing flags conflict (from Karl Berry)
+* Support for --no-whole-archive when needed by GNU ld (from Ulrich Drepper)
+* Implementation of --enable-linktype, --enable-profile, --enable-shared,
+ --enable-static in gm_PROG_LIBTOOL macro
+* New 'libtoolize' program (modeled after GNU gettext's 'gettextize') to help
+ conversion to libtool
+* New ABOUT-LIBS document for inclusion with libtool-supported packages
+
+New in 0.2:
+* Support for *-*-linux
+* Better checking for GNU ld
+* Reimplemented the config file so that it corresponds more closely to the
+ variables listed in (libtool)Porting Libtool.
+* Reimplemented the shared library version scheme. See (libtool)Versioning.
+* Replaced '--config-file' and '--version-file' options with '--confdir'
+* Added new install-libs and install-progs modes
+
+New in 0.1:
+* First release of libtool
+* Support for: *-*-freebsd*, *-*-netbsd*, *-*-sunos4*, *-*-ultrix4*
+--
+
+Copyright (C) 1996, 1998-2019, 2021-2022 Free Software Foundation, Inc.
+
+This file is part of GNU Libtool.
+
+Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved. This file is offered as-is,
+without warranty of any kind.
diff --git a/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/README b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/README
new file mode 100644
index 0000000..0984306
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/README
@@ -0,0 +1,261 @@
+# GNU Libtool
+
+1. Introduction
+===============
+
+[GNU Libtool][libtool] is a generic library support script.
+[Libtool][] hides the complexity of using shared libraries behind a
+consistent, portable interface.
+
+Libtool's home page is:
+
+ http://www.gnu.org/software/libtool/libtool.html
+
+See the file [NEWS][] for a description of recent changes to Libtool.
+
+Please note that you can build GNU Libtool from this directory using a
+vendor Make program as long as this is an official release tarball;
+otherwise you will need GNU Make for sane VPATH support. See the file
+[INSTALL][] for complete generic instructions on how to build and install
+Libtool. Also, see the file [doc/notes.txt][notes] for some platform-
+specific information.
+
+See the info node (libtool)Tested Platforms. (or the file
+[doc/PLATFORMS][platforms]) for a list of platforms that Libtool already
+supports.
+
+Please try it on all the platforms you have access to:
+
+ * If it builds and passes the test suite (`gmake check`), please send
+ a short note to the [libtool mailing list][libtool list] with a
+ subject line including the string `[PLATFORM]`, and containing the
+ details from the end of `./libtool --help` in the body.
+ * Otherwise, see _Reporting Bugs_ below for how to help us fix any
+ problems you discover.
+
+To use Libtool, add the new generic library building commands to your
+`Makefile`, `Makefile.in`, or `Makefile.am`. See the documentation for
+details.
+
+[install]: http://git.savannah.gnu.org/cgit/libtool.git/tree/INSTALL
+[libtool]: http://www.gnu.org/s/libtool
+[libtool list]: mailto:libtool@gnu.org
+[news]: http://git.savannah.gnu.org/cgit/libtool.git/tree/NEWS
+[notes]: http://git.savannah.gnu.org/cgit/libtool.git/tree/doc/notes.texi
+[platforms]: http://git.savannah.gnu.org/cgit/libtool.git/tree/doc/PLATFORMS
+
+
+2. Reporting Bugs
+=================
+
+If this distribution doesn't work for you, before you report the
+problem, at least try upgrading to the latest released version first,
+and see whether the issue persists. If you feel able, you can also
+check whether the issue has been fixed in the development sources for
+the next release (see _Obtaining the Latest Sources_ below).
+
+Once you've determined that your bug is still not fixed in the latest
+version, please send a full report to the libtool [bug mailing list][],
+including:
+
+ 1. the information from the end of the help message given by
+ `./libtool --help`, and the verbose output of any failed tests
+ (see _The Test Suites_ immediately below);
+ 2. complete instructions for how to reproduce your bug, along with
+ the results you were expecting, and how they differ from what you
+ actually see;
+ 3. a workaround or full fix for the bug, if you have it;
+ 4. a copy of `tests/testsuite.log` if you are experiencing failures
+ in the Autotest testsuite.
+ 5. new test cases for the testsuite that demonstrate the bug are
+ especially welcome, and will help to ensure that future releases
+ don't reintroduce the problem - if you're not able to write a
+ complete testsuite case, a simple standalone shell script is
+ usually good enough to help us write a test for you.
+
+If you have any other suggestions, or if you wish to port Libtool to a
+new platform, please send email to the [mailing list][libtool list].
+
+Please note that if you send us an non-trivial code for inclusion in a
+future release, we may ask you for a copyright assignment (for brief
+details see the 'Copyright Assignment' section on our
+[Contributing][contribute] webpage.
+
+[bug mailing list]: mailto:bug-libtool@gnu.org
+[contribute]: http://www.gnu.org/software/libtool/contribute.html
+
+
+3. The Test Suite
+=================
+
+Libtool comes an integrated sets of tests to check that your build
+is sane. You can run like this, assuming that `gmake` refers to GNU
+make:
+
+ gmake check
+
+The new, Autotest-driven testsuite is documented in:
+
+ info Autoconf 'testsuite Invocation'
+
+but simple help may also be obtained through:
+
+ gmake check TESTSUITEFLAGS='--help'
+
+For verbose output, add the flag '-v', for running only a subset of the
+independent tests, merely specify them by number or by keyword, both of
+which are displayed with the '--list' flag. For example, the 'libtool'
+keyword is used for the tests that exercise only this script. So it is
+possible to test an installed script, possibly from a different Libtool
+release, with:
+
+ gmake check \
+ TESTSUITEFLAGS="-k libtool LIBTOOL=/path/to/libtool"
+
+Some tests, like the one exercising `max_cmd_len` limits, make use of
+this to invoke the testsuite recursively on a subset of tests. For these
+tests, the variable `INNER_TESTSUITEFLAGS` may be used. It will be
+expanded right after the `-k libtool`, without separating whitespace, so
+that further limiting of the recursive set of tests is possible. For
+example, to run only the template tests within the `max_cmd_len`, use:
+
+ gmake check TESTSUITEFLAGS="-v -x -k max_cmd_len \
+ INNER_TESTSUITEFLAGS=',template -v -x'"
+
+If you wish to report test failures to the libtool list, you need to
+send the file `tests/testsuite.log` to the [bug mailing list][].
+
+
+4. Obtaining the Latest Sources
+===============================
+
+* With the exception of ancient releases, all official GNU Libtool
+ releases have a detached GPG signature file. With this you can verify
+ that the corresponding file (i.e. without the `.sig` suffix) is the
+ same file that was released by the owner of it's GPG key ID. First,
+ be sure to download both the .sig file and the corresponding release,
+ then run a command like this:
+
+ gpg --verify libtool-x.y.z.tar.gz.sig
+
+ If that command fails because you don't have the required public key,
+ then run this command to import it:
+
+ gpg --keyserver keys.gnupg.net --recv-keys 2983D606
+
+ and then rerun the `gpg --verify` command.
+
+* Official stable releases of GNU Libtool, along with these detached
+ signature files are available from:
+
+ ftp://ftp.gnu.org/gnu/libtool
+
+ To reduce load on the main server, please use one of the mirrors
+ listed at:
+
+ http://www.gnu.org/order/ftp.html
+
+* Alpha quality pre-releases of GNU Libtool, also with detached
+ signature files are available from:
+
+ ftp://alpha.gnu.org/gnu/libtool
+
+ and some of the mirrors listed at:
+
+ http://www.gnu.org/order/ftp.html
+
+* The master libtool repository is stored in git.
+
+ If you are a member of the savannah group for GNU Libtool, a writable
+ copy of the libtool repository can be obtained by:
+
+ git clone @git.sv.gnu.org:/srv/git/libtool.git
+
+ If you are behind a firewall that blocks the git protocol, you may
+ find it useful to use
+
+ git config --global url.http://git.sv.gnu.org/r/.insteadof \
+ git://git.sv.gnu.org/
+
+ to force git to transparently rewrite all savannah git references to
+ use http.
+
+ If you are not a member of the savannah group for GNU Libtool, you can
+ still fetch a read-only copy with either:
+
+ git clone git://git.sv.gnu.org/libtool.git
+
+ or using the CVS pserver protocol:
+
+ cvs -d:pserver:anonymous@pserver.git.sv.gnu.org:/srv/git/libtool.git \
+ co -d libtool HEAD
+
+* Before you can build from git, you need to bootstrap. This requires:
+ - Autoconf 2.64 or later
+ - Automake 1.11.1 or later
+ - Help2man 1.29 or later
+ - Xz 4.999.8beta or later (from [tukaani.org](http://tukaani.org/xz))
+ - Texinfo 4.8 or later
+ - Any prerequisites of the above (such as m4, perl, tex)
+
+ Note that these bootstrapping dependencies are much stricter than
+ those required to use a destributed release for your own packages.
+ After installation, GNU Libtool is designed to work either standalone,
+ or optionally with:
+ - Autoconf 2.59 or later
+ - Automake 1.9.6 or later
+
+* The `bootstrap` script sets up the source directory for you to hack.
+
+
+5. Version Numbering
+====================
+
+People have complained that they find the version numbering scheme under
+which libtool is released confusing... so we've changed it!
+
+It works like this:
+
+ .
+
+Releases with a **major-number** less than 1 were not yet feature
+complete. Releases with a **major-number** of 1 used the old numbering
+scheme that everyone disliked so much. Releases with a **major-number**
+of 2 us the new scheme described here. If libtool ever undergoes a
+major rewrite or substantial restructuring, the **major-number** will be
+incremented again.
+
+If we make a patch release to fix bugs in a stable release, we use a
+third number, so:
+
+ 2.4.2
+
+If we make an alpha quality prerelease, we use a fourth number for the
+number of changsets applied since the version it's based on:
+
+ 2.4.2.418
+
+And finally, if you build an unreleased version it will have a short git
+revision hash string in hexadecimal appended to all of that:
+
+ 2.4.2.418.3-30eaa
+
+--
+ Copyright (C) 2004-2010, 2015-2019, 2021-2022 Free Software
+ Foundation, Inc.
+
+ Written by Gary V. Vaughan, 2004
+
+ This file is part of GNU Libtool.
+
+Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved. This file is offered as-is,
+without warranty of any kind.
+
+
+Local Variables:
+mode: text
+fill-column: 72
+End:
+vim:tw=72
diff --git a/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/THANKS b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/THANKS
new file mode 100644
index 0000000..fa5f6ee
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libtool-2.4.7/THANKS
@@ -0,0 +1,342 @@
+These people have contributed to GNU Libtool. Some have reported problems,
+others have contributed improvements to the documentation and actual code.
+The particular contributions are described in the version control logs and
+ChangeLog files. If your name has been left out, if you'd rather not be
+listed, or if you'd prefer a different address be used, please send a
+note to the bug-report mailing list (as seen at end of e.g., libtool --help).
+
+##
+aakropotkin alex.ameen.tx@gmail.com
+Akim Demaille akim@epita.fr
+Alan Hourihane alanh@fairlite.co.uk
+Alan Modra amodra@bigpond.net.au
+Alan W. Irwin irwin@beluga.phys.uvic.ca
+Albert Cheng acheng@ncsa.uiuc.edu
+Albert Chin-A-Young china@thewrittenword.com
+Alex Ameen alex.ameen.tx@gmail.com
+Alexander Hass alexander.hass@sap.com
+Alexander Shevchenko sav_ix@ukr.net
+Alexandre Duret-Lutz adl@gnu.org
+Alexei Sheplyakov varg@theor.jinr.ru
+Alex Potapenko opotapeno@gmail.com
+Alfred M. Szmidt ams@kemisten.nu
+Allan McRae allan@archlinux.org
+Allan Sandfeld Jensen snowwolf@one2one-networks.com
+Alon Bar-Lev alon.barlev@gmail.com
+Andreas Jaeger aj@suse.de
+Andreas Schiffler aschiffler@ferzkopp.net
+Andreas Schwab schwab@linux-m68k.org
+Andrew C. Feren aferen@CetaceanNetworks.com
+Andrew Suffield asuffield@debian.org
+Andrey Slepuhin pooh@msu.ru
+Aneesh Kumar K.V kvaneesh@hotmail.com
+Anthony Green green@redhat.com
+Archie Cobbs archie@whistle.com
+Arkadiusz Miśkiewicz arekm@maven.pl
+Arne Woerner woerner@mediabase-gmbh.de
+Assar Westerlund assar@sics.se
+Bart Van Assche bvanassche@acm.org
+Benjamin Reed ranger@befunk.com
+Bernhard Fischer spam.protected
+Bernhard Rosenkraenzer bero@redhat.de
+Bernhard Voelker mail@bernhard-voelker.de
+Bert Driehuis bert_driehuis@compuware.com
+Bert Wesarg bert.wesarg@googlemail.com
+Bob McElrath bob+libtool@mcelrath.org
+Boyd Lynn Gerber gerberb@zenez.com
+Brad brad@comstyle.com
+Brad Smith brad@comstyle.com
+Brent Leback brent.leback@st.com
+Brian Barrett brbarret@osl.iu.edu
+Brian W. Barrett bbarrett@lanl.gov
+Brice De Bruyne bricedb@gmail.com
+Brook Moses bmoses@google.com
+Brooks Moses bmoses@google.com
+Bruce Korb bkorb@gnu.org
+Bruno Haible bruno@clisp.org
+Camilo La Rota camilo.larota@ens-lyon.fr
+Carl D. Roth roth@cse.ucsc.edu
+Chad Cunningham ccunning@math.ohio-state.edu
+Chris Demetriou cgd@google.com
+Chris Lattner sabre@skylab.org
+Chris P. Ross cross@eng.us.uu.net
+Christiaan Welvaart cjw@daneel.dyndns.org
+Christian Biesinger cbiesinger@web.de
+Christian Cornelssen ccorn@cs.tu-berlin.de
+Christian Rössel christian.roessel@gmx.de
+Christoph Egger Christoph_Egger@gmx.de
+Christopher A. Knight chriskn@crt.com
+Christopher Hulbert cchgroupmail@gmail.com
+Christopher Pfisterer cp@chrisp.de
+Christoph Pfisterer cp@chrisp.de
+Craig Dooley xlnxminusx@gmail.com
+Craig Tierney Craig.Tierney@noaa.gov
+Cristophe Jarry christophe.jarry@ouvaton.org
+Dalibor Topic robilad@kaffe.org
+Daniel Harvey daniel@amristar.com.au
+Daniel Kobras kobras@linux.de
+Daniel Reed djr@redhat.com
+Daniel Richard G. skunk@iSKUNK.ORG
+Dan McMahill mcmahill@mtl.mit.edu
+Dan McNichol mcnichol@austin.ibm.com
+Dave Brolley brolley@redhat.com
+Dave Korn dave.korn.cygwin@googlemail.com
+Dave Vasilevsky thevas@mac.com
+Dave Yost Dave@Yost.com
+David 'Digit' Turner digit@google.com
+David Edelsohn dje.gcc@gmail.com
+David Heine dlheine@truffle.Stanford.EDU
+David Jones jones@mosaid.com
+Derek R. Price derek@ximbiot.com
+Dirk Mueller dmueller@suse.de
+DJ Delorie dj@delorie.com
+Donald Anderson dda@world.std.com
+Donald D. Anderson dda@sleepycat.com
+Donn Washburn n5xwb@comcast.net
+Doug Evans devans@casey.cygnus.com
+Ed Maste emaste@freebsd.org
+Edouard G. Parmelan Edouard.Parmelan@France.NCR.COM
+Edward M. Lee tailbert@yahoo.com
+Elizabeth Barham soggytrousers@yahoo.com
+Erez Zadok ezk@cs.columbia.edu
+Eric Bavier bavier@cray.com
+Eric Blake ebb9@byu.net
+Eric Estievenart eric@via.ecp.fr
+Eric Lindahl erik@theophys.kth.se
+Erik van Pienbroek erik-gnu@vanpienbroek.nl
+Ethan Mallove ethan.mallove@sun.com
+Fabian Groffen grobian@gentoo.org
+Frank Ch. Eigler fche@cygnus.com
+Fred Cox sailorfred@yahoo.com
+Fred Fish fnf@be.com
+Fredrik Estreen estreen@algonet.se
+Fritz Elfert felfert@to.com
+Gary Kumfert kumfert@llnl.gov
+Geoffrey Keating geoffk@apple.com
+George Bosilca bosilca@cs.utk.edu
+Gerald Pfeifer gerald@pfeifer.com
+Greg Eisenhauer eisen@cc.gatech.edu
+Guido Draheim guidod-2001q3@gmx.de
+Henning Nielsen Lund hnl_dk@amigaos.dk
+Hiroyuki Sato hiroysato@gmail.com
+H.J. Lu hjl@gnu.org
+Howard Chu hyc@highlandsun.com
+Ian Lance Taylor ian@cygnus.com
+Ingo Weinhold ingo_weinhold@gmx.de
+Jacob Meuser jakemsr@jakemsr.com
+Jakub Bogusz qboosh@pld-linux.org
+Jakub Jelinek jakub@redhat.com
+James E Wilson wilson@specifixinc.com
+James Su james.su@gmail.com
+Jan Engelhardt jengelh@inai.de
+Jan Kratochvil project-libtool@jankratochvil.net
+Jay Krell jay.krell@cornell.edu
+Jean-Frederic Clere jfrederic.clere@fujitsu-siemens.com
+Jeff Squyres jsquyres@cisco.com
+Jens Petersen petersen@redhat.com
+Jeremie LE HEN tataz@sitadelle.com
+Jeremy C. Reed reed@reedmedia.net
+Jeremy Huddleston Sequoia jeremyhu@macports.org
+Jim Meyering jim@meyering.net
+Jim Pick jim@kaffe.org
+Jim Tison jtison@us.ibm.com
+Jiro Takabatake jiro@din.or.jp
+Joakim Tjernlund joakim.tjernlund@transmode.se
+Joel N. Weber II devnull@gnu.org
+Joe Orton joe@manyfish.co.uk
+Joerg Sonnenberger joerg@netbsd.org
+John Bowler jbowler@acm.org
+John David Anglin dave.anglin@nrc-cnrc.gc.ca
+John R. Cary cary@txcorp.com
+John Wehle john@feith.com
+John Wolfe jlw@sco.com
+Jon Meredith jonm@alchemetrics.co.uk
+Joseph Beckenbach III jrb3@best.com
+Joseph Prostko joe.prostko@gmail.com
+Juergen Reuter reuter@t00pcx17094.desy.de
+Jürgen Reuter juergen.reuter@physik.uni-freiburg.de
+Justin Lecher jlec@gentoo.org
+Karl Berry karl@freefriends.org
+Kean Johnston jkj@sco.com
+Keith Packard keithp@keithp.com
+Ken Block block@zk3.dec.com
+Kenneth Albanowski kjahds@kjahds.com
+Kevin P. Fleming kpfleming@backtobasicsmgmt.com
+Kevin Ryde user42@zip.com.au
+Khem Raj raj.khem@gmail.com
+KO Myung-Hun komh78@gmail.com
+Kurt D. Zeilenga Kurt@OpenLDAP.Org
+Kurt Roeckx kurt@roeckx.be
+Lawrence Velázquez larryv@macports.org
+Leif Ekblad leif@rdos.net
+Lennart Poettering lennart@poettering.net
+Lionel Landwerlin llandwerlin@gmail.com
+Loren James Rittle rittle@latour.rsch.comm.mot.com
+Lucas Holt luke@foolishgames.com
+Maciej Helminiak dion2@wp.pl
+Maciej W. Rozycki macro@ds2.pg.gda.pl
+Mahesh Narayanamurthi mahesh.mach@gmail.com
+Makoto Ishisone ishisone@sra.co.jp
+Manfred Weichel Manfred.Weichel@pdb.siemens.de
+Manish Singh yosh@gimp.org
+Marcel Loose loose@astron.nl
+Marc Espie espie@nerim.net
+Marc Glisse marc.glisse@inria.fr
+Marc J. Fraioli fraioli@dg-rtp.dg.com
+Marcus Comstedt marcus@mc.pp.se
+Marius Vollmer mvo@zagadka.de
+Mark Kettenis kettenis@gnu.org
+Markus Duft markus.duft@salomon.at
+Markus F.X.J. Oberhumer markus@oberhumer.com
+Martin Doucha doucha@integri.cz
+Masahiro Nobori nobori@ss.titech.ac.jp
+Mats Rynge rynge@isi.edu
+Matthieu Herrb matthieu.herrb@laas.fr
+Matthijs Kooijman matthijs@stdin.nl
+Max Bowsher maxb@ukf.net
+Michael Forster email@michael-forster.de
+Michael Haubenwallner michael.haubenwallner@salomon.at
+Michael Matz matz@ifh.de
+Michael Pruett michael@68k.org
+Michael Schmitz mschmitz@iname.com
+Michael Tiemann tiemann@cygnus.com
+Micheal E. Faenza mfaenza@mitre.org
+Mike Frysinger vapier@gentoo.org
+Mike Gorchak lestat@i.com.ua
+Mike Miller mtmiller@ieee.org
+Mike Stump mrs@apple.com
+Mikhail Zabaluev mikhail.zabaluev@gmail.com
+Misty De Meo misty@brew.sh
+Mocha netbsd_alpha@yahoo.com
+Mo DeJong mdejong@redhat.com
+Morten Eriksen mortene@sim.no
+Mumit Khan khan@xraylith.wisc.edu
+Naofumi Yasufuku naofumi@yasufuku.net
+Nick Bowler nbowler@draconx.ca
+Nick Hudson nick@nthcliff.demon.co.uk
+Nick Rasmussen nick@jive.org
+NIIBE Yutaka gniibe@m17n.org
+Nix nix@esperi.org.uk
+Noah Misch noah@cs.caltech.edu
+Norihiro Tanaka noritnk@kcn.ne.jp
+Olaf Lenz olenz@fias.uni-frankfurt.de
+Olivier Blin olivier.blin@softathome.com
+Ollie Wild aaw@google.com
+Olly Betts olly@muscat.co.uk
+Ondřej Bílka neleai@seznam.cz
+Ozkan Sezer sezeroz@gmail.com
+Pádraig Brady P@draigBrady.com
+Paolo Bonzini bonzini@gnu.org
+Patrice Fromy patrice.fromy@u-psud.fr
+Patrick Welche prlw1@newn.cam.ac.uk
+Paul Berrevoets paul@swi.com
+Paul Biggar paul.biggar@gmail.com
+Paul Eggert eggert@cs.ucla.edu
+Paul Laight plaight@quantxautomation.co.uk
+Paul Seidler sepek@lavabit.com
+Paul Sokolovsky Paul.Sokolovsky@technologist.com
+Pavel (Pasha) Shamis shamisp@ornl.gov
+Pavel Raiskup praiskup@redhat.com
+Pavel Roskin pavel_roskin@geocities.com
+Paweł Daniluk pawel@bioexploratorium.pl
+Per Bothner per@bothner.com
+Peter Breitenlohner peb@mppmu.mpg.de
+Peter Eisentraut peter_e@gmx.net
+Peter Ekberg peda@axentia.se
+Peter Fritzsche peter.fritzsche@gmx.de
+Peter Jeremy peterjeremy@optushome.com.au
+Peter Johansson trojkan@gmail.com
+Peter Kjellerstedt peter.kjellerstedt@axis.com
+Peter Rosin peda@lysator.liu.se
+Philip Allison philip.allison@smoothwall.net
+Pierre Ossman ossman@ossman.lkpg.cendio.se
+Rainer Emrich r.emrich@de.tecosim.com
+Rainer Orth ro@CeBiTec.Uni-Bielefeld.DE
+Rainer Tammer tammer@tammer.net
+Raja R Harinath harinath@cs.umn.edu
+Ralf Menzel menzel@ls6.cs.uni-dortmund.de
+Ralph Schleicher rs@nunatak.allgaeu.org
+Reid Spencer reid@x10sys.com
+Reuben Thomas rrt@sc3d.org
+Richard B. Kreckel kreckel@ginac.de
+Richard Dawe rich@phekda.freeserve.co.uk
+Richard Moseley dickie.moseley@virgin.net
+Richard Palo richard.palo@baou.fr
+Richard Purdie rpurdie@rpsys.net
+Richard Sandiford richards@transitive.com
+Richard W.M. Jones rjones@redhat.com
+Rico Tzschichholz ricotz@ubuntu.com
+Robert Garron Robert.Garron@Access3000.net
+Robert Millan rmh@aybabtu.com
+Roberto Bagnara bagnara@cs.unipr.it
+Robert Ögren lists@roboros.com
+Robert Yang liezhi.yang@windriver.com
+Roger Cornelius rac@tenzing.org
+Roland Mainz roland.mainz@nrubsig.org
+Roumen Petrov bugtrack@roumenpetrov.info
+Rudolf Leitgeb r.leitgeb@x-pin.com
+Ryan Hill dirtyepic@gentoo.org
+Ryan Schmidt libtool@ryandesign.com
+Sam Thursfield ssssam@gmail.com
+Samuel Meder meder@mcs.anl.gov
+Samuel Thibault samuel.thibault@ens-lyon.org
+Sascha Schumann sascha@schumann.cx
+Scott McCreary scottmc2@gmail.com
+Sebastian Wilhelmi wilhelmi@ira.uka.de
+Simon Josefsson jas@extundo.com
+Stacey Marshall stacey.marshall@oracle.com
+Stas Maximov smaximov@ieee.org
+Stefan Nordhausen nordhaus@informatik.hu-berlin.de
+Stefan Sperling stsp@elego.de
+Stepan Kasal kasal@ucw.cz
+Stephane Conversy Stephane.Conversy@lri.fr
+Stephan Kulow coolo@kde.org
+Steve Ellcey sellcey@mips.com
+Steven M. Schultz sms@moe.2bsd.com
+Steve Price sprice@hiwaay.net
+Svante Signell srs@kth.se
+Sven Verdoolaege skimo@liacs.nl
+Syd Polk spolk@redhat.com
+Terry D. Dontje Terry.Dontje@Sun.COM
+Thorsten Glaser tg@66h.42h.de
+Tijl Coosemans tijl@FreeBSD.org
+Tilman Koschnick til@subnetz.org
+Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu
+Timothy Wall twall@oculustech.com
+Tim Rice tim@multitalents.net
+Tim Van Holder tim.van.holder@pandora.be
+Titus von Boxberg titus@v9g.de
+Tobias Stoeckmann tobias@stoeckmann.org
+Todd C. Miller Todd.Miller@courtesan.com
+Todd Vierling tv@duh.org
+Tod Milam tmilam@traclabs.com
+Tom Kacvinsky tjk@ams.org
+Tom Tromey tromey@cygnus.com
+Tony Wyatt wyattaw@optushome.com.au
+Tor Lillqvist tml@iki.fi
+Török Edwin edwintorok@gmail.com
+Toshio Kuratomi badger@prtr-13.ucsc.edu
+Ulrich Drepper drepper@ipd.info.uni-karlsruhe.de
+Utz-Uwe Haus haus@mail.math.uni-magdeburg.de
+Václav Haisman vhaisman@gmail.com
+Václav Zeman vhaisman@gmail.com
+Vadim vadim@olly.ru
+Vadim Zeitlin vz-libtool@zeitlins.org
+Vincent Lefevre vincent@vinc17.net
+Vincent Torri doursse@users.sf.net
+Vladimir Kushnir kushn@mail.kar.net
+Volker Christian voc@soft.uni-linz.ac.at
+Warren Dodge warren.l.dodge@Tektronix.com
+Wesley W. Terpstra terpstra@ito.tu-darmstadt.de
+Wilfredo Sanchez wsanchez@apple.com
+William M. Perry wmperry@aventail.com
+Xavier Pianet xavier@xingo.com
+Xin Li
+Xin LI d@delphij.net
+Yaakov Selkowitz yselkowitz@users.sourceforge.net
+Дилян Палаузов dilyan.palauzov@aegee.org
+Юрий Андреевич Пухальский pooh@cryptopro.ru
+
+;; Local Variables:
+;; coding: utf-8
+;; End:
diff --git a/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/AUTHORS b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/AUTHORS
new file mode 100644
index 0000000..8f91512
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/AUTHORS
@@ -0,0 +1,202 @@
+Copyright © 2001 Johannes Erdfelt
+Copyright © 2007-2009 Daniel Drake
+Copyright © 2010-2012 Peter Stuge
+Copyright © 2008-2016 Nathan Hjelm
+Copyright © 2009-2013 Pete Batard
+Copyright © 2009-2013 Ludovic Rousseau
+Copyright © 2010-2012 Michael Plante
+Copyright © 2011-2013 Hans de Goede
+Copyright © 2012-2013 Martin Pieuchot
+Copyright © 2012-2013 Toby Gray
+Copyright © 2013-2018 Chris Dickens
+
+Other contributors:
+Aaron Luft
+Adam Korcz
+Adrian Bunk
+Adrien Destugues
+Akshay Jaggi
+Alan Ott
+Alan Stern
+Aleksandr Mezin
+Alexander Pyhalov
+Alexander Schlarb
+Alexander Stein
+Alex Vatchenko
+Andrew Aldridge
+Andrew Fernandes
+Andrew Goodney
+Andy Chunyu
+Andy McFadden
+Angus Gratton
+Anil Nair
+Ankur Verma
+Anthony Clay
+Antonio Ospite
+Artem Egorkine
+Aurelien Jarno
+Axel Gembe
+Aymeric Vincent
+Baruch Siach
+Bastien Nocera
+Bei Zhang
+Bence Csokas
+Benjamin Berg
+Benjamin Dobell
+Bohdan Tymkiv
+Brent Rector
+Bruno Harbulot
+Carl Karsten
+Christophe Zeitouny
+Chris Zhu
+Chunyu Xie
+Colin Walters
+Craig Hutchinson
+Dave Camarillo
+David Engraf
+Davidlohr Bueso
+David Moore
+Dmitry Fleytman
+Dmitry Kostjuchenko
+Dmitry Zakablukov
+Doug Johnston
+Evan Hunter
+Evan Miller
+Fabrice Fontaine
+Federico Manzan
+Felipe Balbi
+Florian Albrechtskirchinger
+Francesco Montorsi
+Francisco Facioni
+Frank Li
+Frederik Carlier
+Freek Dijkstra
+Gaurav Gupta
+Graeme Gill
+Greg Kroah-Hartman
+Gustavo Zacarias
+Haidong Zheng
+Hans Ulrich Niedermann
+Harry Mallon
+Hector Martin
+Hoi-Ho Chan
+Ido Yariv
+Igor Anokhin
+Ihor Dutchak
+Ilya Konstantinov
+Jakub Klama
+James Hanko
+Jeffrey Nichols
+Jie Zhang
+Jim Chen
+Johann Richard
+John Keeping
+John Sheu
+Jonas Malaco
+Jonathon Jongsma
+Joost Muller
+Josh Gao
+Joshua Blake
+Joshua Hou
+Juan Cruz Viotti
+Julian Scheel
+Justin Bischoff
+Karsten Koenig
+Keith Ahluwalia
+Kenjiro Tsuji
+Kimura Masaru
+Konrad Rzepecki
+Kuangye Guo
+Lars Kanis
+Lars Wirzenius
+Lei Chen
+Léo Lam
+Liang Yunwang
+Luca Longinotti
+Luz Paz
+Mac Wang
+Marco Trevisan (Treviño)
+Marcus Meissner
+Mark Kuo
+Markus Heidelberg
+Martin Ettl
+Martin Koegler
+Martin Ling
+Martin Thierer
+Mathias Hjärtström
+Matthew Stapleton
+Matthias Bolte
+Michael Dickens
+Michel Zou
+Mike Frysinger
+Mikhail Gusarov
+Mikolaj Kucharski
+Morgan Leborgne
+Moritz Fischer
+Nancy Li
+Nia Alarie
+Nicholas Corgan
+Omri Iluz
+Orin Eman
+Ozkan Sezer
+Patrick Stewart
+Paul Cercueil
+Paul Fertser
+Paul Qureshi
+Pekka Nikander
+Philémon Favrod
+Pino Toscano
+Rob Walker
+Romain Vimont
+Roman Kalashnikov
+Ryan Hileman
+Ryan Schmidt
+Saleem Rashid
+Sameeh Jubran
+Sean McBride
+Sebastian Pipping
+Sebastian von Ohr
+Sergey Serb
+Shawn Hoffman
+Simon Haggett
+Simon Newton
+Slash Gordon
+Stefan Agner
+Stefan Tauner
+Steinar H. Gunderson
+Stephen Groat
+Theo Buehler
+Thomas Röfer
+Tim Hutt
+Tim Roberts
+Tobias Klauser
+Toby Peterson
+Tormod Volden
+Trygve Laugstøl
+Uri Lublin
+Uwe Bonnes
+Vasily Khoruzhick
+Vegard Storheil Eriksen
+Venkatesh Shukla
+Vianney le Clément de Saint-Marcq
+Victor Toso
+Vinicius Tinti
+Vitali Lovich
+Vladimir Beloborodov
+William Orr
+William Skellenger
+Xiaofan Chen
+Yegor Yefremov
+Zhiqiang Liu
+Zoltán Kovács
+Сергей Валерьевич
+Ларионов Даниил
+Роман Донченко
+jonner
+orbitcowboy
+osy
+parafin
+RipleyTom
+Seneral
+saur0n
+winterrace
diff --git a/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/COPYING b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/COPYING
new file mode 100644
index 0000000..5ab7695
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/COPYING
@@ -0,0 +1,504 @@
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ c) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ d) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ e) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ , 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
+
+
diff --git a/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/NEWS b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/NEWS
new file mode 100644
index 0000000..4fc85af
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/NEWS
@@ -0,0 +1,2 @@
+For the latest libusb news, please refer to the ChangeLog file, or visit:
+http://libusb.info
diff --git a/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/README b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/README
new file mode 100644
index 0000000..f72faae
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/libusb-1.0.26/README
@@ -0,0 +1,28 @@
+# libusb
+
+libusb is a library for USB device access from Linux, macOS,
+Windows, OpenBSD/NetBSD, Haiku and Solaris userspace.
+It is written in C (Haiku backend in C++) and licensed under the GNU
+Lesser General Public License version 2.1 or, at your option, any later
+version (see COPYING).
+
+libusb is abstracted internally in such a way that it can hopefully
+be ported to other operating systems. Please see the PORTING
+file for more information.
+
+libusb homepage:
+http://libusb.info/
+
+Developers will wish to consult the API documentation:
+http://api.libusb.info
+
+Use the mailing list for questions, comments, etc:
+http://mailing-list.libusb.info
+
+- Hans de Goede
+- Xiaofan Chen
+- Ludovic Rousseau
+- Nathan Hjelm
+- Chris Dickens
+
+(Please use the mailing list rather than mailing developers directly)
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/AUTHORS b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/AUTHORS
new file mode 100644
index 0000000..2a989f3
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/AUTHORS
@@ -0,0 +1,12 @@
+Dominic Rath
+Magnus Lundin
+Michael Fischer
+Spencer Oliver
+Carsten Schlote
+Øyvind Harboe
+Duane Ellis
+Michael Schwingen
+Rick Altherr
+David Brownell
+Vincint Palatin
+Zachary T Welch
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/AUTHORS.ChangeLog b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/AUTHORS.ChangeLog
new file mode 100644
index 0000000..b2b5e6b
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/AUTHORS.ChangeLog
@@ -0,0 +1,10 @@
+drath:Dominic Rath
+mlu:Magnus Lundin
+mifi:Michael Fischer
+ntfreak:Spencer Oliver
+duane:Duane Ellis
+oharboe:Øyvind Harboe
+kc8apf:Rick Altherr
+zwelch:Zachary T Welch
+vpalatin:Vincent Palatin
+bodylove:Carsten Schlote
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/COPYING b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/COPYING
new file mode 100644
index 0000000..0e8db92
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/COPYING
@@ -0,0 +1,16 @@
+OpenOCD is provided under:
+
+ SPDX-License-Identifier: GPL-2.0-or-later
+
+Being under the terms of the GNU General Public License version 2 or
+later, according with:
+
+ LICENSES/preferred/GPL-2.0
+
+In addition, other licenses may also apply. Please see:
+
+ LICENSES/license-rules.txt
+
+for more details.
+
+All contributions to OpenOCD are subject to this COPYING file.
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS
new file mode 100644
index 0000000..9db6c5f
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS
@@ -0,0 +1,35 @@
+This file includes highlights of the changes made in the OpenOCD
+source archive release.
+
+JTAG Layer:
+
+Boundary Scan:
+
+Target Layer:
+
+Flash Layer:
+
+Board, Target, and Interface Configuration Scripts:
+
+Server Layer:
+
+RTOS:
+
+Documentation:
+
+Build and Release:
+
+
+This release also contains a number of other important functional and
+cosmetic bugfixes. For more details about what has changed since the
+last release, see the git repository history:
+
+http://sourceforge.net/p/openocd/code/ci/v0.x.0/log/?path=
+
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.10.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.10.0
new file mode 100644
index 0000000..e3b1e25
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.10.0
@@ -0,0 +1,155 @@
+This file includes highlights of the changes made in the OpenOCD
+source archive release.
+
+JTAG Layer:
+ * New driver for J-Link adapters based on libjaylink
+ (including support for FPGA configuration, SWO and EMUCOM)
+ * FTDI improvements to work at 30MHz clock
+ * BCM2835 native driver SWD and Raspberry Pi2 support
+ * BCM2835 is set to 4ma drive, slow slew rate
+ * ixo-usb-jtag (emulation of an Altera Bus Blaster I on
+ Cypress FX2 IC) support
+ * JTAG pass-through mode for CMSIS-DAP (including support for
+ FPGA configuration)
+ * OpenJTAG support for Cypress CY7C65215
+ * connect_assert_srst support for SWD
+ * Xilinx Virtex-II Series7 bitstream loading support
+ * Use JEP106 data to decode IDs
+ * Deprecated "ft2232" driver removed (use "ftdi" instead)
+ * GPL-incompatible FTDI D2XX library support dropped (Presto,
+ OpenJTAG and USB-Blaster I are using libftdi only now)
+ * ZY1000 support dropped (unmaintained since long)
+ * oocd_trace support dropped
+
+Boundary Scan:
+
+Target Layer:
+ * ARMv7-A, Cortex-M, Cortex-A/R important fixes and
+ improvements (allowing e.g. simultaneous debugging of A8 and
+ M3 cores, JTAG WAIT support etc.)
+ * ARM Cortex-A,R allow interrupt disable during single-step
+ (maskisr command)
+ * Semihosting support for ARMv7-A
+ * ARM Cortex-M7 support
+ * Intel Quark mcu D2000 support
+ * Freescale LS102x SAP support
+ * ThreadX RTOS support on ARM926E-JS
+ * Cortex-M RTOS stack alignment fixes
+ * FreeRTOS FPU support
+ * uC/OS-III RTOS support
+ * bridging semihosting to GDB's File-I/O support
+ * -defer-examine option added to target create command
+ * verify_image_checksum command added
+
+Flash Layer:
+ * Atmel SAM4S, SAM4N, SAM4C support
+ * Atmel SAMV, SAMS, SAME (Cortex-M7) support
+ * Atmel AT91SAMD handle reset run/halt in DSU, other fixes
+ * Atmel AT91SAML21, SAML22, SAMC20/SAMC21, SAMD09 support
+ * ST STM32F4x support
+ * ST STM32F74x/76x/77x, STM32L4 support
+ * ST STM32L0 categories 1, 2 and 5 support
+ * Kinetis K02, K21, K22, K24, K26, K63, K64, K66 support
+ * Kinetis KE, KVx, K8x families support
+ * Kinetis FlexNVM handling
+ * Kinetis flash protection, security, mass_erase improvements
+ * Infineon XMC4xxx family support
+ * Infineon XMC1000 flash driver
+ * Energy Micro EFM32 Happy Gecko support
+ * Energy Micro EFM32 debug interface lock support
+ * Analog Devices ADuCM360 support
+ * Unified Nuvoton NuMicro flash driver
+ * NIIET K1921VK01T (Cortex-M4) support
+ * Nordic Semiconductor nRF51 improvements
+ * Spansion FM4 flash (including MB9BFx64/x65, S6E2DH) driver
+ * Ambiq Micro Apollo flash driver
+ * PIC32MX new device IDs, 17x/27x flash support
+ * read_bank() and verify_bank() NOR flash internal API to
+ allow reading (and verifying) non-memory-mapped devices
+ * JTAGSPI driver to access SPI NOR flashes via a trivial
+ FPGA proxy
+ * Milandr read/verify for Info memory support
+ * Various discrete SPI NOR flashes support
+ * CFI 16-bit flash reversed endianness support
+
+Board, Target, and Interface Configuration Scripts:
+ * Digilent JTAG-HS2, JTAG-HS3 interfaces configs
+ * FTDI UM232H module as JTAG interface config
+ * 100ask's OpenJTAG interface config
+ * MBFTDI interface config
+ * XDS100v3 interface config
+ * Freescale Vybrid VF6xx target config
+ * EmCraft VF6 SOM and baseboard configs
+ * Freescale SabreSD board config
+ * Freescale VF65GS10 tower board config
+ * Pipistrello Xilinx Spartan6 LX45 FPGA board config
+ * miniSpartan6+ board config
+ * Xilinx Kintex7 Development board config
+ * Parallella-I board config
+ * Digilent Atlys and Analog Discovery board configs
+ * Numato Opsis board config
+ * Xilinx Spartan 6 FPGA "Device DNA" reading support
+ * Altera 10M50 FPGA (MAX10 family) target config
+ * Altera EPM240 CPLD (MAXII family) target config
+ * Marsohod2, Marsohod3 FPGA, Marsohod CPLD boards configs
+ * Novena's integrated FPGA board config
+ * XMOS XS1-XAU8A-10's ARM core config
+ * XMOS xCORE-XA Core Module board config
+ * Exynos5250 target config
+ * Arndale board config
+ * FM4 MB9BFxxx family configs
+ * Spansion SK-FM4-U120-9B560 board config
+ * Diolan LPC4357-DB1 board config
+ * ST STM32F469 discovery board config
+ * ST STM32F7-DISCO, STM327[4|5]6G-EVAL boards configs
+ * ST STM32L4 discovery, NUCLEO L476RG, STM32F429I-DISC1 boards
+ configs
+ * Atheros AR2313, AR2315 targets config
+ * Netgear WP102 board config
+ * La Fonera FON2200 board config
+ * Linksys WAG200G board config
+ * LPC-Link2 board config
+ * NXP LPC4370 target config
+ * Atmel SAMV, SAMS, SAME target configs
+ * Atmel SAM E70 Xplained, SAM V71 Xplained Ultra boards
+ configs
+ * Nordic nRF52 target config
+ * Nordic nRF51-DK, nRF52-DK boards configs
+ * Infineon XMC4700 Relax Kit, XMC4800 Relax EtherCAT Kit,
+ XMC4300 Relax EtherCAT Kit boards configs
+ * Renesas S7G2 target config
+ * Renesas DK-S7G2 board config
+ * Altera EP3C10 FPGA (Cyclone III family) target config
+ * TI MSP432P4xx target config
+ * Cypress PSoC 5LP target config
+ * Analog Devices ADSP-SC58x target config (Cortex-A5 core only)
+
+Server Layer:
+ * tcl_trace command for async target trace output via Tcl RPC
+
+Documentation:
+
+Build and Release:
+ * Various fixes thanks to http://coccinellery.org/
+ * libftdi is now autodetected with pkgconfig
+ * Releases should now support reproducible builds
+ * Conversion to non-recursive make, requires automake >= 1.14
+ * Udev rules modified to add uaccess tag and moved to
+ 60-openocd.rules
+ * Support searching for scripts relative to the openocd binary
+ for all major architectures
+
+
+This release also contains a number of other important functional and
+cosmetic bugfixes. For more details about what has changed since the
+last release, see the git repository history:
+
+http://sourceforge.net/p/openocd/code/ci/v0.10.0/log/?path=
+
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.11.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.11.0
new file mode 100644
index 0000000..4542aa2
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.11.0
@@ -0,0 +1,238 @@
+This file includes highlights of the changes made in the OpenOCD
+source archive release.
+
+JTAG Layer:
+ * add debug level 4 for verbose I/O debug
+ * bitbang, add read buffer to improve performance
+ * Cadence SystemVerilog Direct Programming Interface (DPI) adapter driver
+ * CMSIS-DAP v2 (USB bulk based) adapter driver
+ * Cypress KitProg adapter driver
+ * FTDI FT232R sync bitbang adapter driver
+ * Linux GPIOD bitbang adapter driver through libgpiod
+ * Mellanox rshim USB or PCIe adapter driver
+ * Nuvoton Nu-Link and Nu-Link2 adapter drivers
+ * NXP IMX GPIO mmap based adapter driver
+ * ST-Link consolidate all versions in single config
+ * ST-Link read properly old USB serial numbers
+ * STLink/V3 support (for ST devices only !)
+ * STM8 SWIM transport
+ * TI XDS110 adapter driver
+ * Xilinx XVC/PCIe adapter driver
+
+Boundary Scan:
+
+Target Layer:
+ * 64 bit address support
+ * ARCv2 target support
+ * ARM Cortex-A hypervisor mode support
+ * ARM Cortex-M fast PC sampling support for profiling
+ * ARM generic CTI support
+ * ARM generic mem-ap target support
+ * ARMv7-A MMU tools
+ * ARMv7m traces add TCP stream server
+ * ARMv8 AARCH64 target support and semihosting support
+ * ARMv8 AARCH64 disassembler support through capstone library
+ * ARMv8-M target support
+ * EnSilica eSi-RISC target support, including instruction tracing
+ eSi-Trace support
+ * MIPS64 target support
+ * Motorola SREC S6 record image file support
+ * RISC-V target support
+ * SEGGER Real Time Transfer (RTT) initial support (for single target,
+ Cortex-M only)
+ * ST STM8 target support
+ * Various MIPS32 target improvements
+
+Flash Layer:
+ * Atheros (ath79) SPI interface support
+ * Atmel atmega128rfa1 support
+ * Atmel SAM D21, D51, DA1, E51, E53, E54, G55, R30 support
+ * Atmel SAMC2?N* support
+ * Cypress PSoC5LP, PSoC6 support
+ * EnSilica eSi-RISC support
+ * Foshan Synwit Tech SWM050 support
+ * Maxim Integrated MAX32XXX support
+ * Nordic Semiconductor nRF51822, nRF52810, nRF52832 support
+ * NXP Kinetis K27, K28, KE1x, KEAx, KL28, KL8x, KV5x, KWx support
+ * Renesas RPC HF support
+ * SH QSPI support
+ * SiFive Freedom E support
+ * Silicon Labs EFR-family, EZR32HG support
+ * ST BlueNRG support
+ * ST STM32 QUAD/OCTO-SPI interface support for Flash, FRAM and EEPROM
+ * ST STM32F72x, STM32F4x3, STM32H7xx support
+ * ST STM32G0xx, STM32G4xx, STM32L4x, STM32WB, STM32WL support
+ * ST STM32L5x support (non secure mode)
+ * TI CC13xx, CC26xx, CC32xx support
+ * TI MSP432 support
+ * Winner Micro w600 support
+ * Xilinx XCF platform support
+ * Various discrete SPI NOR flashes support
+
+Board, Target, and Interface Configuration Scripts:
+ * 8devices LIMA board config
+ * Achilles Instant-Development Kit Arria 10 board config
+ * Amazon Kindle 2 and DX board config
+ * Analog Devices ADSP-SC58x, ADSP-SC584-EZBRD board config
+ * Andes Technology ADP-XC7KFF676 board config
+ * Andes Technology Corvette-F1 board config
+ * ARM Musca A board config
+ * Arty Spartan 7 FPGA board config
+ * Atmel SAMD10 Xplained mini board config
+ * Atmel SAMD11 Xplained Pro board config
+ * Atmel SAM G55 Xplained Pro board config
+ * AVNET UltraZED EG StarterKit board config
+ * Blue Pill STM32F103C8 board config
+ * DP Busblaster v4.1a board config
+ * DPTechnics DPT-Board-v1 board config
+ * Emcraft imx8 SOM BSB board config
+ * Globalscale ESPRESSObin board config
+ * Kasli board config
+ * Kintex Ultrascale XCKU040 board config
+ * Knovative KC-100 board config
+ * LeMaker HiKey board config
+ * Microchip (Atmel) SAME54 Xplained Pro board config
+ * Microchip (Atmel) SAML11 Xplained Pro board config
+ * Nordic module NRF52 board config
+ * Numato Lab Mimas A7 board config
+ * NXP Freedom FRDM-LS1012A board config
+ * NXP IMX7SABRE board config
+ * NXP IMX8MP-EVK board config
+ * NXP MC-IMX8M-EVK board config
+ * QuickLogic QuickFeather board config
+ * Renesas R-Car E2, H2, M2 board config
+ * Renesas R-Car Salvator-X(S) board config
+ * Renesas RZ/A1H GR-Peach board config
+ * Rigado BMD-300 board config
+ * Sayma AMC board config
+ * Sifive e31arty, e51arty, hifive1 board config
+ * ST B-L475E-IOT01A board config
+ * ST BlueNRG idb007v1, idb008v1, idb011v1 board config
+ * ST STM32F412g discovery board config
+ * ST STM32F413h discovery board config
+ * ST STM32F469i discovery board config
+ * ST STM32F7 Nucleo board config
+ * ST STM32F723e discovery board config
+ * ST STM32F746g discovery board config
+ * ST STM32F769i discovery board config
+ * ST STM32H735g discovery board config
+ * ST STM32H743zi Nucleo board config
+ * ST STM32H745i discovery board config
+ * ST STM32H747i discovery board config
+ * ST STM32H750b discovery board config
+ * ST STM32H7b3i discovery board config
+ * ST STM32H7x_dual_qspi board config
+ * ST STM32H7x3i Eval boards config
+ * ST STM32L073 Nucleo board config
+ * ST STM32L476g discovery board config
+ * ST STM32L496g discovery board config
+ * ST STM32L4p5g discovery board config
+ * ST STM32L4r9i discovery board config
+ * ST STM32L5 Nucleo board config
+ * ST STM32MP15x DK2 board config
+ * ST STM32WB Nucleo board config
+ * ST STM8L152R8 Nucleo board config
+ * Synopsys DesignWare ARC EM board config
+ * Synopsys DesignWare ARC HSDK board config
+ * TI BeagleBone family boards config
+ * TI CC13xx, CC26xx, CC32xx LaunchPad board config
+ * TI MSP432 LaunchPad board config
+ * Tocoding Poplar board config
+ * TP-Link WDR4300 board config
+ * Allwinner V3s target config
+ * Andes Technology NDS V5 target config
+ * Atmel atmega128rfa1 target config
+ * ARM corelink SSE-200 target config
+ * Atheros_ar9344 target config
+ * Cypress PSoC5LP, PSoC6 target config
+ * EnSilica eSi-RISC target config
+ * Foshan Synwit Tech SWM050 target config
+ * GigaDevice GD32VF103 target config
+ * Hisilicon Hi3798 target config
+ * Hisilicon Hi6220 target config
+ * Infineon TLE987x target config
+ * Marvell Armada 3700 target config
+ * Maxim Integrated MAX32XXX target config
+ * Mellanox BlueField target config
+ * Microchip (Atmel) SAME5x, SAML1x target config
+ * NXP IMX6SX, IMX6UL, IMX7, IMX7ULP, IMX8 target config
+ * NXP Kinetis KE1xZ, KE1xF target config
+ * NXP LPC84x, LPC8Nxx, LS1012A, NHS31xx target config
+ * Qualcomm QCA4531 target config
+ * QuickLogic EOS S3 target config
+ * Renesas R-Car E2, H2, M2 target config
+ * Renesas R-Car Gen3 target config
+ * Renesas RZ/A1H target config
+ * Rockchip RK3308 target config
+ * ST BlueNRG target config
+ * ST STM32G0, STM32G4, STM32H7, STM32L0, STM32L5 target config
+ * ST STM32MP15x target config
+ * ST STM32WBx, STM32WLEx target config
+ * ST STM8L152, S003, S103, S105 target config
+ * Synopsys DesignWare ARC EM target config
+ * Synopsys DesignWare ARC HS Development Kit SoC target config
+ * TI CC13xx, CC26xx, CC32xx target config
+ * TI TNETC4401 target config
+ * Xilinx UltraScale+ target config
+ * Altera 5M570Z (MAXV family) CPLD config
+ * Xilinx Ultrascale, XCF CPLD config
+ * Intel (Altera) Arria10 FPGA config
+ * Cadence SystemVerilog Direct Programming Interface (DPI) interface config
+ * Cypress KitProg interface config
+ * Digilent SMT2 NC interface config
+ * DLN-2 example of Linux GPIOD interface config
+ * FTDI C232HM interface config
+ * HIE JTAG Debugger interface config
+ * In-Circuit's ICprog interface config
+ * isodebug isolated JTAG/SWD+UART interface config
+ * Mellanox rshim USB or PCIe interface config
+ * Nuvoton Nu-Link interface config
+ * NXP IMX GPIO mmap based interface config
+ * Steppenprobe open hardware interface config
+ * TI XDS110 interface config
+
+Server Layer:
+ * 64 bit address support
+ * default bind to IPv4 localhost
+ * gdb: allow multiple connections
+ * gdb: architecture element support
+ * gdb: vCont, vRun support
+ * telnet: handle Ctrl+A, Ctrl+E and Ctrl+K
+
+RTOS:
+ * Chromium-EC rtos support
+ * hwthread pseudo rtos support
+ * NuttX rtos support
+ * RIOT rtos support
+
+Documentation:
+ * Improve STM32 flash driver
+ * Various typo fix and improvements
+
+Build and Release:
+ * Add libutil to support jimtcl version 0.80
+ * Clang warning fixes
+ * GitHub workflow for Win32 snapshot binaries
+ * Handle Tcl return values consistently
+ * Mitigation for CVE-2018-5704: Prevent some forms of Cross
+ Protocol Scripting attacks
+ * Support for libftdi 1.5
+ * Travis-CI basic support
+ * Update libjaylink to version 0.2.0
+ * Update jimtcl to version 0.79
+ * Use external (optional) library capstone for ARM and AARCH64 disassembly
+
+
+This release also contains a number of other important functional and
+cosmetic bugfixes. For more details about what has changed since the
+last release, see the git repository history:
+
+http://sourceforge.net/p/openocd/code/ci/v0.11.0/log/?path=
+
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.12.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.12.0
new file mode 100644
index 0000000..208146a
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.12.0
@@ -0,0 +1,132 @@
+This file includes highlights of the changes made in the OpenOCD
+source archive release.
+
+JTAG Layer:
+ * add default to adapter speed when unspecified (100 kHz)
+ * AM335X gpio (BeagleBones) adapter driver
+ * BCM2835 support for SWD
+ * Cadence Virtual Debug (vdebug) adapter driver
+ * CMSIS-DAP support for SWO and SWD multidrop
+ * Espressif USB JTAG Programmer adapter driver
+ * Remote bitbang support for Windows host
+ * ST-LINK add TCP server support to adapter driver
+ * SWD multidrop support
+
+Boundary Scan:
+
+Target Layer:
+ * aarch64: support watchpoints
+ * arm: support independent TPIU and SWO for trace
+ * arm adi v5: support Large Physical Address Extension
+ * arm adi v6: support added, for jtag and swd transport
+ * cortex_a: support watchpoints
+ * elf 64bit load support
+ * Espressif: support ESP32, ESP32-S2 and ESP32-S3 cores
+ * semihosting: support user defined operations
+ * Xtensa: support Xtensa LX architecture via JTAG and ADIv5 DAP
+
+Flash Layer:
+ * Atmel/Microchip SAM E51G18A, E51G19A, R35J18B, LAN9255 support
+ * GigaDevice GD32E23x, GD32F1x0/3x0, GD32VF103 support
+ * Nuvoton NPCX series support
+ * onsemi RSL10 support
+ * Raspberry Pi Pico RP2040 support
+ * ST BlueNRG-LPS support
+ * ST STM32 G05x, G06x, G0Bx, G0Cx, U57x, U58x, WB1x, WL5x support
+ * ST STM32 G0, G4, L4, L4+, L5, WB, WL OTP support
+
+Board, Target, and Interface Configuration Scripts:
+ * Ampere Computing eMAG8180, Altra ("Quicksilver") and Altra Max ("Mystique") board config
+ * Cadence KC705 FPGA (Xtensa Development Platform) via JTAG and ADIv5 DAP board config
+ * Digilent Nexys Video board config
+ * Espressif ESP32 ETHERNET-KIT and WROVER-KIT board config
+ * Espressif ESP32 via ESP USB Bridge generic board config
+ * Espressif ESP32-S2 Kaluga 1 board config
+ * Espressif ESP32-S2 with ESP USB Bridge board config
+ * Espressif ESP32-S3 example board config
+ * Kontron SMARC-sAL28 board config
+ * LambdaConcept ECPIX-5 board config
+ * Microchip ATSAMA5D27-SOM1-EK1 board config
+ * Microchip EVB-LAN9255 board config
+ * Microchip SAME51 Curiosity Nano board config
+ * NXP FRDM-K64F, LS1046ARDB and LS1088ARDB board config
+ * NXP RT6XX board config
+ * Olimex H405 board config
+ * Radiona ULX3S board config
+ * Raspberry Pi 3 and Raspberry Pi 4 model B board config
+ * Raspberry Pi Pico-Debug board config
+ * Renesas R-Car V3U Falcon board config
+ * ST BlueNRG-LPS steval-idb012v1 board config
+ * ST NUCLEO-8S208RB board config
+ * ST NUCLEO-G031K8, NUCLEO-G070RB, NUCLEO-G071RB board config
+ * ST NUCLEO-G431KB, NUCLEO-G431RB, NUCLEO-G474RE board config
+ * ST STM32MP13x-DK board config
+ * TI AM625 EVM, AM642 EVM and AM654 EVM board config
+ * TI J721E EVM, J721S2 EVM and J7200 EVM board config
+ * Ampere Computing eMAG, Altra ("Quicksilver") and Altra Max ("Mystique") target config
+ * Cadence Xtensa generic and Xtensa VDebug target config
+ * Broadcom BCM2711, BCM2835, BCM2836 and BCM2837 target config
+ * Espressif ESP32, ESP32-S2 and ESP32-S3 target config
+ * Microchip ATSAMA5D2 series target config
+ * NanoXplore NG-Ultra SoC target config
+ * NXP IMX8QM target config
+ * NXP LS1028A, LS1046A and LS1088A target config
+ * NXP RT600 (Xtensa HiFi DSP) target config
+ * onsemi RSL10 target config
+ * Raspberry Pi Pico RP2040 target config
+ * Renesas R8A779A0 V3U target config
+ * Renesas RZ/Five target config
+ * Renesas RZ/G2 MPU family target config
+ * Rockchip RK3399 target config
+ * ST BlueNRG-LPS target config
+ * ST STM32MP13x target config
+ * TI AM625, AM654, J721E and J721S2 target config
+ * Ashling Opella-LD interface config
+ * Aspeed AST2600 linuxgpiod based interface config
+ * Blinkinlabs JTAG_Hat interface config
+ * Cadence Virtual Debug (vdebug) interface config
+ * Espressif ESP32-S2 Kaluga 1 board's interface config
+ * Espressif USB Bridge jtag interface config
+ * Infineon DAP miniWiggler V3 interface config
+ * PLS SPC5 interface config
+ * Tigard interface config
+ * Lattice MachXO3 family FPGA config
+
+Server Layer:
+ * GDB: add per-target remote protocol extensions
+ * GDB: more 'Z' packets support
+ * IPDBG JtagHost server functionality
+ * semihosting: I/O redirection to TCP server
+ * telnet: support for command's autocomplete
+
+RTOS:
+ * 'none' rtos support
+ * Zephyr rtos support
+
+Documentation:
+
+Build and Release:
+ * Add json extension to jimtcl build
+ * Drop dependency from libusb0
+ * Drop repository repo.or.cz for submodules
+ * Move gerrit to https://review.openocd.org/
+ * Require autoconf 2.69 or newer
+ * Update jep106 to revision JEP106BF.01
+ * Update jimtcl to version 0.81
+ * Update libjaylink to version 0.3.1
+ * New configure flag '--enable-jimtcl-maintainer' for jimtcl build
+
+
+This release also contains a number of other important functional and
+cosmetic bugfixes. For more details about what has changed since the
+last release, see the git repository history:
+
+http://sourceforge.net/p/openocd/code/ci/v0.12.0/log/?path=
+
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.2.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.2.0
new file mode 100644
index 0000000..7426926
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.2.0
@@ -0,0 +1,80 @@
+The OpenOCD 0.2.0 source archive release includes numerous improvements
+that were made since the initial 0.1.0 source archive release. Many
+contributors helped make this release a great success, and the community
+of developers and maintainers look forward to any response.
+
+In addition to the list of changes below, countless bug fixing and
+cleaning was performed across the tree. Various TCL command parameters
+must past stricter value checks, and many more error conditions have
+been handled correctly. These efforts helped to make the 0.2.0 release
+more stable and robust, though some changes may expose latent bugs in
+your existing configuration scripts.
+
+This release does not maintain backward compatibility in all respects,
+so some target or configuration scripts may need to be updated. In some
+cases, you may also see warnings; resolve those, because they indicate
+commands that will be removed in the future.
+
+The following areas of OpenOCD functionality changed in this release:
+
+JTAG Layer:
+- Improves modularity: core, TCL, driver commands, and interface have
+ been separated, encapsulated, and documented for developers. Mostly.
+- Improves JTAG TAP transition tables:
+ * Makes TAP paths variable length, rather than being fixed at 7 steps.
+ * Fixes problems with some targets that did not like longer paths.
+- Improves JTAG driver/minidriver modularity and encapsulation.
+- New drivers:
+ * Adds stub minidriver for developing new embedded JTAG interfaces.
+- Improves drivers:
+ * ft2232+ftd2xx:
+ + Adds initial high-speed device support: --enable-ftd2xx-highspeed
+ + Supports more types of FTDI-based devices.
+ * jlink:
+ + Works with more versions of the firmware (v3 and newer)
+ + Supports dynamically detects device capabilities and limits
+ * vsllink:
+ + Supports very long scan chains
+ * amtjtagaccel:
+ + Fixes broken ID code detection problems.
+
+Target Layer:
+- New devices: AVR, FA526
+- Improved support: ARM ADI, ARM11, MIPS
+- Numerous other bug fixes and improvements
+
+Flash Layer:
+- Improved drivers: mflash
+- New drivers: AT91SAM3, AVR, Davinci NAND
+
+Board, Interface, and Target Configuration Scripts:
+- Many new and improved targets and boards are now available.
+- Better separation of "board" and "target" configuration
+- Moved all TCL files to top-level "tcl" directory in the source tree
+- Installation moved from '$pkglibdir/' to '$pkgdatadir/scripts/'.
+- Site-specific files should be installed under '$pkgdatadir/site/';
+ files that exist this tree will be used in preference to default
+ distribution configurations in '$pkgdatadir/scripts/'.
+
+Documentation:
+- Updated User Guide: http://openocd.berlios.de/doc/html/index.html
+ * Partially re-written and re-organized.
+ * Standardized presentation for all commands.
+ * Covers many drivers and commands that were previously omitted.
+ * New index for commands and drivers.
+- Added Developer Manual: http://openocd.berlios.de/doc/doxygen/index.html
+ * Now includes architecture, technical primers, style guides, and more.
+ * Available in-tree and on-line.
+
+Build and Release:
+- Increased configuration and compilation warning coverage.
+ * Use --disable-werror to work around build errors caused by warnings.
+- Use libtool to produce helper libraries as a step toward "libopenocd".
+- New processes and scripting to facilitate future source releases.
+
+For more details about what has changed since 0.1.0, see the ChangeLog
+associated with this release.
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.3.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.3.0
new file mode 100644
index 0000000..80e8823
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.3.0
@@ -0,0 +1,82 @@
+This file should include highlights of the changes made in the
+OpenOCD openocd-0.3.0 source archive release. See the repository
+history for details about what changed, including bugfixes and
+other issues not mentioned here.
+
+JTAG Layer:
+ FT2232H (high speed USB) support doesn't need separate configuration
+ New FT2232H JTAG adapters: Amontec, Olimex, Signalyzer
+ New reset_config options for SRST gating the JTAG clock (or not)
+ TAP declaration no longer requires ircapture and mask attributes
+ Scan chain setup should be more robust, with better diagnostics
+ New TAP events:
+ "post-reset" for TAP-invariant setup code (TAPs not usable yet)
+ "setup" for use once TAPs are addressable (e.g. with ICEpick)
+ Overridable Tcl "init_reset" and "jtag_init" procedures
+ Simple "autoprobe" mechanism to help simplify server setup
+
+Boundary Scan:
+ SVF bugfixes ... parsing fixes, better STATE switch conformance
+ XSVF bugfixes ... be more correct, handle Xilinx tool output
+
+Target Layer:
+ Warn on use of obsolete numeric target IDs
+ New commands for use with Cortex-M3 processors:
+ "cortex_m3 disassemble" ... Thumb2 disassembly (UAL format)
+ "cortex_m3 vector_catch" ... traps certain hardware faults
+ without tying up breakpoint resources
+ If you're willing to help debug it
+ VERY EARLY Cortex-A8 and ARMv7A support
+ Updated BeagleBoard.org hardware support
+ you may need to explicitly "reset" after connect-to-Beagle
+ New commands for use with XScale processors: "xscale vector_table"
+ ARM
+ bugfixes to single-stepping Thumb code
+ ETM: unavailable registers are not listed
+ ETB, ETM: report actual hardware status
+ ARM9
+ name change: "arm9 vector_catch" not "arm9tdmi vector_catch"
+ ARM11
+ single stepping support for i.MX31
+ bugfix for missing "arm11" prefix on "arm11 memwrite ..."
+ GDB support
+ gdb_attach command is gone
+
+Flash Layer:
+ The lpc2000 driver handles the new NXP LPC1700 (Cortex-M3) chips
+ New drivers:
+ lpc2900, for NXP LPC2900 chips (ARM968 based)
+ mx3_nand, for imx31
+ New "last" flag for NOR "flash erase_sector" and "flash protect"
+ The "nand erase N" command now erases all of bank N
+ Speed up davinci_nand by about 3x
+
+Board, Target, and Interface Configuration Scripts:
+ Amontec JTAGkey2 support
+ Cleanup and additions for the TI/Luminary Stellaris scripts
+ LPC1768 target (and flash) support
+ Keil MCB1700 eval board
+ Samsung s3c2450
+ Mini2440 board
+ Numeric TAP and Target identifiers now trigger warnings
+ PXA255 partially enumerates
+
+Documentation:
+ Capture more debugging and setup advice
+ Notes on target source code changes that may help debugging
+
+Build and Release:
+ Repository moved from SVN at Berlios to GIT at SourceForge
+ Clean builds on (32-bit) Cygwin
+ Clean builds on 64-bit MinGW
+
+For more details about what has changed since the last release,
+see the git repository history. With gitweb, you can browse that
+in various levels of detail.
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.4.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.4.0
new file mode 100644
index 0000000..cbd5526
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.4.0
@@ -0,0 +1,98 @@
+This file includes highlights of the changes made in the
+OpenOCD 0.4.0 source archive release. See the repository
+history for details about what changed, including bugfixes
+and other issues not mentioned here.
+
+JTAG Layer:
+ Support KT-Link JTAG adapter.
+ Support USB-JTAG, Altera USB-Blaster and compatibles.
+
+Boundary Scan:
+
+Target Layer:
+ General
+ - Removed commands which have been obsolete for at least
+ a year (from both documentation and, sometimes, code).
+ - new "reset-assert" event, for systems without SRST
+ ARM
+ - supports "reset-assert" event (except on Cortex-M3)
+ - renamed "armv4_5" command prefix as "arm"
+ - recognize TrustZone "Secure Monitor" mode
+ - "arm regs" command output changed
+ - register names use "sp" not "r13"
+ - add top-level "mcr" and "mrc" commands, replacing
+ various core-specific operations
+ - basic semihosting support (ARM7/ARM9 only, for now)
+ ARM11
+ - Should act much more like other ARM cores:
+ * Preliminary ETM and ETB hookup
+ * accelerated "flash erase_check"
+ * accelerated GDB memory checksum
+ * support "arm regs" command
+ * can access all core modes and registers
+ * watchpoint support
+ - Shares some core debug code with Cortex-A8
+ Cortex-A8
+ - Should act much more like other ARM cores:
+ * support "arm regs" command
+ * can access all core modes and registers
+ * watchpoint support
+ - Shares some core debug code with ARM11
+ Cortex-M3
+ - Exposed DWT registers like cycle counter
+ - vector_catch settings not clobbered by resets
+ - no longer interferes with firmware's fault handling
+ ETM, ETB
+ - "trigger_percent" command moved ETM --> ETB
+ - "etm trigger_debug" command added
+ MIPS
+ - use fastdata writes
+ Freescale DSP563xx cores (partial support)
+
+Flash Layer:
+ 'flash bank' and 'nand device' take as first argument.
+ With this, flash/NAND commands allow referencing banks by name:
+ - : reference the bank with its defined name
+ - [.N]: reference the driver's Nth bank
+ New 'nand verify' command to check bank against an image file.
+ The "flash erase_address" command now rejects partial sectors;
+ previously it would silently erase extra data. If you
+ want to erase the rest of the first and/or last sectors
+ instead of failing, you must pass an explicit "pad" flag.
+ New at91sam9 NAND controller driver.
+ New s3c64xx NAND controller driver.
+
+Board, Target, and Interface Configuration Scripts:
+ ARM9
+ - ETM and ETB hookup for iMX2* targets
+ Add $HOME/.openocd to the search path.
+ Handle Rev C of LM3S811 eval boards.
+ - use "luminary-lm3s811.cfg" for older boards
+ - use "luminary.cfg" for RevC and newer
+
+Core Jim/TCL Scripting:
+ New 'usage' command to provide terse command help.
+ Improved command 'help' command output (sorted and indented).
+ Improved command handling:
+ - Most boolean settings now accept any of the following:
+ on/off, enable/disable, true/false, yes/no, 1/0
+ - More error checking and reporting.
+
+Documentation:
+ New built-in command development documentation and primer.
+
+Build and Release:
+ Use --enable-doxygen-pdf to build PDF developer documentation.
+ Consider upgrading to libftdi 0.17 if you use that library; it
+ includes bugfixes which improve FT2232H support.
+
+For more details about what has changed since the last release,
+see the git repository history. With gitweb, you can browse that
+in various levels of detail.
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.5.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.5.0
new file mode 100644
index 0000000..90ea35c
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.5.0
@@ -0,0 +1,73 @@
+This file includes highlights of the changes made in the
+OpenOCD 0.5.0 source archive release. See the repository
+history for details about what changed, including bugfixes
+and other issues not mentioned here.
+
+JTAG Layer:
+ New driver for "Bus Pirate"
+ Rename various commands so they're not JTAG-specific
+ There are migration procedures for most of these, but you should
+ convert your scripts to the new names, since those procedures
+ will not be around forever.
+ jtag jinterface ... is now adapter_name
+ jtag_khz ... is now adapter_khz
+ jtag_nsrst_delay ... is now adapter_nsrst_delay
+ jtag_nsrst_assert_width ... is now adapter_nsrst_assert_width
+ Support Voipac VPACLink JTAG Adapter.
+
+Boundary Scan:
+
+Transport framework core ... supporting future work for SWD, SPI, and other
+non-JTAG ways to debug targets or program flash.
+
+Target Layer:
+ ARM:
+ - basic semihosting support for ARMv7M.
+ - renamed "armv7m" command prefix as "arm"
+ MIPS:
+ - "ejtag_srst" variant removed. The same functionality is
+ obtained by using "reset_config none".
+ - added PIC32MX software reset support, this means srst is not
+ required to be connected anymore.
+ OTHER:
+ - preliminary AVR32 AP7000 support.
+
+Flash Layer:
+ New "stellaris recover" command, implements the procedure
+ to recover locked devices (restoring non-volatile
+ state to the factory defaults, including erasing
+ the flash and its protection bits, and possibly
+ re-enabling hardware debugging).
+ PIC32MX now uses algorithm for flash programming, this
+ has increased the performance by approx 96%.
+ New 'pic32mx unlock' cmd to remove readout protection.
+ New STM32 Value Line Support.
+ New 'virtual' flash driver, used to associate other addresses
+ with a flash bank. See pic32mx.cfg for usage.
+ New iMX27 NAND flash controller driver.
+
+Board, Target, and Interface Configuration Scripts:
+ Support IAR LPC1768 kickstart board (by Olimex)
+ Support Voipac PXA270/PXA270M module.
+ New $PARPORTADDR tcl variable used to change default
+ parallel port address used.
+ Remove lm3s811.cfg; use "stellaris.cfg" instead
+
+Core Jim/TCL Scripting:
+ New "add_script_search_dir" command, behaviour is the same
+ as the "-s" cmd line option.
+
+Documentation:
+
+Build and Release:
+
+For more details about what has changed since the last release,
+see the git repository history. With gitweb, you can browse that
+in various levels of detail.
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.6.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.6.0
new file mode 100644
index 0000000..0acd242
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.6.0
@@ -0,0 +1,54 @@
+This file includes highlights of the changes made in the
+OpenOCD source archive release. See the
+repository history for details about what changed, including
+bugfixes and other issues not mentioned here.
+
+JTAG Layer:
+ New STLINK V1/V2 JTAG/SWD adapter support.
+ New OSJTAG adapter support.
+ New Tincantools Flyswatter2 support.
+ Improved ULINK driver.
+ Improved RLINK driver.
+ Support for adapters based on FT232H chips.
+ New experimental driver for FTDI based adapters, using libusb-1.0 in asynchronous mode.
+
+Boundary Scan:
+
+Target Layer:
+ New Cortex-M0 support.
+ New Cortex-M4 support.
+ Improved Working area algorithm.
+ New RTOS support. Currently linux, FreeRTOS, ThreadX and eCos.
+ Connecting under reset to Cortex-Mx and MIPS chips.
+
+Flash Layer:
+ New SST39WF1601 support.
+ New EN29LV800BB support.
+ New async algorithm support for selected targets, stm32, stellaris and pic32.
+ New Atmel SAM3S, SAM3N support.
+ New ST STM32L support.
+ New Microchip PIC32MX1xx/2xx support.
+ New Freescale Kinetis K40 support.
+
+Board, Target, and Interface Configuration Scripts:
+ Support Dangerous Prototypes Bus Blaster.
+ Support ST SPEAr Family.
+ Support Gumstix Verdex boards.
+ Support TI Beaglebone.
+
+Documentation:
+ Improved HACKING info for submitting patches.
+ Fixed numerous broken links.
+
+Build and Release:
+
+For more details about what has changed since the last release,
+see the git repository history. With gitweb, you can browse that
+in various levels of detail.
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.7.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.7.0
new file mode 100644
index 0000000..47a8fa6
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.7.0
@@ -0,0 +1,43 @@
+This file includes highlights of the changes made in the
+OpenOCD source archive release. See the
+repository history for details about what changed, including
+bugfixes and other issues not mentioned here.
+
+JTAG Layer:
+ New TI ICDI adapter support.
+ Support Latest OSBDM firmware.
+ Improved MIPS EJTAG Support.
+
+Boundary Scan:
+
+Target Layer:
+ New ARMv7R and Cortex-R4 support.
+ Added ChibiOS/RT support.
+
+Flash Layer:
+ New NXP LPC1850 support.
+ New NXP LPC4300 support.
+ New NXP SPIFI support.
+ New Energy Micro EFM32 support.
+ New ST STM32W support.
+ New ST STM32f2 write protection and lock/unlock support.
+ Ability to override STM32 flash bank size.
+
+Board, Target, and Interface Configuration Scripts:
+ Support Freescale i.MX6 series targets.
+
+Documentation:
+ New MIPS debugging info.
+
+Build and Release:
+
+For more details about what has changed since the last release,
+see the git repository history. With gitweb, you can browse that
+in various levels of detail.
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.8.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.8.0
new file mode 100644
index 0000000..33b3af4
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.8.0
@@ -0,0 +1,111 @@
+This file includes highlights of the changes made in the OpenOCD
+source archive release.
+
+JTAG Layer:
+ * New CMSIS-DAP driver
+ * Andes AICE debug adapter support
+ * New OpenJTAG driver
+ * New BCM2835 (RaspberryPi) driver
+ * JTAG VPI client driver (for OpenRISC Reference Platform SoC)
+ * Xilinx BSCAN_* for OpenRISC support
+ * ST-LINKv2-1 support
+ * ST-LINKv2 SWO tracing support (UART emulation)
+ * JLink-OB (onboard) support
+ * Altera USB Blaster driver rewrite, initial Blaster II
+ support
+ * ULINK driver ported to libusb-1.0, OpenULINK build fixes
+ * Support up to 64 bit IR lengths
+ * SVF playback (FPGA programming) fixes
+ * "ftdi" interface driver got extensive testing and is now
+ recommended over the old ft2232 implementation
+
+Boundary Scan:
+
+Target Layer:
+ * New target: Andes nds32
+ * New target: OpenRISC OR1K
+ * New target: Intel Quark X10xx
+ * MIPS EJTAG 1.5/2.0 support
+ * MIPS speed improvements
+ * Cortex-M, Cortex-A (MEM-AP, APB-AP) targets working with BE
+ hosts now
+ * XScale vector_catch support, reset fixes
+ * dsp563xx ad-hoc breakpoint/watchpoint support
+ * RTOS support for embKernel
+ * Target profiling improvements
+ * Memory access functions testbench
+
+Flash Layer:
+ * STM32 family sync with reference manuals, other bugfixes
+ * STM32F401, STM32F07x support
+ * Atmel SAM4L, SAMG5x support
+ * at91sam3sd8{a,b}, at91sam3s8{a,b,c}, at91sam4s,
+ at91sam3n0{a,b,0a,0b} support, bugfixes
+ * Atmel SAMD support
+ * Milandr 1986ВЕ* support
+ * Kinetis KL, K21 support
+ * Nuvoton NuMicro MINI5{1,2,4} support
+ * Nuvoton NUC910 series support
+ * NXP LPC43xx, LPC2000 fixes
+ * NXP LPC800, LPC810 support
+ * More ATmega parts supported
+ * Fujitsu MB9Ax family support
+ * EFM32 Wonder Gecko family support
+ * Nordic nRF51 support
+
+Board, Target, and Interface Configuration Scripts:
+ * STM32W108xx generic target config
+ * STM32F429 discovery board config
+ * STM32 Nucleo boards configs
+ * DENX M53EVK board config
+ * Altera Cyclone V SoC, SoCkit config
+ * New TI Launchpads board configs
+ * TI am43xx devices, AM437x GP EVM, AM438x ePOS EVM board
+ configs
+ * Marvell Armada 370 family initial support
+ * TI TMDX570LS31USB (TMS570, Cortex-R4) support scripts
+ * Freescale FRDM-KL25Z, KL46Z board configs
+ * Digilent Zedboard config
+ * Asus RT-N16, Linksys WRT54GL, BT HomeHub board configs
+ * Atmel Xplained initial support
+ * Broadcom bcm28155_ap board config
+ * TUMPA, TUMPA Lite interface configs
+ * Digilent JTAG-SMT2 interface config
+ * New RAM testing functions
+ * Easy-to-use firmware recovery helpers targetting ordinary
+ users with common equipment
+
+Server Layer:
+ * Auto-generation of GDB target description for ARMv7-M,
+ ARM4, nds32, OR1K, Quark
+ * GDB File-I/O Remote Protocol extension support
+ * Default GDB flashing events handlers to initialise and reset
+ the target automatically when "load" is used
+
+Documentation:
+ * Extensive README* changes
+ * The official User's Guide was proofread
+ * Example cross-build script
+ * RTOS documentation improvements
+ * Tcl RPC documentation and examples added
+
+Build and Release:
+ * *BSD, OS X, clang, ARM, windows build fixes
+ * New pkg-config support changes the way libusb (and other
+ dependencies) are handled. Many adapter drivers are now
+ selected automatically during the configure stage.
+
+
+This release also contains a number of other important functional and
+cosmetic bugfixes. For more details about what has changed since the
+last release, see the git repository history:
+
+http://sourceforge.net/p/openocd/code/ci/v0.8.0/log/?path=
+
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.9.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.9.0
new file mode 100644
index 0000000..77ae4b0
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/NEWS-0.9.0
@@ -0,0 +1,110 @@
+This file includes highlights of the changes made in the OpenOCD
+source archive release.
+
+JTAG Layer:
+ * SWD support with FTDI, Versaloon, J-Link, sysfsgpio
+ * CMSIS-DAP massive speed and stability improvements
+ * Versaloon driver ported to libusb-1.0
+ * STLink can reestablish communication with a target that was
+ disconnected or rebooted
+ * STLink FAULT and WAIT SWD handling improved
+ * New hla_serial command to distinguish between several HLA
+ adapters attached to a single machine
+ * Serial number support for CMSIS-DAP and J-Link adapters
+ * Support for more J-Link adapters
+ * TAP autoprobing improvements
+ * Big speedup for SVF playback with USB Blaster
+
+Boundary Scan:
+
+Target Layer:
+ * Stability improvements for targets that get disconnected or
+ rebooted during a debug session
+ * MIPS speed and reliability improvements
+ * MIPS 1.5/2.0 fixes
+ * ARMv7-R improvements
+ * Cortex-A improvements, A7, A15 MPCores support
+ * FPU support for ARMv7-M (Cortex-M4F)
+ * TPIU/ITM support (including SWO/SWV tracing), can be
+ captured with external tools or STLink
+ * JTAG Serial Port (Advanced Debug System softcore) support
+ * Profiling support for OpenRISC
+ * ChibiOS/RT 3.0 support (with and without FPU)
+ * FreeRTOS current versions support
+ * Freescale MQX RTOS support
+ * GDB target description support for MIPS
+ * The last created target is auto-selected as the current
+
+Flash Layer:
+ * nRF51 async loader to improve flashing performance and stability
+ * Cypress PSoC 41xx/42xx and CCG1 families flash driver
+ * Silabs SiM3 family flash driver
+ * Marvell Wireless Microcontroller SPI flash driver
+ * Kinetis mass erase (part unsecuring) implemented
+ * lpcspifi stability fixes
+ * STM32 family sync with reference manuals, L0 support, bugfixes
+ * LPC2000 driver automatically determines part and flash size
+ * NXP LPC11(x)xx, LPC13xx, LPC15xx, LPC8xx, LPC5410x, LPC407x support
+ * Atmel SAMD, SAMR, SAML21 devices support
+ * Atmel SAM4E16 support
+ * ZeroGecko family support
+ * TI Tiva C Blizzard and Snowflake families support
+ * Nuvoton NuMicro M051 support
+ * EZR32 support in EFM32 driver
+
+Board, Target, and Interface Configuration Scripts:
+ * Normal target configs can work with HLA (STLink, ICDI) adapters
+ * STM32 discovery and Nucleo boards configs
+ * Gumstix AeroCore board config
+ * General Plus GP326XXXA target config
+ * Micrel KS869x target config
+ * ASUS RT-N66U board config
+ * Atmel SAM4E-EK board config
+ * Atmel AT91SAM4L proper reset handling implemented
+ * TI OMAP/AM 3505, 3517 target configs
+ * nRF51822-mKIT board config
+ * RC Module К1879ХБ1Я target config
+ * TI TMDX570LS20SUSB board config
+ * TI TMS570 USB Kit board config
+ * TI CC2538, CC26xx target configs
+ * TI AM437x major config improvements, DDR support
+ * TI AM437X IDK board config
+ * TI SimpleLink Wi-Fi CC3200 LaunchPad configs
+ * Silicon Labs EM357, EM358 target configs
+ * Infineon XMC1000, XMC4000 family targets and boards configs
+ * Atheros AR9331 target config
+ * TP-LINK TL-MR3020 board config
+ * Alphascale asm9260t target and eval kit configs
+ * Olimex SAM7-LA2 (AT91SAM7A2) board config
+ * EFM32 Gecko boards configs
+ * Spansion FM4 target and SK-FM4-176L-S6E2CC board configs
+ * LPC1xxx target configs were restructured
+ * IoT-LAB debug adapter config
+ * DP BusBlaster KT-Link compatible config
+
+Server Layer:
+ * Polling period can be configured
+ * "shutdown" command has an immediate effect
+ * The "program" command doesn't lead to a shutdown by
+ default, use optional "exit" parameter for the old behaviour
+ * Proper OS signal handling was implemented
+ * Async target notifications for the Tcl RPC
+
+Documentation:
+
+Build and Release:
+
+
+This release also contains a number of other important functional and
+cosmetic bugfixes. For more details about what has changed since the
+last release, see the git repository history:
+
+http://sourceforge.net/p/openocd/code/ci/v0.9.0/log/?path=
+
+
+For older NEWS, see the NEWS files associated with each release
+(i.e. NEWS-).
+
+For more information about contributing test reports, bug fixes, or new
+features and device support, please read the new Developer Manual (or
+the BUGS and PATCHES.txt files in the source archive).
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README
new file mode 100644
index 0000000..7d3f10d
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README
@@ -0,0 +1,356 @@
+Welcome to OpenOCD!
+===================
+
+OpenOCD provides on-chip programming and debugging support with a
+layered architecture of JTAG interface and TAP support including:
+
+- (X)SVF playback to facilitate automated boundary scan and FPGA/CPLD
+ programming;
+- debug target support (e.g. ARM, MIPS): single-stepping,
+ breakpoints/watchpoints, gprof profiling, etc;
+- flash chip drivers (e.g. CFI, NAND, internal flash);
+- embedded TCL interpreter for easy scripting.
+
+Several network interfaces are available for interacting with OpenOCD:
+telnet, TCL, and GDB. The GDB server enables OpenOCD to function as a
+"remote target" for source-level debugging of embedded systems using
+the GNU GDB program (and the others who talk GDB protocol, e.g. IDA
+Pro).
+
+This README file contains an overview of the following topics:
+
+- quickstart instructions,
+- how to find and build more OpenOCD documentation,
+- list of the supported hardware,
+- the installation and build process,
+- packaging tips.
+
+
+============================
+Quickstart for the impatient
+============================
+
+If you have a popular board then just start OpenOCD with its config,
+e.g.:
+
+ openocd -f board/stm32f4discovery.cfg
+
+If you are connecting a particular adapter with some specific target,
+you need to source both the jtag interface and the target configs,
+e.g.:
+
+ openocd -f interface/ftdi/jtagkey2.cfg -c "transport select jtag" \
+ -f target/ti_calypso.cfg
+
+ openocd -f interface/stlink.cfg -c "transport select hla_swd" \
+ -f target/stm32l0.cfg
+
+After OpenOCD startup, connect GDB with
+
+ (gdb) target extended-remote localhost:3333
+
+
+=====================
+OpenOCD Documentation
+=====================
+
+In addition to the in-tree documentation, the latest manuals may be
+viewed online at the following URLs:
+
+ OpenOCD User's Guide:
+ http://openocd.org/doc/html/index.html
+
+ OpenOCD Developer's Manual:
+ http://openocd.org/doc/doxygen/html/index.html
+
+These reflect the latest development versions, so the following section
+introduces how to build the complete documentation from the package.
+
+For more information, refer to these documents or contact the developers
+by subscribing to the OpenOCD developer mailing list:
+
+ openocd-devel@lists.sourceforge.net
+
+Building the OpenOCD Documentation
+----------------------------------
+
+By default the OpenOCD build process prepares documentation in the
+"Info format" and installs it the standard way, so that "info openocd"
+can access it.
+
+Additionally, the OpenOCD User's Guide can be produced in the
+following different formats:
+
+ # If PDFVIEWER is set, this creates and views the PDF User Guide.
+ make pdf && ${PDFVIEWER} doc/openocd.pdf
+
+ # If HTMLVIEWER is set, this creates and views the HTML User Guide.
+ make html && ${HTMLVIEWER} doc/openocd.html/index.html
+
+The OpenOCD Developer Manual contains information about the internal
+architecture and other details about the code:
+
+ # NB! make sure doxygen is installed, type doxygen --version
+ make doxygen && ${HTMLVIEWER} doxygen/index.html
+
+
+==================
+Supported hardware
+==================
+
+JTAG adapters
+-------------
+
+AM335x, ARM-JTAG-EW, ARM-USB-OCD, ARM-USB-TINY, AT91RM9200, axm0432, BCM2835,
+Bus Blaster, Buspirate, Cadence DPI, Cadence vdebug, Chameleon, CMSIS-DAP,
+Cortino, Cypress KitProg, DENX, Digilent JTAG-SMT2, DLC 5, DLP-USB1232H,
+embedded projects, Espressif USB JTAG Programmer,
+eStick, FlashLINK, FlossJTAG, Flyswatter, Flyswatter2,
+FTDI FT232R, Gateworks, Hoegl, ICDI, ICEBear, J-Link, JTAG VPI, JTAGkey,
+JTAGkey2, JTAG-lock-pick, KT-Link, Linux GPIOD, Lisa/L, LPC1768-Stick,
+Mellanox rshim, MiniModule, NGX, Nuvoton Nu-Link, Nu-Link2, NXHX, NXP IMX GPIO,
+OOCDLink, Opendous, OpenJTAG, Openmoko, OpenRD, OSBDM, Presto, Redbee,
+Remote Bitbang, RLink, SheevaPlug devkit, Stellaris evkits,
+ST-LINK (SWO tracing supported), STM32-PerformanceStick, STR9-comStick,
+sysfsgpio, Tigard, TI XDS110, TUMPA, Turtelizer, ULINK, USB-A9260, USB-Blaster,
+USB-JTAG, USBprog, VPACLink, VSLLink, Wiggler, XDS100v2, Xilinx XVC/PCIe,
+Xverve.
+
+Debug targets
+-------------
+
+ARM: AArch64, ARM11, ARM7, ARM9, Cortex-A/R (v7-A/R), Cortex-M (ARMv{6/7/8}-M),
+FA526, Feroceon/Dragonite, XScale.
+ARCv2, AVR32, DSP563xx, DSP5680xx, EnSilica eSi-RISC, EJTAG (MIPS32, MIPS64),
+ESP32, ESP32-S2, ESP32-S3, Intel Quark, LS102x-SAP, RISC-V, ST STM8,
+Xtensa.
+
+Flash drivers
+-------------
+
+ADUC702x, AT91SAM, AT91SAM9 (NAND), ATH79, ATmega128RFA1, Atmel SAM, AVR, CFI,
+DSP5680xx, EFM32, EM357, eSi-RISC, eSi-TSMC, EZR32HG, FM3, FM4, Freedom E SPI,
+GD32, i.MX31, Kinetis, LPC8xx/LPC1xxx/LPC2xxx/LPC541xx, LPC2900, LPC3180, LPC32xx,
+LPCSPIFI, Marvell QSPI, MAX32, Milandr, MXC, NIIET, nRF51, nRF52 , NuMicro,
+NUC910, Nuvoton NPCX, onsemi RSL10, Orion/Kirkwood, PIC32mx, PSoC4/5LP/6,
+Raspberry RP2040, Renesas RPC HF and SH QSPI,
+S3C24xx, S3C6400, SiM3x, SiFive Freedom E, Stellaris, ST BlueNRG, STM32,
+STM32 QUAD/OCTO-SPI for Flash/FRAM/EEPROM, STMSMI, STR7x, STR9x, SWM050,
+TI CC13xx, TI CC26xx, TI CC32xx, TI MSP432, Winner Micro w600, Xilinx XCF,
+XMC1xxx, XMC4xxx.
+
+
+==================
+Installing OpenOCD
+==================
+
+A Note to OpenOCD Users
+-----------------------
+
+If you would rather be working "with" OpenOCD rather than "on" it, your
+operating system or JTAG interface supplier may provide binaries for
+you in a convenient-enough package.
+
+Such packages may be more stable than git mainline, where
+bleeding-edge development takes place. These "Packagers" produce
+binary releases of OpenOCD after the developers produces new "release"
+versions of the source code. Previous versions of OpenOCD cannot be
+used to diagnose problems with the current release, so users are
+encouraged to keep in contact with their distribution package
+maintainers or interface vendors to ensure suitable upgrades appear
+regularly.
+
+Users of these binary versions of OpenOCD must contact their Packager to
+ask for support or newer versions of the binaries; the OpenOCD
+developers do not support packages directly.
+
+A Note to OpenOCD Packagers
+---------------------------
+
+You are a PACKAGER of OpenOCD if you:
+
+- Sell dongles and include pre-built binaries;
+- Supply tools or IDEs (a development solution integrating OpenOCD);
+- Build packages (e.g. RPM or DEB files for a GNU/Linux distribution).
+
+As a PACKAGER, you will experience first reports of most issues.
+When you fix those problems for your users, your solution may help
+prevent hundreds (if not thousands) of other questions from other users.
+
+If something does not work for you, please work to inform the OpenOCD
+developers know how to improve the system or documentation to avoid
+future problems, and follow-up to help us ensure the issue will be fully
+resolved in our future releases.
+
+That said, the OpenOCD developers would also like you to follow a few
+suggestions:
+
+- Send patches, including config files, upstream, participate in the
+ discussions;
+- Enable all the options OpenOCD supports, even those unrelated to your
+ particular hardware;
+- Use "ftdi" interface adapter driver for the FTDI-based devices.
+
+
+================
+Building OpenOCD
+================
+
+The INSTALL file contains generic instructions for running 'configure'
+and compiling the OpenOCD source code. That file is provided by
+default for all GNU autotools packages. If you are not familiar with
+the GNU autotools, then you should read those instructions first.
+
+The remainder of this document tries to provide some instructions for
+those looking for a quick-install.
+
+OpenOCD Dependencies
+--------------------
+
+GCC or Clang is currently required to build OpenOCD. The developers
+have begun to enforce strict code warnings (-Wall, -Werror, -Wextra,
+and more) and use C99-specific features: inline functions, named
+initializers, mixing declarations with code, and other tricks. While
+it may be possible to use other compilers, they must be somewhat
+modern and could require extending support to conditionally remove
+GCC-specific extensions.
+
+You'll also need:
+
+- make
+- libtool
+- pkg-config >= 0.23 or pkgconf
+
+OpenOCD uses jimtcl library; build from git can retrieve jimtcl as git
+submodule.
+
+Additionally, for building from git:
+
+- autoconf >= 2.69
+- automake >= 1.14
+- texinfo >= 5.0
+
+Optional USB-based adapter drivers need libusb-1.0.
+
+Optional USB-Blaster, ASIX Presto and OpenJTAG interface adapter
+drivers need:
+ - libftdi: http://www.intra2net.com/en/developer/libftdi/index.php
+
+Optional CMSIS-DAP adapter driver needs HIDAPI library.
+
+Optional linuxgpiod adapter driver needs libgpiod library.
+
+Optional J-Link adapter driver needs libjaylink library.
+
+Optional ARM disassembly needs capstone library.
+
+Optional development script checkpatch needs:
+
+- perl
+- python
+- python-ply
+
+Permissions delegation
+----------------------
+
+Running OpenOCD with root/administrative permissions is strongly
+discouraged for security reasons.
+
+For USB devices on GNU/Linux you should use the contrib/60-openocd.rules
+file. It probably belongs somewhere in /etc/udev/rules.d, but
+consult your operating system documentation to be sure. Do not forget
+to add yourself to the "plugdev" group.
+
+For parallel port adapters on GNU/Linux and FreeBSD please change your
+"ppdev" (parport* or ppi*) device node permissions accordingly.
+
+For parport adapters on Windows you need to run install_giveio.bat
+(it's also possible to use "ioperm" with Cygwin instead) to give
+ordinary users permissions for accessing the "LPT" registers directly.
+
+Compiling OpenOCD
+-----------------
+
+To build OpenOCD, use the following sequence of commands:
+
+ ./bootstrap (when building from the git repository)
+ ./configure [options]
+ make
+ sudo make install
+
+The 'configure' step generates the Makefiles required to build
+OpenOCD, usually with one or more options provided to it. The first
+'make' step will build OpenOCD and place the final executable in
+'./src/'. The final (optional) step, ``make install'', places all of
+the files in the required location.
+
+To see the list of all the supported options, run
+ ./configure --help
+
+Cross-compiling Options
+-----------------------
+
+Cross-compiling is supported the standard autotools way, you just need
+to specify the cross-compiling target triplet in the --host option,
+e.g. for cross-building for Windows 32-bit with MinGW on Debian:
+
+ ./configure --host=i686-w64-mingw32 [options]
+
+To make pkg-config work nicely for cross-compiling, you might need an
+additional wrapper script as described at
+
+ https://autotools.io/pkgconfig/cross-compiling.html
+
+This is needed to tell pkg-config where to look for the target
+libraries that OpenOCD depends on. Alternatively, you can specify
+*_CFLAGS and *_LIBS environment variables directly, see "./configure
+--help" for the details.
+
+For a more or less complete script that does all this for you, see
+
+ contrib/cross-build.sh
+
+Parallel Port Dongles
+---------------------
+
+If you want to access the parallel port using the PPDEV interface you
+have to specify both --enable-parport AND --enable-parport-ppdev, since
+the later option is an option to the parport driver.
+
+The same is true for the --enable-parport-giveio option, you have to
+use both the --enable-parport AND the --enable-parport-giveio option
+if you want to use giveio instead of ioperm parallel port access
+method.
+
+
+==========================
+Obtaining OpenOCD From GIT
+==========================
+
+You can download the current GIT version with a GIT client of your
+choice from the main repository:
+
+ git://git.code.sf.net/p/openocd/code
+
+You may prefer to use a mirror:
+
+ http://repo.or.cz/r/openocd.git
+ git://repo.or.cz/openocd.git
+
+Using the GIT command line client, you might use the following command
+to set up a local copy of the current repository (make sure there is no
+directory called "openocd" in the current directory):
+
+ git clone git://git.code.sf.net/p/openocd/code openocd
+
+Then you can update that at your convenience using
+
+ git pull
+
+There is also a gitweb interface, which you can use either to browse
+the repository or to download arbitrary snapshots using HTTP:
+
+ http://repo.or.cz/w/openocd.git
+
+Snapshots are compressed tarballs of the source tree, about 1.3 MBytes
+each at this writing.
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README.Windows b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README.Windows
new file mode 100644
index 0000000..64bf5c0
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README.Windows
@@ -0,0 +1,56 @@
+Building OpenOCD for Windows
+----------------------------
+
+You can build OpenOCD for Windows natively with either MinGW-w64/MSYS
+or Cygwin (plain MinGW might work with --disable-werror but is not
+recommended as it doesn't provide enough C99 compatibility).
+Alternatively, one can cross-compile it using MinGW-w64 on a *nix
+host. See README for the generic instructions.
+
+Also, the MSYS2 project provides both ready-made binaries and an easy
+way to self-compile from their software repository out of the box.
+
+Native MinGW-w64/MSYS compilation
+-----------------------------
+
+As MSYS doesn't come with pkg-config pre-installed, you need to add it
+manually. The easiest way to do that is to download pkg-config-lite
+from:
+
+ http://sourceforge.net/projects/pkgconfiglite/
+
+Then simply unzip the archive to the root directory of your MinGW-w64
+installation.
+
+USB adapters
+------------
+
+For the adapters that use a HID-based protocol, e.g. CMSIS-DAP, you do
+not need to perform any additional configuration.
+
+For all the others you usually need to have WinUSB.sys (or
+libusbK.sys) driver installed. Some vendor software (e.g. for
+ST-LINKv2) does it on its own. For the other cases the easiest way to
+assign WinUSB to a device is to use the latest Zadig installer:
+
+ http://zadig.akeo.ie
+
+When using a composite USB device, it's often necessary to assign
+WinUSB.sys to the composite parent instead of the specific
+interface. To do that one needs to activate an advanced option in the
+Zadig installer.
+
+If you need to use the same adapter with other applications that may
+require another driver, a solution for Windows Vista and above is to
+activate the IgnoreHWSerNum registry setting for the USB device.
+
+That setting forces Windows to associate the driver per port instead of
+per serial number, the same behaviour as when the device does not contain
+a serial number. So different drivers can be installed for the adapter on
+different ports and you just need to plug the adapter into the correct
+port depending on which application to use.
+
+For more information, see:
+
+ https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-device-specific-registry-settings
+ http://www.ftdichip.com/Support/Knowledgebase/index.html?ignorehardwareserialnumber.htm
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README.macOS b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README.macOS
new file mode 100644
index 0000000..91d5e92
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/README.macOS
@@ -0,0 +1,54 @@
+Building OpenOCD for macOS
+--------------------------
+
+There are a few prerequisites you will need first:
+
+- Xcode (install from the AppStore)
+- Command Line Tools (install from Xcode -> Preferences -> Downloads)
+- Gentoo Prefix (http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap.xml)
+ or
+- Homebrew (http://mxcl.github.io/homebrew/)
+ or
+- MacPorts (http://www.macports.org/install.php)
+
+
+If you're building manually you need Texinfo version 5.0 or later. The
+simplest way to get it is to use Homebrew (brew install texinfo) and
+then ``export PATH=/usr/local/opt/texinfo/bin:$PATH``.
+
+
+With Gentoo Prefix you can build the release version or the latest
+devel version (-9999) the usual way described in the Gentoo
+documentation. Alternatively, install the prerequisites and build
+manually from the sources.
+
+
+With Homebrew you can either run:
+ brew install [--HEAD] openocd (where optional --HEAD asks brew to
+ install the current git version)
+ or
+ brew install libtool automake libusb [hidapi] [libftdi]
+ (to install the needed dependencies and then proceed with the
+ manual building procedure)
+
+
+For building with MacPorts you need to run:
+ sudo port install libtool automake autoconf pkgconfig \
+ libusb [libftdi1]
+
+You should also specify LDFLAGS and CPPFLAGS to allow configure to use
+MacPorts' libraries, so run configure like this:
+ LDFLAGS=-L/opt/local/lib CPPFLAGS=-I/opt/local/include ./configure [options]
+
+
+See README for the generic building instructions.
+
+If you're using a USB adapter and have a driver kext matched to it,
+you will need to unload it prior to running OpenOCD. E.g. with Apple
+driver (OS X 10.9 or later) for FTDI run:
+ sudo kextunload -b com.apple.driver.AppleUSBFTDI
+for FTDI vendor driver use:
+ sudo kextunload FTDIUSBSerialDriver.kext
+
+To learn more on the topic please refer to the official libusb FAQ:
+https://github.com/libusb/libusb/wiki/FAQ
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/exceptions/eCos-exception-2.0 b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/exceptions/eCos-exception-2.0
new file mode 100644
index 0000000..d21109f
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/exceptions/eCos-exception-2.0
@@ -0,0 +1,20 @@
+SPDX-Exception-Identifier: eCos-exception-2.0
+SPDX-URL: https://spdx.org/licenses/eCos-exception-2.0.html
+SPDX-Licenses: GPL-2.0-only, GPL-2.0-or-later
+Usage-Guide:
+ This exception is used together with one of the above SPDX-Licenses.
+ To use this exception add it with the keyword WITH to one of the
+ identifiers in the SPDX-Licenses tag:
+ SPDX-License-Identifier: WITH eCos-exception-2.0
+License-Text:
+
+As a special exception, if other files instantiate templates or use
+macros or inline functions from this file, or you compile this
+file and link it with other works to produce a work based on this
+file, this file does not by itself cause the resulting work to be
+covered by the GNU General Public License. However the source code for
+this file must still be made available in accordance with section (3)
+of the GNU General Public License.
+
+This exception does not invalidate any other reasons why a work based on
+this file might be covered by the GNU General Public License.
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/license-rules.txt b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/license-rules.txt
new file mode 100644
index 0000000..c751929
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/license-rules.txt
@@ -0,0 +1,275 @@
+# SPDX-License-Identifier: GPL-2.0-or-later OR GFDL-1.2-no-invariants-or-later
+
+OpenOCD licensing rules
+=======================
+
+The OpenOCD source code is provided under the terms of the GNU General
+Public License version 2 or later (GPL-2.0-or-later), as provided in
+LICENSES/preferred/GPL-2.0.
+
+The OpenOCD documentation is provided under the terms of the GNU Free
+Documentation License version 1.2 or later without Invariant Sections
+(GFDL-1.2-no-invariants-or-later).
+
+Few stand-alone applications coexist in the same code tree of OpenOCD
+and are provided under the terms of the GNU General Public License
+version 3 (GPL-3.0), as provided in LICENSES/stand-alone/GPL-3.0.
+
+This documentation file provides a description of how each source file
+should be annotated to make its license clear and unambiguous.
+It doesn't replace the OpenOCD's license.
+
+The license described in the COPYING file applies to the OpenOCD source
+as a whole, though individual source files can have a different license
+which is required to be compatible with the GPL-2.0:
+
+ GPL-1.0-or-later : GNU General Public License v1.0 or later
+ GPL-2.0-or-later : GNU General Public License v2.0 or later
+ LGPL-2.0 : GNU Library General Public License v2 only
+ LGPL-2.0-or-later : GNU Library General Public License v2 or later
+ LGPL-2.1 : GNU Lesser General Public License v2.1 only
+ LGPL-2.1-or-later : GNU Lesser General Public License v2.1 or later
+
+Aside from that, individual files can be provided under a dual license,
+e.g. one of the compatible GPL variants and alternatively under a
+permissive license like BSD, MIT etc.
+
+The common way of expressing the license of a source file is to add the
+matching boilerplate text into the top comment of the file. Due to
+formatting, typos etc. these "boilerplates" are hard to validate for
+tools which are used in the context of license compliance.
+
+An alternative to boilerplate text is the use of Software Package Data
+Exchange (SPDX) license identifiers in each source file. SPDX license
+identifiers are machine parsable and precise shorthands for the license
+under which the content of the file is contributed. SPDX license
+identifiers are managed by the SPDX Workgroup at the Linux Foundation and
+have been agreed on by partners throughout the industry, tool vendors, and
+legal teams. For further information see https://spdx.org/
+
+OpenOCD requires the precise SPDX identifier in all source files.
+The valid identifiers used in OpenOCD are explained in the section
+`License identifiers` and have been retrieved from the official SPDX
+license list at https://spdx.org/licenses/ along with the license texts.
+
+License identifier syntax
+-------------------------
+
+1. Placement:
+
+ The SPDX license identifier in OpenOCD files shall be added at the
+ first possible line in a file which can contain a comment. For the
+ majority of files this is the first line, except for scripts which
+ require the '#!PATH_TO_INTERPRETER' in the first line. For those
+ scripts the SPDX identifier goes into the second line.
+
+2. Style:
+
+ The SPDX license identifier is added in form of a comment. The comment
+ style depends on the file type::
+
+ C source: // SPDX-License-Identifier:
+ C header: /* SPDX-License-Identifier: */
+ ASM: /* SPDX-License-Identifier: */
+ makefiles: # SPDX-License-Identifier:
+ scripts: # SPDX-License-Identifier:
+ texinfo: @c SPDX-License-Identifier:
+ text: # SPDX-License-Identifier:
+
+ If a specific tool cannot handle the standard comment style, then the
+ appropriate comment mechanism which the tool accepts shall be used. This
+ is the reason for having the "/\* \*/" style comment in C header
+ files. There was build breakage observed with generated .lds files where
+ 'ld' failed to parse the C++ comment. This has been fixed by now, but
+ there are still older assembler tools which cannot handle C++ style
+ comments.
+
+3. Syntax:
+
+ A is either an SPDX short form license
+ identifier found on the SPDX License List, or the combination of two
+ SPDX short form license identifiers separated by "WITH" when a license
+ exception applies. When multiple licenses apply, an expression consists
+ of keywords "AND", "OR" separating sub-expressions and surrounded by
+ "(", ")" .
+
+ License identifiers for licenses like [L]GPL with the 'or later' option
+ are constructed by using a "-or-later":
+
+ // SPDX-License-Identifier: GPL-2.0-or-later
+ // SPDX-License-Identifier: LGPL-2.1-or-later
+
+ WITH should be used when there is a modifier to a license needed.
+ Exceptions can only be used with particular License identifiers. The
+ valid License identifiers are listed in the tags of the exception text
+ file.
+
+ OR should be used if the file is dual licensed and only one license is
+ to be selected. For example, some source files are available under dual
+ licenses:
+
+ // SPDX-License-Identifier: GPL-2.0-or-later OR BSD-1-Clause
+ // SPDX-License-Identifier: GPL-2.0-or-later OR BSD-2-Clause
+ // SPDX-License-Identifier: GPL-2.0-or-later OR BSD-3-Clause
+
+ AND should be used if the file has multiple licenses whose terms all
+ apply to use the file. For example, if code is inherited from another
+ project and permission has been given to put it in OpenOCD, but the
+ original license terms need to remain in effect::
+
+ // SPDX-License-Identifier: GPL-2.0-or-later AND MIT
+
+License identifiers
+-------------------
+
+The licenses currently used, as well as the licenses for code added to
+OpenOCD, can be broken down into:
+
+1. `Preferred licenses`:
+
+ Whenever possible these licenses should be used as they are known to be
+ fully compatible and widely used. These licenses are available from the
+ directory:
+
+ LICENSES/preferred/
+
+ in the OpenOCD source tree.
+
+ The files in this directory contain the full license text and
+ `Metatags`. The file names are identical to the SPDX license
+ identifier which shall be used for the license in source files.
+
+ Examples:
+
+ LICENSES/preferred/GPL-2.0
+
+ Contains the GPL version 2 license text and the required metatags.
+
+ `Metatags`:
+
+ The following meta tags must be available in a license file:
+
+ - Valid-License-Identifier:
+
+ One or more lines which declare which License Identifiers are valid
+ inside the project to reference this particular license text. Usually
+ this is a single valid identifier, but e.g. for licenses with the 'or
+ later' options two identifiers are valid.
+
+ - SPDX-URL:
+
+ The URL of the SPDX page which contains additional information related
+ to the license.
+
+ - Usage-Guidance:
+
+ Freeform text for usage advice. The text must include correct examples
+ for the SPDX license identifiers as they should be put into source
+ files according to the `License identifier syntax` guidelines.
+
+ - License-Text:
+
+ All text after this tag is treated as the original license text
+
+ File format examples::
+
+ Valid-License-Identifier: GPL-2.0
+ Valid-License-Identifier: GPL-2.0-only
+ Valid-License-Identifier: GPL-2.0-or-later
+ SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
+ Usage-Guide:
+ To use this license in source code, put one of the following SPDX
+ tag/value pairs into a comment according to the placement
+ guidelines in the licensing rules documentation.
+ For 'GNU General Public License (GPL) version 2 only' use:
+ SPDX-License-Identifier: GPL-2.0
+ or
+ SPDX-License-Identifier: GPL-2.0-only
+ For 'GNU General Public License (GPL) version 2 or any later version' use:
+ SPDX-License-Identifier: GPL-2.0-or-later
+ License-Text:
+ Full license text
+
+2. Exceptions:
+
+ Some licenses can be amended with exceptions which grant certain rights
+ which the original license does not. These exceptions are available
+ from the directory::
+
+ LICENSES/exceptions/
+
+ in the OpenOCD source tree. The files in this directory contain the full
+ exception text and the required `Exception Metatags`_.
+
+ Examples::
+
+ LICENSES/exceptions/eCos-exception-2.0
+
+ Exception Metatags:
+
+ The following meta tags must be available in an exception file:
+
+ - SPDX-Exception-Identifier:
+
+ One exception identifier which can be used with SPDX license
+ identifiers.
+
+ - SPDX-URL:
+
+ The URL of the SPDX page which contains additional information related
+ to the exception.
+
+ - SPDX-Licenses:
+
+ A comma separated list of SPDX license identifiers for which the
+ exception can be used.
+
+ - Usage-Guidance:
+
+ Freeform text for usage advice. The text must be followed by correct
+ examples for the SPDX license identifiers as they should be put into
+ source files according to the `License identifier syntax`_ guidelines.
+
+ - Exception-Text:
+
+ All text after this tag is treated as the original exception text
+
+ File format examples::
+
+ SPDX-Exception-Identifier: eCos-exception-2.0
+ SPDX-URL: https://spdx.org/licenses/eCos-exception-2.0.html
+ SPDX-Licenses: GPL-2.0-only, GPL-2.0-or-later
+ Usage-Guide:
+ This exception is used together with one of the above SPDX-Licenses.
+ To use this exception add it with the keyword WITH to one of the
+ identifiers in the SPDX-Licenses tag:
+ SPDX-License-Identifier: WITH eCos-exception-2.0
+ License-Text:
+ Full license text
+
+3. Stand-alone licenses:
+
+ These licenses should only be used for stand-alone applications that are
+ distributed with OpenOCD but are not included in the OpenOCD binary.
+ These licenses are available from the directory:
+
+ LICENSES/stand-alone/
+
+ in the OpenOCD source tree.
+
+ Examples:
+
+ SPDX-License-Identifier: GPL-3.0
+
+The format and requirements of the license files in the other sub-directories
+of directory
+
+ LICENSES
+
+have to follow the same format and requirements of the `Preferred licenses`.
+
+All SPDX license identifiers and exceptions must have a corresponding file
+in the LICENSES subdirectories. This is required to allow tool
+verification (e.g. checkpatch.pl) and to have the licenses ready to read
+and extract right from the source, which is recommended by various FOSS
+organizations, e.g. the `FSFE REUSE initiative `.
diff --git a/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/preferred/BSD-1-Clause b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/preferred/BSD-1-Clause
new file mode 100644
index 0000000..c63b05b
--- /dev/null
+++ b/openocd-win/openocd/distro-info/licenses/openocd-0.12.0/preferred/BSD-1-Clause
@@ -0,0 +1,28 @@
+Valid-License-Identifier: BSD-1-Clause
+SPDX-URL: https://spdx.org/licenses/BSD-1-Clause.html
+Usage-Guide:
+ To use the BSD 1-clause License put the following SPDX
+ tag/value pair into a comment according to the placement guidelines in
+ the licensing rules documentation:
+ SPDX-License-Identifier: BSD-1-Clause
+License-Text:
+
+Copyright (c)