Cleanup build system and configuration.

* Drop unused variables from build system that refer to the system
libraries.
* Drop unused lists of libgcc objects.
* Drop no longer used variables from co

Cleanup build system and configuration.

* Drop unused variables from build system that refer to the system
libraries.
* Drop unused lists of libgcc objects.
* Drop no longer used variables from configuration script.
* Remove no longer needed building of kernel-libgcc and -libsupc++ from
build_cross_tools_gcc4, only the boot-specific (32-bit) libs are
built for a x86_64 target.
* Explicitly disable threads and TLS support when building the cross
compiler, as the only libraries that are used by Haiku's build system
is the 32-bit libgcc and libsupc++ for the bootloader on x86_64 (and
for that neither is wanted).

show more ...

Add a nasm test for ELF generation

We should probably only test this when targetting x86 arch...

Update version of legacy compiler.

Drop unused variable HAIKU_GCC_GLUE_CODE_<target_arch>

Fix configure --help to not rely on gcc.

* Make sure that the invocation of 'configure --help', 'configure -h' or
just 'configure' will show the usage text and exit.

Add support for specifying the host compiler with CC.

* On some systems, the host compiler may not be called 'gcc', so allow
overriding the default via the CC environment variable.

configure: correct documentation of the -j<N> option. Fixes #10828.

Add new configuration option --no-downloads.

* If --no-downloads has been given, Haiku will be built without
trying to download anything, all required packages need to be put
into the download f

Add new configuration option --no-downloads.

* If --no-downloads has been given, Haiku will be built without
trying to download anything, all required packages need to be put
into the download folder manually (the build will stop on missing
packages).
* As the required HaikuPorts repository can't be downloaded in this
mode, a local repository is created during the build, which only
contains the packages available in the downloads folder.

This is useful for building Haiku completely from source.

show more ...

build: Fix raspberry_pi target board name. Not pi

configure: correct check for haikuporter from directory to file

Whitespace fixes.

Abort configure script if haikuports, haikuports cross and haikuporter directories do not exist.

Signed-off-by: Jessica Hamilton <jessica.l.hamilton@gmail.com>

configure: allow setting HAIKU_BOOT_BOARD

* Since this affects generated objects and needs a clean build anyway,
it is better set and fixed at configure time.
* It could also be used when building t

configure: allow setting HAIKU_BOOT_BOARD

* Since this affects generated objects and needs a clean build anyway,
it is better set and fixed at configure time.
* It could also be used when building the cross compiler to set
appropriate options.

show more ...

Add --use-clang option to configure

This also adjusts the jam files to not use $(CLANG) anymore.

Sorry, my last commit was incomplete

Switch back from yasm to nasm

These days, nasm supports more instructions than yasm. Additionally, it
offers a disassembler.

mips: Remove mips

* As per the ML discussions. Bumps MIPS to tier 3.
* We've reached a unanimous descision that MIPS doesn't
target any real / valid hardware Haiku wants to pursue
at the moment.

mips: Remove mips

* As per the ML discussions. Bumps MIPS to tier 3.
* We've reached a unanimous descision that MIPS doesn't
target any real / valid hardware Haiku wants to pursue
at the moment. In the event that anyone wants to pursue
MIPS, feel free to fork Haiku into your own repository
(and we'll even link to it on the website ports page)
* If someone develops a viable plan for MIPS (and gets the
port working, it can be readded at a later date)

show more ...

configure: --use-gcc-pipe now affects build_cross_tools_gcc4.

build_cross_tools_gcc4: unbreak --use-gcc-graphite.

* added -pipe to CFLAGS, builds are faster and /tmp usage is avoided at the
cost of more memory used.
* replaced ppl by isl as required by gcc 4.8

Drop --remote-user configuration option again.

* as Ingo has pointed out, the remote user settings doesn't
relate to the build configuration at all, so setting the
remote user via HAIKU_REMOTE_U

Drop --remote-user configuration option again.

* as Ingo has pointed out, the remote user settings doesn't
relate to the build configuration at all, so setting the
remote user via HAIKU_REMOTE_USER in UserBuildConfig or
via shell environment is the way to go
* additionally: drop debug output

show more ...

Add support for specifying remote ssh login user.

* add option --remote-user to configure, which sets HAIKU_REMOTE_USER
* add evaluation of HAIKU_REMOTE_USER variable when ssh-ing
into git.haiku-o

Add support for specifying remote ssh login user.

* add option --remote-user to configure, which sets HAIKU_REMOTE_USER
* add evaluation of HAIKU_REMOTE_USER variable when ssh-ing
into git.haiku-os.org

show more ...

x86_64: include the "32" dir when targeting 32-bit

* helps with building boot loader with GCC 4.8

configure: Fix for whitespace in path (2nd try)

May fix #10170.

Revert "configure: Fix for whitespace in path"

This reverts commit 5369d17d119d1ae8e496805ed7c820bbfaa9accd.

Breaks the build. Take the walk of shame.

configure: Fix for whitespace in path

May fix #10170.