[PATCH] examples: allow to reuse environment variables in android-build
+ rename them to not clash with non intended environment variables
Signed-off-by: Petr Vorel
---
examples/android-build | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/examples/android-build b/examples/android-build
index 123ba96..a420c2c 100755
--- a/examples/android-build
+++ b/examples/android-build
@@ -8,24 +8,24 @@
# the android libc must be patched around) and Gingerbread.
# Point this to the Android root directory; it's used in the defconfig CFLAGS
-export A="$HOME/android"
+export ANDROID="${ANDROID:-$HOME/android}"
# Android product being built
-P=zoom2
+TARGET_PRODUCT=${TARGET_PRODUCT:-zoom2}
# Toolchain version in use by this version of Android
GCCVER=4.4.3
-export PATH="$A/prebuilt/linux-x86/toolchain/arm-eabi-$GCCVER/bin:$PATH"
+export PATH="$ANDROID/prebuilt/linux-x86/toolchain/arm-eabi-$GCCVER/bin:$PATH"
# Set the linker flags; compiler flags are in the defconfig file
if grep "^CONFIG_STATIC=y" .config >/dev/null ; then
# Static linking
- LDFLAGS="-static -Xlinker -z -Xlinker muldefs -nostdlib
$A/out/target/product/$P/obj/lib/crtbegin_static.o
$A/out/target/product/$P/obj/lib/crtend_android.o
-L$A/out/target/product/$P/obj/lib
-L$A/out/target/product/$P/obj/STATIC_LIBRARIES/libm_intermediates
-L$A/out/target/product/$P/obj/STATIC_LIBRARIES/libc_intermediates"
+ LDFLAGS="-static -Xlinker -z -Xlinker muldefs -nostdlib
$ANDROID/out/target/product/$TARGET_PRODUCT/obj/lib/crtbegin_static.o
$ANDROID/out/target/product/$TARGET_PRODUCT/obj/lib/crtend_android.o
-L$ANDROID/out/target/product/$TARGET_PRODUCT/obj/lib
-L$ANDROID/out/target/product/$TARGET_PRODUCT/obj/STATIC_LIBRARIES/libm_intermediates
-L$ANDROID/out/target/product/$TARGET_PRODUCT/obj/STATIC_LIBRARIES/libc_intermediates"
LDLIBS="m c gcc"
else
# Dynamic linking
- LDFLAGS="-Xlinker -z -Xlinker muldefs -nostdlib -Bdynamic -Xlinker
-T$A/build/core/armelf.x -Xlinker -dynamic-linker -Xlinker /system/bin/linker
-Xlinker -z -Xlinker nocopyreloc -Xlinker --no-undefined
$A/out/target/product/$P/obj/lib/crtbegin_dynamic.o
$A/out/target/product/$P/obj/lib/crtend_android.o
-L$A/out/target/product/$P/obj/lib"
+ LDFLAGS="-Xlinker -z -Xlinker muldefs -nostdlib -Bdynamic -Xlinker
-T$ANDROID/build/core/armelf.x -Xlinker -dynamic-linker -Xlinker
/system/bin/linker -Xlinker -z -Xlinker nocopyreloc -Xlinker --no-undefined
$ANDROID/out/target/product/$TARGET_PRODUCT/obj/lib/crtbegin_dynamic.o
$ANDROID/out/target/product/$TARGET_PRODUCT/obj/lib/crtend_android.o
-L$ANDROID/out/target/product/$TARGET_PRODUCT/obj/lib"
LDLIBS="dl m c gcc"
fi
--
2.9.3
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
Re: BusyBox for OSX
Op 31-08-16 om 11:59 schreef casey:
> REM’d out that build option in /configs/osx_defconfig:
[...]
> #CONFIG_EXTRA_CFLAGS=‘-arch x86_64 -mmacosx-version-min=10.5'
Your problem here were the curly (non-ASCII) single quotes (‘’). Shells
don't understand these. Use the straight ASCII ones ('') instead.
- M.
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
Re: Altscreens for less and more
What is altscreen? On Sun, Sep 4, 2016 at 2:49 PM, Cág wrote: > Hi, > > I've already written to the Alpine list, but, assuming these are > specifically BusyBox utilities, here is it. > > On my Alpine after booting login(1) starts on the same screen, > meaning I can see all boot messages. less(1) and more(1) leave the > screen filled with output. Is there a way to recompile them all > somehow to have altscreens? Or maybe there are patches? > > Thank ye, > Cág > ___ > busybox mailing list > busybox@busybox.net > http://lists.busybox.net/mailman/listinfo/busybox ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
Altscreens for less and more
Hi, I've already written to the Alpine list, but, assuming these are specifically BusyBox utilities, here is it. On my Alpine after booting login(1) starts on the same screen, meaning I can see all boot messages. less(1) and more(1) leave the screen filled with output. Is there a way to recompile them all somehow to have altscreens? Or maybe there are patches? Thank ye, Cág ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
Re: [PATCH] libbb: More informative "short write" error
On 04/09/2016 12:11, Lauri Kasanen wrote: Over at TinyCore, we receive a huge number of questions of the type "I got "short write", what does it mean?". Mostly for the rpi port and when using bb wget. The attached patch makes the message more informative, and hopefully lets more people know what's up without having to ask. I think a better fix would be to have a version of bb_verror_msg() (which is called by bb_error_msg_and_die) that adds strerror(errno) to the printed message. This way, the information given would always match the actual error that happens. Of course, it's more invasive. But bb_verror_msg() deserves to be rewritten anyway: it performs a lot of operations that can fail, including allocating heap memory - you don't want that on an abnormal exit path. -- Laurent ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
[PATCH] libbb: More informative "short write" error
Hi,
Over at TinyCore, we receive a huge number of questions of the type "I
got "short write", what does it mean?". Mostly for the rpi port and when
using bb wget. The attached patch makes the message more informative,
and hopefully lets more people know what's up without having to ask.
- Lauri
--
http://www.fastmail.com - A no graphics, no pop-ups email service
From 5c9f3c91db1e8f5b7adb7fb8211ece92a5ecc756 Mon Sep 17 00:00:00 2001
From: Lauri Kasanen
Date: Sun, 4 Sep 2016 13:08:59 +0300
Subject: [PATCH] libbb: More informative "short write" error
Signed-off-by: Lauri Kasanen
---
libbb/xfuncs_printf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libbb/xfuncs_printf.c b/libbb/xfuncs_printf.c
index e9222f6..101836e 100644
--- a/libbb/xfuncs_printf.c
+++ b/libbb/xfuncs_printf.c
@@ -236,7 +236,7 @@ void FAST_FUNC xwrite(int fd, const void *buf, size_t count)
if (count) {
ssize_t size = full_write(fd, buf, count);
if ((size_t)size != count)
- bb_error_msg_and_die("short write");
+ bb_error_msg_and_die("short write, out of disk space?");
}
}
void FAST_FUNC xwrite_str(int fd, const char *str)
--
2.6.2
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
