Age | Commit message (Collapse) | Author | Files | Lines |
|
... when determining if it can be linked statically, and if Python
scripting should default to y.
Prompted by a failure of i686-w64-mingw32,nios2-spico-elf sample
on a system where configure didn't report static linking support.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Remove explicit core passes selection for multilib
|
|
It is only used if this libc flavor uses a multilib iterator (and not
determines the multilibs itself). This class currently includes glibc,
uClibc, musl - but they explicitly select CC_CORE_PASSES_NEEDED anyway.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Fix up the sysroot issue for sh4 in a different way
|
|
(see the comments in the code for details on the issue)
Old workaround in 100-gcc.sh stopped working (probably, due to one
of GCC version upgrades), so switch to the other approach originally
described there: adjust the list of multilibs to not include the
default target explicitly.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Go into subdirectory when checksumming/signing
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Do not create multilib symlinks if not using sysroot
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Fix unclosed string
|
|
... that resulted in a warning from kconfig
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Make creation of ld.so.conf optional
|
|
... enabled by default for multilib and disabled otherwise. Buildroot
has been complaining about /etc/ld.so.conf presence for almost a year
now and I missed that.
After the release, xldd will be modified to query the compiler for
the list of multilibs to search. This would be too invasive change
before 1.23, though.
Note that it may lead to configurations where xldd currently does not
find the libraries (if both DEMULTILIB and CREATE_LDSO_CONF are turned
off). This is not the default setting in Kconfig, though.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Add tarball signing to release script
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Release mgmt
|
|
One TBD left is the signing of the tarballs.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... which are not of much interest to the end user.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Hot fix for 'make install'
|
|
... while I continue to work on release script.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Run samples through an update
|
|
Cross-ldd: handling e_flags is tricky and depends on arch
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Move documents to github.io
|
|
elf2flt: patch has been accepted upstream
|
|
sh*-*-linux-gnu can use GCC6 now
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Will be pulled into release tarball by a release script.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
When moving gcc libs, prefer the same directory as libc
|
|
It turns out buildroot does not currently accept a toolchain where a dynamic
linker does not reside in the multi-os-directory. Unfortunately this is
how glibc installs itself on AArch64 without any extra tricks.
So, provide an option to force everything into /lib or /usr/lib; patch to
buildroot will be worked on separately.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
GCC does not distinguish the resulting binary by the CFLAGS (e.g. based
on which -march= was given). This means, while it will use the right
libraries for linking, at runtime they are all going to request the same
ld.so path and load the libraries from the same default path.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... and default to 'n'.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... as we are going through various multilibs in ld.so.conf
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Also a fix for CT_IterateMultilibs: it didn't pass multi_os_dir_gcc, so
it only worked if the caller did *not* declare it as a local variable.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Convert absolute targets to relative so that they are valid on the host,
too. The procedure is very similar to uclibc, so it is moved into a
common function.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
... and in addition to final toolchain aliasing, use it when configuring
multilibs for glibc/musl. Note that uClibc does not need it, it is
explicitly selecting the tools using CROSS_PREFIX.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
mingw-w64: no <malloc.h> on macos
|
|
binutils 2.23 and earlier are not affected, they had the correct code.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
4.0.6 is the only one not marked obsolete.
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Disable Guile in make if building for host in canadian
|
|
Add ARM patches for 2.12.2/2.13
|
|
Patch from upstream fixing dlopen from a static app
|
|
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
Reported-by: Austin Beer (brainwave64)
Signed-off-by: Alexey Neyman <stilor@att.net>
|
|
make's configure uses pkg-config to detect if Guile should be enabled;
on ArchLinux, this picks up Guile from build machine's pkgconfig and then
it fails to compile.
A better solution might be to create a ${CT_HOST}-pkg-config in
buildtools/bin that would report "unsupported" for all packages.
However a quick grep only showed pkg-config being used by GCJ
(not sure if it will build in canadian cross - we don't have any
samples with GCJ) and Blackfin simulator in GDB (Blackfin is not
currently supported by crosstool-ng). Hence, leave such pkg-config
implementation and testing for another day.
Signed-off-by: Alexey Neyman <stilor@att.net>
|