We are working on to release a new git tree and hope to include everything
together so that people's life can be much easier. At the meanwhile you have
2 choices:
a. apply all the patches from patch hosting project to the gitorious tree
you checked out (there could be conflicts so other issues).
On Jul 1, 4:53 pm, subram subram...@gmail.com wrote:
Hi there
I have an doubt regarding creating new androidmanifest.xml
file,since i need to create an android project from an existing path
that is my .so,when i give like this it shows androidmnifest.xml not
found,kindly suggest how to
Just a quick question, I have an Asus 1000HE with a 160GB HDD, when I
install Android it takes several hours, especially the resizing the
file system step, is there any way to specify (perhaps in
disk_layout.conf?) that I only wanted to use say, the first 16GB, of
the target device?
I am porting a C program. Very simple - it refers to a C function
declared in BIONIC libc:
device/bionic/libc/include/unistd.h
at line 142 (CUPCAKE version) as
extern int fdatasync(int);
Link failure is seen because libc.so doesn't have the implementation:
external/sysstat/sadc.c:901: undefined
Yes, it is. The linker ld fails to find the symbol fdatasync. How to
get it found? And trick in Android.mk?
Kenny
On Jul 2, 8:16 pm, Michael Trimarchi trimar...@gandalf.sssup.it
wrote:
Kenny Yu wrote:
I am porting a C program. Very simple - it refers to a C function
declared in BIONIC libc:
Hi,
Kenny wrote:
Yes, it is. The linker ld fails to find the symbol fdatasync. How to
get it found? And trick in Android.mk?
Kenny
Add to the bionic SYSCALL.txt and call the python script gensyscall.py.
I hope
that it fix your issue
Michael
On Jul 2, 8:16 pm, Michael Trimarchi
