Hi All,
I was using AA for a while now and recently upgraded to CC release.
And i found the build succeeds in some machines and in some machines, it
doesnt.
After digging a little bit it turns out that on the machines where the
build fails,I saw that none of my kernel patches were applied for the linux
kernel directory and when i digged out the root cause, i found that
./staging_dir/host/bin/quilt script can not be executed.

The reason was this for build failure:
My build directory length was very long ( more than 128 characters ). And
as a result, the shell interpreter in ./staging_dir/host/bin/quilt looks
like this ( i have created as an example ):
#!
/disk/fs1/tmp2/kalyan/1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890/ugw/openwrt/core/staging_dir/host/bin/bash
......

And if i try to execute :
[balabhad@blrrsa0011(wlnswg) core]$ ./staging_dir/host/bin/quilt
-bash: ./staging_dir/host/bin/quilt:
/disk/fs1/tmp2/kalyan/1234567890123456789012345678901234567890123456789012345:
bad interpreter: No such file or directory

I crosschecked again AA release, there the shell interpreter just starts
with /bin/bash while in CC release, entire build path is put for shell
interpreter. Why ? Because CC release creates a soft link for bash under
./staging_dir/host/bin:
[balabhad@blrrsa0011(wlnswg) core]$ ls -l ./staging_dir/host/bin/bash
lrwxrwxrwx 1 balabhad wlnswg 9 Sep 28 20:58 ./staging_dir/host/bin/bash ->
/bin/bash

Therefore quilt tool while compilation picks up this bash path and dumps in
its script as shell interpreter.

While i can reduce my build directories lenghts to solve current situation,
any points on how to solve problem in a generic way is appreciated !!

Regards
Kalyan
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to