summaryrefslogtreecommitdiff
path: root/utils/gddrescue/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* gddrescue: update to 1.27Lucian Cristian2023-02-241-4/+2
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* gddrescue: update to 1.26Lucian Cristian2022-06-011-4/+6
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* treewide: remove uClibc++ supportRosen Penev2021-03-051-3/+2
| | | | Signed-off-by: Rosen Penev <rosenp@gmail.com>
* gddrescue: Remove uClibc++ patchRosen Penev2019-10-121-3/+3
| | | | | | | | | | A solution was applied to uClibc++, where the bug actually is. Fixed license information. Small cleanups. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* gddrescue: Add uClibc-ng supportRosen Penev2019-07-251-2/+2
| | | | | | | | | | It turns out, this breaks only when compiling with both uClibc-ng and uClibc++. If the libc or libc++ gets swapped out, it compiles fine. libstdcpp is fine because it already undefs these macros. The actual bug is probably in uClibc-ng but this is a fine workaround. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* gddrescue: Do not build with uClibc-ngRosen Penev2019-07-161-1/+1
| | | | | | | | | | | | | | | From the developer: It seems that uClibc-ng is defining fgetc, fputc, feof, and ferror as macros and not including them in std. IMO this is a bug in uClibc-ng (maybe caused by lack of clarity in the C++ standard), because even the C functions that are alowed to be defined as macros (putc, getc) should be included in std for consistency. Just imagine the chaos if std::getc were defined or undefined depending on how it is implemented. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* gddrescue: add ddrescue a data recovery toolLucian Cristian2019-03-291-0/+51
Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>