Related
ok so i'm trying to compile dropbox..
i have installed build essentials, gcc, and c++. when i run ./configure i get
"configure:3169: error: C compiler cannot create executables"
i've searched the web for the last hour and can't find a working solution. the best guess i have is that the motorola modified packages that i locked down with the webtop scripts are causing problems. here's a chunk of the config.log, i don't really know what this means
Code:
## ----------- ##
## Core tests. ##
## ----------- ##
configure:2274: checking for a BSD-compatible install
configure:2342: result: /usr/bin/install -c
configure:2353: checking whether build environment is sane
configure:2403: result: yes
configure:2544: checking for a thread-safe mkdir -p
configure:2583: result: ./install-sh -c -d
configure:2596: checking for gawk
configure:2612: found /usr/bin/gawk
configure:2623: result: gawk
configure:2634: checking whether make sets $(MAKE)
configure:2656: result: yes
configure:2798: checking for gcc
configure:2814: found /usr/bin/gcc
configure:2825: result: gcc
configure:3054: checking for C compiler version
configure:3063: gcc --version >&5
gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3074: $? = 0
configure:3063: gcc -v >&5
Using built-in specs.
Target: arm-linux-gnueabi
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --disable-libssp --disable-sjlj-exceptions --with-arch=armv5t --with-tune=cortex-a8 --enable-checking=release --build=arm-linux-gnueabi --host=arm-linux-gnueabi --target=arm-linux-gnueabi
Thread model: posix
gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
configure:3074: $? = 0
configure:3063: gcc -V >&5
gcc: '-V' option must have argument
configure:3074: $? = 1
configure:3063: gcc -qversion >&5
gcc: unrecognized option '-qversion'
gcc: no input files
configure:3074: $? = 1
configure:3096: checking for C compiler default output file name
configure:3118: gcc conftest.c >&5
/osh/usr/bin/../lib/gcc/arm-linux-gnueabi/4.3.3/cc1: error while loading shared libraries: libmpfr.so.1: cannot open shared object file: No such file or directory
configure:3122: $? = 1
configure:3159: result:
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "nautilus-dropbox"
| #define PACKAGE_TARNAME "nautilus-dropbox"
| #define PACKAGE_VERSION "0.7.1"
| #define PACKAGE_STRING "nautilus-dropbox 0.7.1"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define PACKAGE "nautilus-dropbox"
| #define VERSION "0.7.1"
| /* end confdefs.h. */
| #include <stdio.h>
| int
| main ()
| {
| FILE *f = fopen ("conftest.out", "w");
| return ferror (f) || fclose (f) != 0;
|
| ;
| return 0;
| }
configure:3165: error: in `/data/home/adas/nautilus-dropbox-0.7.1':
configure:3169: error: C compiler cannot create executables
See `config.log' for more details.
bump?
nobody? i tried reinstalling build-essential, gcc, c++, g++ in synaptic and it errors before finishing.. i think its cause it can't update some of the pkgs the scripts locked. i'm going start over not locking the pkgs and see if i can set up a sane build environment. =) other wise.. i mean, wtf? webtop is useless
I would suppose your problem is described in the following line:
Code:
/osh/usr/bin/../lib/gcc/arm-linux-gnueabi/4.3.3/cc1: error while loading shared libraries: libmpfr.so.1: cannot open shared object file: No such file or directory
Searching for that file, or where it should be (/usr/lib) brings up nothing.
If you open Synaptic and search there are a couple of libmpfr packages, try upgrading/installing them. I don't want to because I don't care about compiling this and the last time I went around randomly upgrading packages it broke my webtop and I just got it where I want it.
Don't forget that in Ubuntu/Debian that you need to install the -dev packages for many libraries if you want to compile.
I was able to compile a simple hello-world.c program after installing libmpfr-dev, which then installed/upgraded other packages.
Hello all,
I am newbie on android development. I have beaglebone(TI AM335x Cortex-A8 about 720MHz with NEON) and want build mplayer. I use TI SDK.
I have modified conf1.sh to this:
Code:
export NDKHOME=/PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/linux-x86
. ./confn.sh
./configure --cc=$NDKHOME/arm-eabi-4.4.3/bin/arm-eabi-gcc --ar=$NDKHOME/arm-eabi-4.4.3/bin/arm-eabi-ar --as=$NDKHOME/arm-eabi-4.4.3/bin/arm-eabi-as --ranlib=$NDK_HOME/arm-eabi-4.4.3/bin/arm-eabi-ranlib --host-cc=gcc --target=arm-linux-eabi --disable-dvdnav --disable-dvdread --disable-dvdread-internal --disable-vcd --disable-real --disable-xanim --disable-mencoder --disable-mp3lib --disable-tremor-internal --disable-fbdev --disable-tga --disable-md5sum --disable-yuv4mpeg --disable-pnm --disable-dvb --disable-tv --disable-ftp --disable-select --disable-armv6t2 --enable-mpg123 --disable-gif --disable-jpeg --enable-faad --disable-libmpeg2-internal --disable-mencoder --datadir="/sdcard/mplayer" --confdir="/sdcard/mplayer" --libdir="/sdcard/mplayer" --disable-armvfp --disable-inet6
confn.sh:
Code:
NDK_PALTFORMS=/PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/ndk/android-ndk-r4
export CFLAGS="-O9 -DANDROID -ffast-math -fomit-frame-pointer -nostdlib -lc -lm -L $NDK_PALTFORMS/platforms/android-8/arch-arm/usr/lib/ -I $NDK_PALTFORMS/platforms/android-8/arch-arm/usr/include/ -march=armv7-a -mtune=cortex-a8 -funroll-loops -Isdl -ldl"
And building has failed with the error below:
Code:
Current branch master is up to date.
Checking for gcc version ... 4.4.3
Checking for working compiler ...
Error: Compiler is not functioning correctly. Check your installation and custom CFLAGS -O9 -DANDROID -ffast-math -fomit-frame-pointer -nostdlib -lc -lm -L /PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/ndk/android-ndk-r4/platforms/android-8/arch-arm/usr/lib/ -I /PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/ndk/android-ndk-r4/platforms/android-8/arch-arm/usr/include/ -march=armv7-a -mtune=cortex-a8 -funroll-loops -Isdl -ldl .
Check "config.log" if you do not understand why it failed.
config.log is like below:
Code:
configuration: --cc=/PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/linux-x86/arm-eabi-4.4.3/bin/arm-eabi-gcc --ar=/PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/linux-x86/arm-eabi-4.4.3/bin/arm-eabi-ar --as=/PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/linux-x86/arm-eabi-4.4.3/bin/arm-eabi-as --ranlib=/arm-eabi-4.4.3/bin/arm-eabi-ranlib --host-cc=gcc --target=arm-linux-eabi --disable-dvdnav --disable-dvdread --disable-dvdread-internal --disable-vcd --disable-real --disable-xanim --disable-mencoder --disable-mp3lib --disable-tremor-internal --disable-fbdev --disable-tga --disable-md5sum --disable-yuv4mpeg --disable-pnm --disable-dvb --disable-tv --disable-ftp --disable-select --disable-armv6t2 --enable-mpg123 --disable-gif --disable-jpeg --enable-faad --disable-libmpeg2-internal --disable-mencoder --datadir=/sdcard/mplayer --confdir=/sdcard/mplayer --libdir=/sdcard/mplayer --disable-armvfp --disable-inet6
============ Checking for gcc version ============
Result is: 4.4.3
##########################################
============ Checking for working compiler ============
int main(void) { return 0; }
gcc -O9 -DANDROID -ffast-math -fomit-frame-pointer -nostdlib -lc -lm -L /PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/ndk/android-ndk-r4/platforms/android-8/arch-arm/usr/lib/ -I /PROJELER/AECMP_BBAndroid/TI_Android_GingerBread_2_3_4_AM335x_Sources/prebuilt/ndk/android-ndk-r4/platforms/android-8/arch-arm/usr/include/ -march=armv7-a -mtune=cortex-a8 -funroll-loops -Isdl -ldl /tmp/mplayer-configure-30206-21317/tmp.c -I. -Iffmpeg -o /tmp/mplayer-configure-30206-21317/tmp
/tmp/mplayer-configure-30206-21317/tmp.c:1: error: bad value (armv7-a) for -march= switch
/tmp/mplayer-configure-30206-21317/tmp.c:1: error: bad value (cortex-a8) for -mtune= switch
What could be the problem ? Any help will be appreciated.
In fact I want to play udp video streams. Can you offer any open source player?
Thanks
Mehmet Kurnaz
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hallo, any one know whats wrong with Jelly Bean AOSP netd, here is logcat:
Code:
I/Netd (10975): Netd 1.0 starting
E/BandwidthController(10975): runIptablesCmd(): failed /system/bin/iptables -t raw -N bw_raw_PREROUTING res=256
E/BandwidthController(10975): runIptablesCmd(): failed /system/bin/ip6tables -t raw -N bw_raw_PREROUTING res=256
D/MDnsDS (10975): MDnsSdListener::Hander starting up
D/MDnsDS (10975): MDnsSdListener starting to monitor
D/MDnsDS (10975): Going to poll with pollCount 1
E/Netd (10975): Unable to start MDnsSdListener (Success)
E/SocketListener(10975): Obtaining file descriptor socket 'mdns' failed: Success
E/NetdConnector( 2399): Communications error: java.io.IOException: No such file or directory
E/NetdConnector( 2399): Error in NativeDaemonConnector: java.io.IOException: No such file or directory
I/Netd (11140): Netd 1.0 starting
E/BandwidthController(11140): runIptablesCmd(): failed /system/bin/iptables -t raw -N bw_raw_PREROUTING res=256
E/BandwidthController(11140): runIptablesCmd(): failed /system/bin/ip6tables -t raw -N bw_raw_PREROUTING res=256
D/MDnsDS (11140): MDnsSdListener::Hander starting up
D/MDnsDS (11140): MDnsSdListener starting to monitor
E/Netd (11140): Unable to start MDnsSdListener (Success)
E/SocketListener(11140): Obtaining file descriptor socket 'mdns' failed: Success
Is these related to kernel or something related to android, many thanks for any hint!!!
Look this - same prob?
...add this section at the end of init.rc:
Code:
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
https://groups.google.com/forum/#!msg/android-platform/faAcGG4QOPo/MDMBeGuF8BkJ
akkufix said:
Look this - same prob?
...add this section at the end of init.rc:
Code:
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
https://groups.google.com/forum/#!msg/android-platform/faAcGG4QOPo/MDMBeGuF8BkJ
Click to expand...
Click to collapse
Yes I added already to init.rc before opened our thread! Not working! Seems something about iptables missing in kernel (see error about res=256 !)... res=256cause wrong command to iptables! Without these "res=256" command to iptables is ok, so what mean these "res"?
munjeni said:
Yes I added already to init.rc before opened our thread! Not working! Seems something about iptables missing in kernel (see error about res=256 !)... res=256cause wrong command to iptables! Without these "res=256" command to iptables is ok, so what mean these "res"?
Click to expand...
Click to collapse
Don't know either what "res" means. Maybe reserved, resolution, received... seems to be a buffer, frame or location.
So, but what i noticed is, you have command "-N bw_raw_PREROUTING", while the guy in my link used "-D bw_raw_PREROUTING".
As man-page of iptable says for -N, --new-chain chain "There must be no target of that name already".
And for command -D --delete chain rule-specification and --delete chain rulenum
"Delete one or more rules from the selected chain. There are two versions of this command: the rule can be specified as a number in the chain (starting at 1 for the first rule) or a rule to match."
This makes the difference, cause "res=256" is already "loaded"??
Or i don't understand anything? :silly:
For reference:
http://ipset.netfilter.org/iptables.man.html
Here http://ipset.netfilter.org/iptables.man.html I can not see anything related to "res" have no idea what these part of the command mean! For example:
/system/bin/iptables -t mangle -D bw_mangle_POSTROUTING res=256
munjeni said:
Here http://ipset.netfilter.org/iptables.man.html I can not see anything related to "res" have no idea what these part of the command mean! For example:
/system/bin/iptables -t mangle -D bw_mangle_POSTROUTING res=256
can not see any reference to these res in iptables
Click to expand...
Click to collapse
I'm looking around for this res and only saw that it is sometimes 256 or 756.
No description at all, yet.
I also found some other guys, having same problems with "Netd 1.0 starting", after putting that lines above into init.rc
This one - https://groups.google.com/forum/?fromgroups=#!topic/renesas-emev-osp/XSdLmPgD9Og
sayed
Code:
BTW - Kernel needs a rebuild too.
And another one - https://groups.google.com/forum/?fromgroups=#!topic/android-building/3qDAbPjnHJc
Code:
1. fastboot -w flashall # This was my initial full system flash after changing the kernels.
2. adb reboot-bootloader
3. fastboot flash system
Step 3 seemed to have done it.
Will try with Tuna JB kernel (quota2)...
Edit:
Think I found a problem, maybe? See:
~ # strace -c netd
strace -c netd
iptables: Chain already exists.
iptables: Chain already exists.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
ip6tables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
ip6tables: Bad rule (does a matching rule exist in that chain?).
iptables: Too many links.
iptables: Too many links.
ip6tables: Too many links.
iptables: Too many links.
ip6tables: Too many links.
iptables: Chain already exists.
iptables: Chain already exists.
iptables: Chain already exists.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables v1.4.11.1: Couldn't find target `penalty_box'
Try `iptables -h' or 'iptables --help' for more information.
ip6tables v1.4.11.1: Couldn't find target `penalty_box'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Click to expand...
Click to collapse
Found some posts on google about "res", these res comming after part of command "--penalty_box res=blabla" so I think "res" is part of subcomand penalty_box ? Will research more, curently nothing found for penalty_box in kernel... researching...
Ok. But what are those "chain already exist" and "no chain/target/match by this name" ? Is there something running in circle?
Edit:
This "already exist" normaly indicates you are try to create the chain more than once. (iptables -N chain name)
For the other prob, maybe it helped to look what tables exists with "iptables -L" ?
Sent from my MT27i using xda app-developers app
Got it!!!
http://img850.imageshack.us/img850/5403/device20121209123052.png
http://img231.imageshack.us/img231/3299/device20121209123124.png
http://img803.imageshack.us/img803/4497/device20121209123143.png
http://img838.imageshack.us/img838/2312/device20121209123024.png
http://img545.imageshack.us/img545/4383/device20121209123117.png
munjeni said:
Got it!!! Problem was missing part of netd in init.rc... finally:
JellyBean... booted!!!
http://img850.imageshack.us/img850/5403/device20121209123052.png
http://img231.imageshack.us/img231/3299/device20121209123124.png
http://img803.imageshack.us/img803/4497/device20121209123143.png
http://img838.imageshack.us/img838/2312/device20121209123024.png
http://img545.imageshack.us/img545/4383/device20121209123117.png
Click to expand...
Click to collapse
Great news. Will you share your sources? I would like to try JB on my U.
Source code is bassed on FXP CM9, but I have no working source because there was a lot of fails so I fixed these things by manyally copying libs, headers ...etc, I am not able to colect all changes, its on my computer! Android source I used is AOSP jb-dev branch! If something fail on your build ask me I will help you to get these rom booted! Android build is not useable in any way because have missing audio, missing sdcard ...etc, we can not do more without help by Sony! We need to ask Sony to give us new brebuilts compatible with JellyBean, ot to give us source code for these things, for example libhardware, libsensors, libaudio, at_core, libril, ste_omxcomponents...!
munjeni said:
Source code is bassed on FXP CM9, but I have no working source because there was a lot of fails so I fixed these things by manyally copying libs, headers ...etc, I am not able to colect all changes, its on my computer! Android source I used is AOSP jb-dev branch! If something fail on your build ask me I will help you to get these rom booted! Android build is not useable in any way because have missing audio, missing sdcard ...etc, we can not do more without help by Sony! We need to ask Sony to give us new brebuilts compatible with JellyBean, ot to give us source code for these things, for example libhardware, libsensors, libaudio, at_core, libril, ste_omxcomponents...!
Click to expand...
Click to collapse
Thanks a lot. Yes, I know that a lot of things missing for jb, but i would like to try cm10 in my U. Could be better if sony give us sources, but i think we won't get it. And i think we can't use new prebuilts while we don't get the first official jb rom.
munjeni said:
Got it!!!
http://img850.imageshack.us/img850/5403/device20121209123052.png
http://img231.imageshack.us/img231/3299/device20121209123124.png
http://img803.imageshack.us/img803/4497/device20121209123143.png
http://img838.imageshack.us/img838/2312/device20121209123024.png
http://img545.imageshack.us/img545/4383/device20121209123117.png
Click to expand...
Click to collapse
Hi,
facing the same problem...
Can you please share the solution? Tired of searching for it.
Thanks in advance.
I'm having quite a difficult time getting a final product actually compiled, and have a question about modifying extract_files.sh.
The primary guide (in addition to many hours of setups, searches and additional reading) I've been using is Cyanogenmod's for JFLTEVZW, and the unified builds have officially confused the hell out of me. I know it went from non-unified, to unified, back to non-unified, but my attempts at compiling a build continue to fail or the OS completely freezes--I've recreated my build environment multiple times and am now using someone else's pre-configured, downloadable Cyanogenmod build environment image, which I've imported into VirtualBox...but something inevitably goes wrong, and I guess I'll ask about that if and when it fails/freezes during the "brunch" process again.
Does linux or however this whole git/repo/sync system is configured "remember" in some configuration file somewhere when I've done a breakfast jflte (not jfltevzw) once before, and despite deleting all contents of the android/system folder and starting fresh, if I do it for jfltevzw again, it will still grab files for jflte, or is that normal?
Code:
[email protected]:~/android/system$ source build/envsetup.sh && breakfast jfltevzw
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/samsung/jflte/vendorsetup.sh
including device/samsung/jfltevzw/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
including vendor/cm/vendorsetup.sh
Looking for dependencies
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.0.2
CM_VERSION=12-20150417-UNOFFICIAL-jfltevzw
TARGET_PRODUCT=cm_jfltevzw
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-28-generic-x86_64-with-Ubuntu-14.10-utopic
HOST_BUILD_TYPE=release
BUILD_ID=LRX22G
OUT_DIR=/home/android/android/system/out
============================================
Is it supposed to be doing this, or have I messed up somewhere since I'm not a linux guru and I know the concept of "I deleted the folder" is not the same as in Windows? I'm wondering if something was written to a file somewhere when I FIRST ran breakfast jflte without knowing exactly which one I should be doing, or if this is normal, despite the s4 being unique by having unified CM builds for a while. I may need to have this build/compile process explained to me as if I'm new to computers, apparently.
My goal is to make various compiled builds so that I can attempt to fix the broken compass. The problem may be that the code worked before the unified builds, and so the other part of my question is, how do I modify extract_files.sh so that I can have it pull the files from a cyanogenmod .zip file? I've read this, and looked at the file and don't understand which of the four lines to edit. Also, within android/system/device/samsung there are jf-common, jflte, jfltevzw, qcom-common folders, and both the jflte and jfltevzw (again, I don't know if both should even be there since I'm doing a sync when the builds are no longer unified) have an extract_files.sh which points to the file in jf-common (again, I don't know if I should/can be doing breakfast/brunch jflte or jfltevzw because of the lack of acknowledgement to prior and vestigial unified components remaining in the CM code in the "how to build CM" documentation):
Code:
#!/bin/sh
set -e
export DEVICE=jfltevzw
export VENDOR=samsung
./../jf-common/extract-files.sh [email protected]
Code:
#!/bin/bash
function extract() {
for FILE in `egrep -v '(^#|^$)' $1`; do
OLDIFS=$IFS IFS=":" PARSING_ARRAY=($FILE) IFS=$OLDIFS
FILE=`echo ${PARSING_ARRAY[0]} | sed -e "s/^-//g"`
DEST=${PARSING_ARRAY[1]}
if [ -z $DEST ]; then
DEST=$FILE
fi
DIR=`dirname $FILE`
if [ ! -d $2/$DIR ]; then
mkdir -p $2/$DIR
fi
if [ "$SRC" = "adb" ]; then
# Try CM target first
adb pull /system/$DEST $2/$DEST
# if file does not exist try OEM target
if [ "$?" != "0" ]; then
adb pull /system/$FILE $2/$DEST
fi
else
cp $SRC/system/$FILE $2/$DEST
# if file dot not exist try destination
if [ "$?" != "0" ]
then
cp $SRC/system/$DEST $2/$DEST
fi
fi
done
}
if [ $# -eq 0 ]; then
SRC=adb
else
if [ $# -eq 1 ]; then
SRC=$1
else
echo "$0: bad number of arguments"
echo ""
echo "usage: $0 [PATH_TO_EXPANDED_ROM]"
echo ""
echo "If PATH_TO_EXPANDED_ROM is not specified, blobs will be extracted from"
echo "the device using adb pull."
exit 1
fi
fi
BASE=../../../vendor/$VENDOR/jf-common/proprietary
rm -rf $BASE/*
DEVBASE=../../../vendor/$VENDOR/$DEVICE/proprietary
rm -rf $DEVBASE/*
extract ../../$VENDOR/jf-common/common-proprietary-files.txt $BASE
extract ../../$VENDOR/$DEVICE/device-proprietary-files.txt $DEVBASE
../jf-common/setup-makefiles.sh
So what exactly do I need to change, per these instructions so that I can pull the proprietary files from, say, cm-11-20140210-SNAPSHOT-M3-jfltevzw.zip (pre-unified) or cm-11-20140504-SNAPSHOT-M6-jflte.zip (post-unified) instead of from my phone? I saw the PATH_TO_EXPANDED_ROM part, but I don't know where that's referenced, so I don't know how to make use of that instead.
I'll be grateful for any help, because I'd really like to take a shot at reviving the compass since it used to work correctly. Thanks =)
Unless someone can guarantee to me that if I were to recompile the very first CM10 build for the S4, I could just do a normal pull of the proprietary files from my CM12 nightly phone and end up with a compiled zip identical to the first CM10 and would have zero changes compared to the original CM10, then I won't bother with trying to pull the proprietary files from an older CM zip instead of my current nightly, which I presume are related to hardware functionality--something I want to fix.
Jon8RFC said:
I'm having quite a difficult time getting a final product actually compiled, and have a question about modifying extract_files.sh.
The primary guide (in addition to many hours of setups, searches and additional reading) I've been using is Cyanogenmod's for JFLTEVZW, and the unified builds have officially confused the hell out of me. I know it went from non-unified, to unified, back to non-unified, but my attempts at compiling a build continue to fail or the OS completely freezes--I've recreated my build environment multiple times and am now using someone else's pre-configured, downloadable Cyanogenmod build environment image, which I've imported into VirtualBox...but something inevitably goes wrong, and I guess I'll ask about that if and when it fails/freezes during the "brunch" process again.
Does linux or however this whole git/repo/sync system is configured "remember" in some configuration file somewhere when I've done a breakfast jflte (not jfltevzw) once before, and despite deleting all contents of the android/system folder and starting fresh, if I do it for jfltevzw again, it will still grab files for jflte, or is that normal?
Code:
[email protected]:~/android/system$ source build/envsetup.sh && breakfast jfltevzw
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/samsung/jflte/vendorsetup.sh
including device/samsung/jfltevzw/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
including vendor/cm/vendorsetup.sh
Looking for dependencies
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.0.2
CM_VERSION=12-20150417-UNOFFICIAL-jfltevzw
TARGET_PRODUCT=cm_jfltevzw
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-28-generic-x86_64-with-Ubuntu-14.10-utopic
HOST_BUILD_TYPE=release
BUILD_ID=LRX22G
OUT_DIR=/home/android/android/system/out
============================================
Is it supposed to be doing this, or have I messed up somewhere since I'm not a linux guru and I know the concept of "I deleted the folder" is not the same as in Windows? I'm wondering if something was written to a file somewhere when I FIRST ran breakfast jflte without knowing exactly which one I should be doing, or if this is normal, despite the s4 being unique by having unified CM builds for a while. I may need to have this build/compile process explained to me as if I'm new to computers, apparently.
My goal is to make various compiled builds so that I can attempt to fix the broken compass. The problem may be that the code worked before the unified builds, and so the other part of my question is, how do I modify extract_files.sh so that I can have it pull the files from a cyanogenmod .zip file? I've read this, and looked at the file and don't understand which of the four lines to edit. Also, within android/system/device/samsung there are jf-common, jflte, jfltevzw, qcom-common folders, and both the jflte and jfltevzw (again, I don't know if both should even be there since I'm doing a sync when the builds are no longer unified) have an extract_files.sh which points to the file in jf-common (again, I don't know if I should/can be doing breakfast/brunch jflte or jfltevzw because of the lack of acknowledgement to prior and vestigial unified components remaining in the CM code in the "how to build CM" documentation):
Code:
#!/bin/sh
set -e
export DEVICE=jfltevzw
export VENDOR=samsung
./../jf-common/extract-files.sh [email protected]
Code:
#!/bin/bash
function extract() {
for FILE in `egrep -v '(^#|^$)' $1`; do
OLDIFS=$IFS IFS=":" PARSING_ARRAY=($FILE) IFS=$OLDIFS
FILE=`echo ${PARSING_ARRAY[0]} | sed -e "s/^-//g"`
DEST=${PARSING_ARRAY[1]}
if [ -z $DEST ]; then
DEST=$FILE
fi
DIR=`dirname $FILE`
if [ ! -d $2/$DIR ]; then
mkdir -p $2/$DIR
fi
if [ "$SRC" = "adb" ]; then
# Try CM target first
adb pull /system/$DEST $2/$DEST
# if file does not exist try OEM target
if [ "$?" != "0" ]; then
adb pull /system/$FILE $2/$DEST
fi
else
cp $SRC/system/$FILE $2/$DEST
# if file dot not exist try destination
if [ "$?" != "0" ]
then
cp $SRC/system/$DEST $2/$DEST
fi
fi
done
}
if [ $# -eq 0 ]; then
SRC=adb
else
if [ $# -eq 1 ]; then
SRC=$1
else
echo "$0: bad number of arguments"
echo ""
echo "usage: $0 [PATH_TO_EXPANDED_ROM]"
echo ""
echo "If PATH_TO_EXPANDED_ROM is not specified, blobs will be extracted from"
echo "the device using adb pull."
exit 1
fi
fi
BASE=../../../vendor/$VENDOR/jf-common/proprietary
rm -rf $BASE/*
DEVBASE=../../../vendor/$VENDOR/$DEVICE/proprietary
rm -rf $DEVBASE/*
extract ../../$VENDOR/jf-common/common-proprietary-files.txt $BASE
extract ../../$VENDOR/$DEVICE/device-proprietary-files.txt $DEVBASE
../jf-common/setup-makefiles.sh
So what exactly do I need to change, per these instructions so that I can pull the proprietary files from, say, cm-11-20140210-SNAPSHOT-M3-jfltevzw.zip (pre-unified) or cm-11-20140504-SNAPSHOT-M6-jflte.zip (post-unified) instead of from my phone? I saw the PATH_TO_EXPANDED_ROM part, but I don't know where that's referenced, so I don't know how to make use of that instead.
I'll be grateful for any help, because I'd really like to take a shot at reviving the compass since it used to work correctly. Thanks =)
Unless someone can guarantee to me that if I were to recompile the very first CM10 build for the S4, I could just do a normal pull of the proprietary files from my CM12 nightly phone and end up with a compiled zip identical to the first CM10 and would have zero changes compared to the original CM10, then I won't bother with trying to pull the proprietary files from an older CM zip instead of my current nightly, which I presume are related to hardware functionality--something I want to fix.
Click to expand...
Click to collapse
Once you breakfast/lunch jfltevzw instead of jflte, that will override the last breakfast/lunch option you chose. So essentially whatever the last thing you selected for the breakfast/lunch is what it will use. You can just edit the script to pull the files from a zip after extracting it, I assume if your building from source you know how bash scripts work.
Cm documentation is horrible and their build system typically is more complicated (seemingly for no reason) than that of aosp. Use jfltevzw and if it doesn't work use jflte, unless you know how to build a device tree for jfltevzw yourself in which case you could do that.
Thanks, Surge! Hope the bootloader unlock progress is still coming along!
I think my remaining problem with the freezing was the fact that I was running it as a VM. I did a real Ubuntu installation (and combined a few how-to guides to actually get things working) and instead of me watching the paint dry for over ten hours, and then it freezing, the build compiled in 1 hour 53 minutes (I guess that puts my poor, overclocked Q9550 into perspective ), and booted up on my phone after a full wipe. I don't know what all I installed that may not have been necessary, so setting up this new environment may have been overkill, but maybe it's worth it for me to make a more updated how-to.
For what it's worth, I still saw warnings during the build and at the beginning of brunch, it still did the src not found string of errors, but CM12 built just fine. I initially thought something was wrong with the build functionality because I saw "make -j4 bacon" in the task manager, so I tried manually building with make jfltevzw, thinking that something was wrong and it was building for the One Plus One...that was very misleading and confusing. That was on the VM, and I wasted HOURS doing two additional pointless builds because I thought the brunch process was FUBAR. Nope, if you see "make -jX bacon", apparently that's a misnomer and it's NOT building CM for the One Plus One.
Also, the repo sync actually maxed out my internet connection and I didn't have to wait a couple of hours for it to sync, when I used the following (8 and 16 didn't cut it):
Code:
repo sync -j32 -c
The -c may have been redundant, according to CM's documentation, but I did it anyway just to play it safe. Also, I didn't officially read it anywhere, but the -j (jobs) switch is frequently referred to as something which should be equal to or less than your processor's core/thread capability. That doesn't apply to the repo sync at all...I had to raise a lot it to actually make use my bandwidth.
The bandwidth usage for the sync was usually pegged at 215mbit downstream and ranged between 4 and 12mbit upstream (my cap is 22) so substantial upstream bandwidth is necessary to keep up with downstream, it seems.
I'm rambling so that if others wander over here, they'll see my experiences. I guess I should make more of a "CM compiling for idiots who are sys admins with Windows, but apparently suck with linux" guide. Step 1 is VirtualBox freezes at some point over 10 hours of compiling, even with 250gigs of space on a dedicated drive, 4gigs of ram, and 4 cpus at 100% allocation...just dual boot instead.
Sony just posted a guide in their site to build AOSP 9.0 for our devices.
https://developer.sony.com/develop/...build-instructions/build-aosp-android-p-9-0-0
I try to build this next week stay tuned
VinBenzin810 said:
I try to build this next week stay tuned
Click to expand...
Click to collapse
That's great! Thanks a lot!
Sent from my [device_name] using XDA-Developers Legacy app
VinBenzin810 said:
I try to build this next week stay tuned
Click to expand...
Click to collapse
TriboDoP said:
That's great! Thanks a lot!
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm actually trying to build it myself now. It's the first time I'm doing it, but their guide is clear and easy to follow. I just need someone to test it when I'm done, my own device isn't unlocked yet and I kinda don't want to unless the bugs are minor.
I'm at step 4 downloading/syncing it right now. I'll let you know when I'm done & upload it in the OP.
Edit: I'll leave it to someone who knows it better. I got stuck at building it (step 5.3), getting an error at the first 10 seconds.
Redcalibur said:
I'm actually trying to build it myself now. It's the first time I'm doing it, but their guide is clear and easy to follow. I just need someone to test it when I'm done, my own device isn't unlocked yet and I kinda don't want to unless the bugs are minor.
I'm at step 4 downloading/syncing it right now. I'll let you know when I'm done & upload it in the OP.
Edit: I'll leave it to someone who knows it better. I got stuck at building it (step 5.3), getting an error at the first 10 seconds.
Click to expand...
Click to collapse
Thanks for trying anyway! Being new to sony i also don't want to breake the camera (altough thankfully there is a custom kernel + twrp + camera-fix) so i am uncertain if i should wait for official android 9 or AOSP android 9 (customroms would be even better).
On my other devices (samsung,oneplus) i use only customroms but at the moment there is very little choice here.
But i love the xz1 with the 835 it is fast as lightning!
Regards!
Sent from my [device_name] using XDA-Developers Legacy app
Redcalibur said:
I'm actually trying to build it myself now. It's the first time I'm doing it, but their guide is clear and easy to follow. I just need someone to test it when I'm done, my own device isn't unlocked yet and I kinda don't want to unless the bugs are minor.
I'm at step 4 downloading/syncing it right now. I'll let you know when I'm done & upload it in the OP.
Edit: I'll leave it to someone who knows it better. I got stuck at building it (step 5.3), getting an error at the first 10 seconds.
Click to expand...
Click to collapse
Which Error you get ? Write me an pn
VinBenzin810 said:
Which Error you get ? Write me an pn
Click to expand...
Click to collapse
Hi, I sent the PM but couldn't find it in between my "sent messages" folder. I'll just send it here too for future references aswell.
So I tried to reproduce the error after running a ./repo_update.sh, but got another error. This time, it progressed a little further. Here are some screens of my terminal.
https://imgur.com/a/4AdBMrp
Redcalibur said:
Hi, I sent the PM but couldn't find it in between my "sent messages" folder. I'll just send it here too for future references aswell.
So I tried to reproduce the error after running a ./repo_update.sh, but got another error. This time, it progressed a little further. Here are some screens of my terminal.
https://imgur.com/a/4AdBMrp
Click to expand...
Click to collapse
I send you an PM look there
Redcalibur said:
Hi, I sent the PM but couldn't find it in between my "sent messages" folder. I'll just send it here too for future references aswell.
So I tried to reproduce the error after running a ./repo_update.sh, but got another error. This time, it progressed a little further. Here are some screens of my terminal.
https://imgur.com/a/4AdBMrp
Click to expand...
Click to collapse
Except
- repo_update.sh hardware/qcom/gps
- vendor-qcom-opensource-location
Poplar xperiadev pie is "today build-able" but doesn't boot yet; good news are xperiadev moves to kernel 4.9; will probably have to wait for SoftwareBinairies v16 Pie specifics...
Will upload poplar_Pie as soon as it will boot...
btw: I've uploaded latest twrp 3.2.3 with OEM.img flash support (and BusyBox) https://androidfilehost.com/?fid=1322778262903981152
Any news about the build?
Getting below error .. doesn't seem like kernel is syncing. Any ideas?
[ 66% 2/3] glob frameworks/base/core/java/**/*.java
ninja: error: 'kernel/sony/msm-4.9/common-kernel/kernel-dtb-poplar', needed by 'out/target/product/poplar/kernel', missing and no known rule to make it
16:01:44 ninja failed with: exit status 1
#### failed to build some targets (07:25 (mm:ss)) ####
rsabluebulls said:
Getting below error .. doesn't seem like kernel is syncing. Any ideas?
[ 66% 2/3] glob frameworks/base/core/java/**/*.java
ninja: error: 'kernel/sony/msm-4.9/common-kernel/kernel-dtb-poplar', needed by 'out/target/product/poplar/kernel', missing and no known rule to make it
16:01:44 ninja failed with: exit status 1
#### failed to build some targets (07:25 (mm:ss)) ####
Click to expand...
Click to collapse
Just delete kernel/sony/msm-4.9/common-kernel directory and your build will go through a complete rebuild of dbt and kernel.
But without Sony Pie OEm vendor image release, the phone will hang on logo...
Thank you oF2pks - I managed to get further with the compile. This is the next error... any help please?
Copying resources from program jar [/Volumes/Mac_Drive/android-pe/out/target/common/obj/APPS/messaging_intermediates/classes.jar]
[ 60% 52636/87279] build out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt
uniq: illegal option -- D
usage: uniq [-c | -d | -u] [-i] [-f fields] [-s chars] [input [output]]
[ 60% 52851/87279] build out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt
uniq: illegal option -- D
usage: uniq [-c | -d | -u] [-i] [-f fields] [-s chars] [input [output]]
[ 60% 52893/87279] build out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt
uniq: illegal option -- D
usage: uniq [-c | -d | -u] [-i] [-f fields] [-s chars] [input [output]]
[ 60% 52978/87279] Yacc: ss <= external/iproute2/misc/ssfilter.y
external/iproute2/misc/ssfilter.y: conflicts: 35 shift/reduce
[ 61% 53613/87279] target C: libext4 <= out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.c
FAILED: out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.o
/bin/bash -c "prebuilts/misc/darwin-x86/ccache/ccache prebuilts/clang/host/darwin-x86/clang-4691093/bin/clang -I external/iptables/extensions/../include/ -I external/iptables/extensions/.. -I out/target/product/poplar/gen/STATIC_LIBRARIES/libext4_intermediates -I external/iptables/extensions -I external/iptables/extensions -I out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates -I out/target/product/poplar/gen/STATIC_LIBRARIES/libext4_intermediates -I libnativehelper/include_jni \$(cat out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/import_includes) -I system/core/include -I system/media/audio/include -I hardware/libhardware/include -I hardware/libhardware_legacy/include -I hardware/ril/include -I libnativehelper/include -I frameworks/native/include -I frameworks/native/opengl/include -I frameworks/av/include -isystem out/target/product/poplar/obj/include -isystem kernel/sony/msm-4.9/common-headers/kernel-headers -isystem bionic/libc/include -isystem bionic/libc/kernel/uapi -isystem bionic/libc/kernel/uapi/asm-arm64 -isystem bionic/libc/kernel/android/scsi -isystem bionic/libc/kernel/android/uapi -c -Werror=implicit-function-declaration -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG -UDEBUG -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument -fcolor-diagnostics -Wno-expansion-to-defined -Wno-zero-as-null-pointer-constant -fdebug-prefix-map=\$PWD/= -ffunction-sections -fdata-sections -fno-short-enums -funwind-tables -fstack-protector-strong -Wa,--noexecstack -D_FORTIFY_SOURCE=2 -Wstrict-aliasing=2 -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Werror=date-time -Werror=format-security -nostdlibinc -march=armv8-a -mcpu=cortex-a53 -target aarch64-linux-android -Bprebuilts/gcc/darwin-x86/aarch64/aarch64-linux-android-4.9/aarch64-linux-android/bin -std=gnu99 -DNO_SHARED_LIBS=1 -DXTABLES_INTERNAL -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DENABLE_IPV4 -DENABLE_IPV6 -D__ANDROID__ -Wall -Werror -Wno-format -Wno-missing-field-initializers -Wno-pointer-arith -Wno-pointer-bool-conversion -Wno-sign-compare -Wno-tautological-pointer-compare -Wno-unused-parameter -fPIC -D_USING_LIBCXX -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -Werror=address-of-temporary -Werror=return-type -Wno-tautological-constant-compare -Wno-null-pointer-arithmetic -Wno-enum-compare -Wno-enum-compare-switch -MD -MF out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.d -o out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.o out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.c"
In file included from out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.c:11:
external/iptables/extensions/../include/linux/netfilter_ipv4/ipt_ECN.h:13:10: fatal error: 'linux/netfilter/xt_DSCP.h' file not found
#include <linux/netfilter/xt_DSCP.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[ 61% 53616/87279] target StaticLib: libv8 (out/target/product/poplar/obj/STATIC_LIBRARIES/libv8_intermediates/libv8.a)
ninja: build stopped: subcommand failed.
18:47:24 ninja failed with: exit status 1
#### failed to build some targets (05:24:19 (hh:mm:ss)) ####
rsabluebulls said:
external/iptables/extensions/../include/linux/netfilter_ipv4/ipt_ECN.h:13:10: fatal error: 'linux/netfilter/xt_DSCP.h' file not found
#include <linux/netfilter/xt_DSCP.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[ 61% 53616/87279] target StaticLib: libv8 (out/target/product/poplar/obj/STATIC_LIBRARIES/libv8_intermediates/libv8.a)
ninja: build stopped: subcommand failed.
18:47:24 ninja failed with: exit status 1
#### failed to build some targets (05:24:19 (hh:mm:ss)) ####
Click to expand...
Click to collapse
Noob here. Does this (https://medium.com/@christopherney/building-android-o-with-a-mac-da07e8bd94f9) help?
christopherney said:
If the following error is raised during the Android building process:
external/iptables/extensions/../include/linux/netfilter_ipv4/ipt_ECN.h:13:10: fatal error: 'linux/netfilter/xt_DSCP.h' file not found
#include <linux/netfilter/xt_DSCP.h>
Please check the filename user or lower case. Remember that the Android building process is case-sensitive.
Click to expand...
Click to collapse
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
Anyone able to assist with the missing separator error in Android.mk which I'm receiving now?
many thanks
--------------------------
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=aosp_g8341
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a73
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=cortex-a73
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=darwin
HOST_OS_EXTRA=Darwin-17.7.0-x86_64-10.13.6
HOST_BUILD_TYPE=release
BUILD_ID=PPR1.180610.009
OUT_DIR=out
============================================
ninja: no work to do.
ninja: no work to do.
wildcard(out/target/product/poplar/clean_steps.mk) was changed, regenerating...
out/build-aosp_g8341.ninja is missing, regenerating...
[2/947] including art/Android.mk ...
art/build/Android.common.mk:50: warning: unsupported HOST_ARCH=x86_64
[119/947] including device/sony/common/Android.mk ...
hardware/qcom/gps/sdm845/android/Android.mk:48: error: missing separator.
19:53:11 ckati failed with: exit status 1
#### failed to build some targets (57 seconds) ####
arslancn said:
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
Click to expand...
Click to collapse
I tested some ROMs, but I will restart them in Sony LOGO. I don't know if anyone is successful. Maybe I still need to flash something.
Anyone come across a StaticLib: libv8src_32 related compiling issue like mine shown in the log below?
Many thanks - got up to 64% clean build...
make[3]: *** Waiting for unfinished jobs....
INSTALL usr/include/scsi/ufs/ (2 files)
INSTALL usr/include/linux/caif/ (2 files)
INSTALL usr/include/linux/byteorder/ (2 files)
INSTALL usr/include/linux/can/ (5 files)
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
make[4]: *** [usr/include/linux/byteorder/.install] Error 1
make[4]: *** [usr/include/linux/caif/.install] Error 1
make[4]: *** [usr/include/linux/can/.install] Error 1
make[4]: *** [usr/include/scsi/ufs/.install] Error 1
make[3]: *** [can] Error 2
make[3]: *** [caif] Error 2
make[3]: *** [byteorder] Error 2
make[3]: *** [ufs] Error 2
make[2]: *** [linux] Error 2
make[2]: *** [scsi] Error 2
make[1]: *** [headers_install] Error 2
make: *** [sub-make] Error 2
[ 64% 56247/87336] target StaticLib: libv8src_32 (out/target/product/poplar/obj_arm/STATIC_LIBRARIES/libv8src_intermediates/libv8src.a)
ninja: build stopped: subcommand failed.
15:16:21 ninja failed with: exit status 1
#### failed to build some targets (49:07 (mm:ss)) ####
Hi all, anyone perhaps have an idea on the below error or perhaps came across it before? (PS. 8.1 ASOP Sony builds without any issues, latest SEP release), this is for Android Pie latest asop
[ 63% 55359/87336] Building Kernel Headers
FAILED: /Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.headers_install_stamp
/bin/bash -c "(if [ ! -z "aosp_yoshino_poplar_defconfig" ]; then rm -f ..//Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.config; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" aosp_yoshino_poplar_defconfig; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" headers_install; fi ) && (if [ "aosp_yoshino_poplar_defconfig" != "aosp_yoshino_poplar_defconfig" ]; then echo "Used a different defconfig for header generation"; rm -f ..//Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.config; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" aosp_yoshino_poplar_defconfig; fi ) && (if [ ! -z "" ]; then echo "Overriding kernel config with ''"; echo >> /Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.config; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" oldconfig; fi )"
GEN ./Makefile
#
# configuration written to .config
#
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/ this link maybe useful for you guys