Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... though none are provided by default.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
This partially reverts commit 429b3e884662a3b9a72890aae23865501e66330f.
Bring back the patches for glibc 2.12 and newer. Propagate/refresh
some patches as needed.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
This partially reverts commit 88e8852ccd94a60979971454f8b49cb1d06cd907.
Bring back releases 2.12 and newer of glibc, along with the associated
Kconfig machinery. Simplify it slightly.
|
|
This reverts commit 39273e0843cc5f7f91d50651b299a0472f59f472.
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
ARM with arch suffix - elf2flt fix
|
|
... that exhibited the issue with elf2flt configuration. Original reported
did not provide the config, and did not respond.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
CT_TARGET is composed as "${CT_ARCH}${CT_ARCH_SUFFIX}", so CT_TARGET may
become something like "armv7", for example. This is used by the configure
script to set the "CPU" variable in the Makefile, leading to a commad line
containing
-DTARGET_armv7 -DTARGET_CPU="armv7"
In this case the compilation of elf2flt.c fails with "Don't know how to
support your CPU architecture??". Passsing "CPU=${CT_ARCH}" in the make
command line overrides the configured value and solves the problem.
Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
|
|
Enable WCHAR in a sample
|
|
Pick up upstream fixes in elf2flt
|
|
Remove "pre-declaration" of config options
|
|
... these are apparently not needed with the current kconfig and only
result in warnings like "SYMBOL changed state" and "reassigning SYMBOL".
Perhaps, it was necessary to run kconfig without first generating
config.gen? But now all the targets that invoke $(CONF) have
`config_files` as a dependency.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... including zlib fix in configure, needed to build canadian crosses
with elf2flt.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... needed to build canadian cross on top of it.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Allow some tunables for ncurses
|
|
Update kernel & glibc
|
|
3 unrelated uClibc changes, see individual commits
|
|
Add zlib as a companion lib
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
with version 1.2.11.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
- Allow user to specify configure arguments to pass through to host/target
ncurses.
- Checkbox for --disable-database
- String option for --with-fallbacks
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
instead of 'make oldconfig' and responding 'y'. This avoids 'Broken pipe'
errors in the log, as well as selects default setting for all options not
explicitly set.
This requires a small fix in the old uClibc. Won't have to maintain that fix
for long though :)
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
It has not seen any new commits since July 2015, and haven't had any
releases since May 2012.
The only two architectures marked as supported by uClibc but not by
uClibc-ng are v850 and i960. Both are marked as "BROKEN" in the most
recent release of uClibc, 0.9.33.2.
RIP, uClibc.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
It has been (incompletely) removed since 1.0.21.
Requested-by: Waldemar Brodkorb <wbx@uclibc-ng.org>
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Uclibc 1.0.22
|
|
Check for C++ in configure
|
|
Require C++ support for gdbserver 7.12 or newer
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... and declare 1.0.21 obsolete.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Also, do not select gdbserver for cross-gdb automatically, or it may
be selected even without meeting the dependencies (if C++ is not enabled)
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Recent GMP/GCC/GDB releases require c++.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Fix build manuals
|
|
Fix gentoo hang
|
|
This serves two purposes:
- installs its manpage
- installs headers, without them it does not make sense to install a
static library
Unfortunately, there's no way to select shared-only build of DUMA.
Hence, disable selection for static library.
Also, allow user to select whether to use stock or ct-ng's wrapper.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
It was running 'make gas ld ...', which was succeeding, but didn't install
anything.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... to work around Gentoo's wrapper idiosyncrasy.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... will be used to implement a smarter install wrapper.
While there, correct the spelling of "OVERIDE".
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Bump autoconf requirement to 2.65
Trivial, merged immediately.
|
|
Required by automake 1.15.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Enable Fortran & tools in x86_64-w64-mingw
|
|
... both were recently a source of bug that didn't manifest on *-linux-*
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Rework configure logic wrt GNU autotools
|
|
Add a workaround for musl in build scripts
|
|
Rather than requiring them of a certain version, detect if they are present
(and have sufficient version) and select an appropriate companion tool
otherwise. The reason is that, for example, most recent gettext requires
automake 1.15, but the newest available CentOS has 1.13. Hence, the option
to "upgrade your system" does not apply, and the warning comment above
the companion tools is rather scary.
With this approach, it will work out of the box - either by using the host's
tools, or by building them as needed. Note that the user can still change
the setting in the config.
While there, propagate the new version checking macro to awk/bash/host binutils,
and switch from --with-foo=xxx to officially blessed FOO=xxx: the latter
does not require checking for bogus values (i.e., --with-foo, --without-foo)
and AC_PROG_* macros recognize the corresponding settings without further
modifications. For now, I kept --with-foo=, if only to complain and steer
people to the new way. To be cleaned up after a release.
Signed-off-by: Alexey Neyman <stilor@att.net>
|