| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Add an initial wrapper:
- find the realpath of the tool being called
- add the '.' in front of the tool name
- add the '/lib' dir to the base dir of the tool
- set and export LD_LIBRARY_PATH
- execve the real tool
|
| | |
| |
| |
| |
| | |
table of content: add missing entry
the hacker's way: no need to "make install"
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Downoading a non-existing file from sourceforge gives you a "200 OK"
and an index.html. As we try to retrieve a .tar.bz2 first, and duma
is bundled in a .tar.gz, we won't get appropriate content, so
just force the extension to avoid the problem.
Thanks to Ingmar Schraub <is@eseco.de> for pointing out the issue.
|
| | | |
|
| |/
|
|
| |
DUMA uses '_' not '.' for major/minor/sub separation.
|
| |
|
|
|
|
| |
During the conversion to using bash arrays, the glibc build script
was improperly converted, and contains an incorrect variable
assignment to the config_options array.
|
| |\
| |
| |
| |
| |
| | |
For every components where it makes sense, use bash arrays (instead
of a string with space-separated values) to store the options pased
to ./configure.
|
| | |
| |
| |
| |
| | |
Some setups require one to pass extra CXX flags at the time of ./configure.
Make it easy.
|
| | | |
|
| | |
| |
| |
| | |
Change extra_config from a string to a array of options.
|
| | |
| |
| |
| | |
Change extra_config from a string to a array of options.
|
| | |
| |
| |
| | |
Change extra_config from a string to a array of options.
|
| | |
| |
| |
| | |
Change extra_config from a string to a array of options.
|
| | |
| |
| |
| | |
Change extra_config from a string to a array of options.
|
| | |
| |
| |
| | |
This is required to use the array variables that came with bash-3.1.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rewrite part of the code to better match the rest.
Most notably, rewrite handling of:
if [ ... ] && [ ... ]
to:
if [ ... -a ... ]
This has the positive side effect of calling "[" only once, although
"[" is probably a shell built-in.
|
| | |
| |
| |
| |
| |
| |
| | |
To test for existing files, use "[ -f blabla ]", not "[ -a blabla ]"
Checking for a file exsitence with "-a" is a bashism.
Althoug we _are_ using bash, it's disturbing as it can be misread as
the 'and' operator. Fix by using "-f".
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Add a few lines of explanations on how to correctly setup
and use Mercurial to send proper patches.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The URL for the crosstool-NG homepage has changed. Update the
README accordingly. The old URL is still valid, though.
|
| | | |
| | |
| | |
| | | |
Move the gcc-4.3.4 version to its place.
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When compiling some C++ code, GCC 4.3.x fails with an internal
compiler error. The bug report is available at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37436. The included patch
is the one that has been merged in the trunk of gcc.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some components (eg. GMP) will fail to correctly build if
the CONFIG_SHELL is not bash (eg. ash or dash). So make bash
the default CONFIG_SHELL.
Keep ash as a possible selection, as future versions of those
currently /broken/ tools may come fixed wrt to CONFIG_SHELL
being POSIX-ly compliant.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The tmul test uses a compiled-in input file in $(srcdir).
The problem is that the Makefile passes it unquoted. The C code
tries to stringify it using clever macros, which may *usually* work.
In my case the source directory was named:
.../toolchain-powerpc-e500v2-linux-gnuspe-1.0-2.fc10/.../tests
And guess what? During testing I found out the program fails because
it tries to open:
.../toolchain-powerpc-e500v2-1-gnuspe-1.0-2.fc10/.../tests
Yes, CPP tokenized the macro before stringifying it and not surprisingly
the 'linux' part was converted to 1.
[on Fedora-10: cpp (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)]
So the attached patch simplify the macros and pass the path as string
from the Makefile.
|
| |\ \ \ |
|
| | |\ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The wrapper script placed around the target binaries when
using the companion libraries does not work for symbolic links
The wrapper scripts needs to follow the links before calling the
actual binary
Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
---
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Because gmp is now always build with --enable-cxx,
g++ has become a required tool
Signed-off-by: Bart vdr Meulen <bartvdrmeulen@gmail.com>
---
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Add gcc-4.4.1
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Handle gcc-4.4+ when adding a new gcc version.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Add 4.3.0 and 4.3.1.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Add libelf 0.8.11, propagate patchset from 0.8.10.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Add latest branch 2_10.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Add ltrace 0.5.2, propagate patchset from 0.5.1 and from Debian.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Add 2.5.15, propagate patchset from 2_5_14 up to 2_5_15.
|
