| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Add the possibility to fallback to either bundled or local patches
if local or bundled are missing.
|
|
This ordering first applies the local patches, then the bundeld ones.
|
|
|
|
|
|
|
|
In the C wrapper, the argc argument is not used, causing an error
(as we treat warnings as errors). Use a dummy allocation to get
rid of the warning.
|
|
When building the C wrapper, specify the source file to be compiled.
|
|
The "Build shared libraries" config option is dependant on the type of
"Target OS".
Moving this options to the "Target OS" sub-menu is also better in the user
perspective: he/she no longer needs to go back and forth to see if he/she
missed any option.
|
|
Now that all kernels that support shared libraries select the correct config
option, we can change the dependency rules of SHARED_LIBS accordingly.
|
|
The Linux kernel supports using shared libraries, so prompt the user.
|
|
The target OSes will be able to select this option if they support shared
libraries, instead of having "Build shared libaries" depend on each OS.
|
|
ltrace, in the debug sub-menu, selects libelf, in the tools sub-menu.
Inverse the order of the two sub-menus, so that the user does not have
to go back and forth between the two sub-menus.
|
|
Move the companion libraries sub-menu down the main menu.
That way, the user does not need to go back and forth in the menu
to change options set by the different components that select the
companion libraries (binutils, gcc, gdb).
|
|
The PPL, CLoog/ppl and MPC libraries require GMP and MPFR.
Select GMP/MPFR appropriately.
|
|
Add the WRAPPER_NEEDED silent config option, that can be selected by
components that require it (companion libs so far).
Rely on this config option when deciding to install the wrapper,
instead of checking GMP/MPFR or PPL/CLoog/MPC.
|
|
|
|
Offer a config choice on whether to isntall the script wrapper, or
the compiled C wrapper. Update docs/overview.txt accordingly.
|
|
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.
|
|
|
|
It apears that more and more ./configure scripts and Makefiles
make use of non-POSIXly correct shell constructs, that don't
work with ash.
For now, just warn the user against using ash, but keep it as
an option in case newer versions of the /broken/ components
come fixed, and we can again use ash, as it is in some cases
really faster than bash.
|
Yann E. MORIN"
Ingmar Schraub
Jim F
Giammarco Zacheo
Thomas Petazzoni
Oron Peled