This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "uClibc-ng - small C library for embedded systems".
The branch, master has been updated
via 3d39f1ae2b2bb9f2aa30eee4b34486b03e24c175 (commit)
via c5722d63ede04b656c7ac8607d075db576a226d8 (commit)
via 6fc08ddc732c8c0a56391d30d4e86aa46bda5495 (commit)
via c08e51d9a9a598e31bf4dcc51afa52388ee99050 (commit)
via e6ab5f05c89550d15e07e9eab2e2623494f60dca (commit)
from b7967026760157bbbfc4fb9db6862cd2085bb0d9 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 3d39f1ae2b2bb9f2aa30eee4b34486b03e24c175
Author: Waldemar Brodkorb <wbx(a)openadk.org>
Date: Sun Dec 28 23:08:54 2014 -0600
remove comment
commit c5722d63ede04b656c7ac8607d075db576a226d8
Author: Waldemar Brodkorb <wbx(a)openadk.org>
Date: Sun Dec 28 23:05:39 2014 -0600
reduce some unneeded warnings.
commit 6fc08ddc732c8c0a56391d30d4e86aa46bda5495
Author: Waldemar Brodkorb <wbx(a)openadk.org>
Date: Sun Dec 28 22:55:38 2014 -0600
remove hidden warning option, not useful for others.
commit c08e51d9a9a598e31bf4dcc51afa52388ee99050
Author: Waldemar Brodkorb <wbx(a)openadk.org>
Date: Sun Dec 28 22:51:58 2014 -0600
fix warning when doing make clean
commit e6ab5f05c89550d15e07e9eab2e2623494f60dca
Author: Waldemar Brodkorb <wbx(a)openadk.org>
Date: Sun Dec 28 22:51:11 2014 -0600
update INSTALL
-----------------------------------------------------------------------
Summary of changes:
INSTALL | 46 ++++++++++++++++++++++------------------------
Rules.mak | 3 ---
extra/Configs/Config.in | 7 -------
libc/stdio/_stdio.c | 1 -
libc/stdio/fflush.c | 2 --
libc/stdio/popen.c | 2 --
test/unistd/Makefile.in | 4 +++-
7 files changed, 25 insertions(+), 40 deletions(-)
diff --git a/INSTALL b/INSTALL
index 78fe3fc..058c021 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,21 +1,20 @@
SOFTWARE REQUIREMENTS
- Compiling uClibc requires Linux kernel header files. uClibc will
+ Compiling uClibc-ng requires Linux kernel header files. uClibc-ng will
be compiled to match the interfaces available in the provided
- version of the Linux kernel headers. Linux kernel version 2.0,
- version 2.2, version 2.4 and version 2.6 are known to work. Other
- kernel versions may work but haven't been tested. Its also helpful
- to have a working version of GNU binutils, and GNU gcc -- using
- excessively old versions of these packages can cause very strange
- errors that are difficult to find and fix.
+ version of the Linux kernel headers. Linux kernel version 3.x is
+ supported.
+ Its also helpful to have a working version of GNU binutils, and
+ GNU gcc -- using excessively old versions of these packages can
+ cause very strange errors that are difficult to find and fix.
-CONFIGURING uClibc:
+CONFIGURING uClibc-ng:
- - Users must have a valid configuration file to compile uClibc. Do not
+ - Users must have a valid configuration file to compile uClibc-ng. Do not
skip this step. New configuration options are added in each
release, and odd configuration options are sometimes removed.
- To configure uClibc, you can run:
+ To configure uClibc-ng, you can run:
make menuconfig
or
@@ -39,10 +38,10 @@ CONFIGURING uClibc:
"make allnoconfig" Set all values to "no" for all options.
-COMPILING uClibc:
+COMPILING uClibc-ng:
- - uClibc does not have proper dependancy checking (yet) so if you
- change your uClibc configuration, you must current rebuild the
+ - uClibc-ng does not have proper dependancy checking so if you
+ change your uClibc-ng configuration, you must current rebuild the
entire library, by first running
make clean
@@ -51,30 +50,29 @@ COMPILING uClibc:
make
- to compile uClibc. or if you are cross compiling, you would
+ to compile uClibc-ng. or if you are cross compiling, you would
instead run something like:
make CROSS_COMPILE=arm-linux-
-INSTALLING the uClibc development environment:
+INSTALLING the uClibc-ng development environment:
- As root, if necessary, run something like:
make PREFIX=<some path> install
- This will install the uClibc runtime and development system (i.e.
+ This will install the uClibc-ng runtime and development system (i.e.
all the header files, libraries, etc) into the directories defined
within your .config file.
-USING uClibc:
+USING uClibc-ng:
- - To compile programs with uClibc you will need a complete toolchain
- (i.e. binutils, gcc, and uClibc) that was built expressly for use
- with uClibc.
+ - To compile programs with uClibc-ng you will need a complete toolchain
+ (i.e. binutils, gcc and uClibc-ng) that was built expressly for use
+ with uClibc-ng.
- - Native and cross compiling toolchains, as well as makefiles for creating
- uClibc toolchains, are available from the uClibc website. You may want
- to check out "buildroot", which is available from the uClibc download
area,
- which provides examples of how to build your own uClibc based system.
+ - You have two choices at the moment:
+ - Use OpenADK from
http://www.openadk.org
+ - Use your own build scripts or environment
diff --git a/Rules.mak b/Rules.mak
index 218eb1f..2a73d7f 100644
--- a/Rules.mak
+++ b/Rules.mak
@@ -67,9 +67,6 @@ AWK = awk
STRIP_FLAGS ?= -x -R .note -R .comment
-## unused? if yes, remove after 0.9.31
-## UNIFDEF := $(top_builddir)extra/scripts/unifdef
-
# Select the compiler needed to build binaries for your development system
HOSTCC = gcc
BUILD_CFLAGS = -Os
diff --git a/extra/Configs/Config.in b/extra/Configs/Config.in
index fab0ddc..5d0f4f0 100644
--- a/extra/Configs/Config.in
+++ b/extra/Configs/Config.in
@@ -2483,11 +2483,4 @@ config DOMULTI
If unsure, keep the default of N.
-config UCLIBC_MJN3_ONLY
- bool "Manuel's hidden warnings"
- help
- Answer Y here to see all Manuel's personal notes, warnings, and todos.
-
- Most people will answer N.
-
endmenu
diff --git a/libc/stdio/_stdio.c b/libc/stdio/_stdio.c
index 388a211..ee247a5 100644
--- a/libc/stdio/_stdio.c
+++ b/libc/stdio/_stdio.c
@@ -195,7 +195,6 @@ void _stdio_term(void)
* chain might be corrupt due to a partial store.
*/
STDIO_INIT_MUTEX(_stdio_openlist_add_lock);
-#warning check
#ifdef __STDIO_BUFFERS
STDIO_INIT_MUTEX(_stdio_openlist_del_lock);
#endif
diff --git a/libc/stdio/fflush.c b/libc/stdio/fflush.c
index d9104a4..cf0356a 100644
--- a/libc/stdio/fflush.c
+++ b/libc/stdio/fflush.c
@@ -97,8 +97,6 @@ int fflush_unlocked(register FILE *stream)
while(stream) {
/* We only care about currently writing streams and do not want to
* block trying to obtain mutexes on non-writing streams. */
-#warning fix for nonatomic
-#warning unnecessary check if no threads
if (__STDIO_STREAM_IS_WRITING(stream)) { /* ONLY IF ATOMIC!!! */
__MY_STDIO_THREADLOCK(stream);
/* Need to check again once we have the lock. */
diff --git a/libc/stdio/popen.c b/libc/stdio/popen.c
index 40a6dda..e1b1d40 100644
--- a/libc/stdio/popen.c
+++ b/libc/stdio/popen.c
@@ -124,8 +124,6 @@ FILE *popen(const char *command, const char *modes)
return NULL;
}
-#warning is pclose correct wrt the new mutex semantics?
-
int pclose(FILE *stream)
{
struct popen_list_item *p;
diff --git a/test/unistd/Makefile.in b/test/unistd/Makefile.in
index 44ff360..6f8a274 100644
--- a/test/unistd/Makefile.in
+++ b/test/unistd/Makefile.in
@@ -1,9 +1,10 @@
# uClibc unistd tests
# Licensed under the LGPL v2.1, see the file COPYING.LIB in this tarball.
+TESTS_DISABLED :=
# If LFS is not set, get rid of all *64 tests up front
ifeq ($(UCLIBC_HAS_LFS),)
-TESTS_DISABLED := tst-preadwrite64 tst-posix_fallocate64 tst-fallocate64
+TESTS_DISABLED += tst-preadwrite64 tst-fallocate64
endif
# If we don't have LINUX_SPECIFIC, then get rid of tst-fallocate
@@ -29,6 +30,7 @@ else
# reordering is not supported, behaves as if POSIXLY_CORRECT would be set
OPTS_tstgetopt := -a -b -cfoobar --required foobar --optional=bazbug --none --colou
--color --colour random
endif
+
# for embedded systems 4 GB disk space is not available
TESTS_DISABLED += tst-posix_fallocate64
hooks/post-receive
--
uClibc-ng - small C library for embedded systems