Age | Commit message (Collapse) | Author | Files | Lines |
|
- Don't parallelise the perl build as libdummy.so must be built before
building {cpan,ext}/.
- Iteratively append ${PKG_CFLAGS_CONFIGURE} to ccflags when building
perl as environment variables aren't considered by the configure script.
- Add missing build step `build_dir' to build.usage.
- Force the perk prefix to /usr rather than the default value of /usr/local.
|
|
- General cleanup; consistent build status files in $PREFIX,
LICENSE -> LICENCE., fix libelf's pkg_libelf_install_post(), rotate
status files and tarballs.
|
|
collisions and leaks.
- Implemented consistent build/configure/install variable handling with per-level [0123]
defaults. Fixes lack of uniform CFLAGS (-g3 -O0) usage. The new build variables include:
- {AR,CC,RANLIB}_{BUILD,CONFIGURE,INSTALL},
- {{C,LD,MAKE}FLAGS_{BUILD,CONFIGURE,INSTALL}}{,_EXTRA},
- CONFIGURE_ARGS{,_EXTRA}, ENV_VARS_EXTRA, LIBTOOL_MIDIPIX, and PREFIX_EXTRA.
|
|
- Added --{build-{scripts,steps},help,tarball}. Variables can now
be overriden on the command-line.
- Integrated bzip2, dash, less, ncurses, popt, rsync, tar, util-linux,
which, and xz; as there are no patches in portage/ for util-linux just
yet, this presently requires integrated local patches. Git is included
in build.vars only as it requires OpenSSL.
- Include ntapi.local.patch and psxscl.local.patch in the repository.
|
|
etc.) build scripts; everything now goes into $PREFIX_NATIVE
except for the cross compiler and its dependencies, which go
into $PREFIX_TARGET.
- Replaced specific PREFIX variables w/ generic per-build level CFLAGS.
- Merged 204.psxscl.build into pkg.build.
- Generalised patching procedure into build.subr.
|
|
no values are inherited when and wherever they should not be.
- Remove pointless CFLAGS export in 007.gcc.full.build when doing a
runtime or full build.
|
|
- Changed build directory name format to $[1}-{cross,native}-${TARGET}.
- Fixed binutils.host DESTDIR and libelf installation bug.
|
|
- Removed support for particularly pathnames with whitespace or tab cha-
racters. If you have whitespaces in your pathnames anyway, the script will
methodically destroy every single file on your disk(s).
|
|
|