On 23/01/12 08:14 PM, Jack Bates wrote:
On 20/01/12 05:59 AM, Jack Bates wrote:
On 20/01/12 04:29 AM, Jo-Philipp Wich wrote:
The configure code is uninteresting, the config.log contains runtime
info.
Thanks, here it is: http://nottheoilrig.com/openwrt/201201200/config.log
I think I understand the problem: $SED is
"/home/ubuntu/8.09/staging_dir/host/bin/sed -i -e", so:
echo first | $SED -e 's/\(fir\|lo\)/la/'
- expands to:
ubuntu@domU-12-31-39-00-C5-81:~$ echo first |
/home/ubuntu/8.09/staging_dir/host/bin/sed -i -e -e 's/\(fir\|lo\)/la/'
/home/ubuntu/8.09/staging_dir/host/bin/sed: -e expression #1, char 1:
unknown command: `-'
ubuntu@domU-12-31-39-00-C5-81:~$ echo $?
1
ubuntu@domU-12-31-39-00-C5-81:~$
- which (not surprisingly) does fail
Now to figure out why $SED is
"/home/ubuntu/8.09/staging_dir/host/bin/sed -i -e"...
Hmm... So I *think* the problem is that 8.09/rules.mk line 105:
> 105: SED:=$(STAGING_DIR_HOST)/bin/sed -i -e
- and maybe 8.09/build_dir/host/quilt-0.47/configure lines 5094-5096:
> 5094: case $SED in
> 5095: [\\/]* | ?:[\\/]*)
> 5096: ac_cv_path_SED="$SED" # Let the user override the test with a path.
Consequently $SED is "/home/ubuntu/8.09/staging_dir/host/bin/sed -i -e"
and 8.09/build_dir/host/quilt-0.47/configure line 5145:
> 5145: if test "`echo first | $SED -e 's/\(fir\|lo\)/la/'
2>/dev/null`" = "last"; then
- expands to:
> ubuntu@domU-12-31-39-00-C5-81:~$ echo first |
/home/ubuntu/8.09/staging_dir/host/bin/sed -i -e -e 's/\(fir\|lo\)/la/'
> /home/ubuntu/8.09/staging_dir/host/bin/sed: -e expression #1, char 1:
unknown command: `-'
> ubuntu@domU-12-31-39-00-C5-81:~$ echo $?
> 1
> ubuntu@domU-12-31-39-00-C5-81:~$
- which fails :-P
What I don't understand is how most people are able to build OpenWrt?
Why does this not normally fail?
Thanks!
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-users
