Thanks for the clarification Brian. The big app you mention is the 'dalvikvm' binary? Could you point us how we could get, for instance, the android home app running with this dalvikvm binary? Is it even possible to do this... I mean we were able to run a simple hello world java app, but I could not get any of the Android jars (e.g. out/target/common/obj/APPS/Home_intermediaries/classes.jar) running.
Cheers, Filipe
Could you help us understand what is required to get, for instance, the home app running on
Brian Swetland wrote: > [Filipe Abrantes <filipe.abran...@gmail.com>]
>> Ok, but that will compile for the target 'SIMULATOR' right? My idea >> was compile everything for an x86 device. I don't fully understand the >> differences between the simulator target and the other ones... for >> instance I understand that on the simulator target dalvik is compiled >> against the 'standard' glibc but what else is different?
> The SIMULATOR target tries to build the entire system more like an > application. Things don't really run in multiple processes. A lot of > things don't work the way they would on a real devices. It still exists > as a debugging aid (you can run it all under valgrind which is kinda > handy at times) but it's deprecated and will be going away (as soon as > we get valgrind type functionality with the emulator or on-device). It > is the source of a lot of cruft in the build.
>> Cheers, >> Filipe
>> On Nov 7, 9:22 am, freedom <koansin....@gmail.com> wrote:
>>> Try >>> make TARGET_ARCH=x86 TARGET_BUILD_TYPE=release TARGET_PRODUCT=sim
>>> On Nov 5, 10:34 pm, Filipe Abrantes <filipe.abran...@gmail.com> wrote:
>>>> Hi all,
>>>> The target simulator compilation method for x86 works and we are able >>>> to run dalvik. However I am trying to compile android with all its >>>> components natively for x86. To do so I set up the repo thing as >>>> usually and then run make (without any "lunch") as
>>>> make TARGET_ARCH=x86
>>>> it goes through quite a few modules but eventually it complains about >>>> the lack of rule to make emulator. I dig through a few files in build/ >>>> (core and others) to try to understand how I could change this but I >>>> was not successfull. The output error is:
>>>> Install: out/host/linux-x86/bin/dexlist >>>> host Prebuilt: dexpreopt (out/host/linux-x86/obj/EXECUTABLES/ >>>> dexpreopt_intermediates/dexpreopt.py) >>>> make: *** No rule to make target `out/host/linux-x86/bin/emulator', >>>> needed by `out/host/linux-x86/bin/dexpreopt.py'. Stop.
>>>> Any help is much appreciated, Cheers, >>>> Filipe
>>>> On Oct 30, 1:53 pm, freedom <koansin....@gmail.com> wrote:
>>>>> a quick fix to the problem is "choosetype release" after >>>>> "lunch 2" because in release mode "SkDebugf()" is an >>>>> empty function instead of "Android_SkDebugf()"
>>>>> On Oct 30, 9:28 am, Jim Ancona <j...@anconafamily.com> wrote:
>>>>>> On Oct 23, 7:26 pm, fadden <thefad...@gmail.com> wrote:
>>>>>>> On Oct 23, 9:52 am, kapare <kevyn.alexandre.p...@gmail.com> wrote:
>>>>>>>> Can you give me clue or example of how to compile the dalvik for x86 >>>>>>>> or PPC.
>>>>>>> Start with:
>>>>>>> .build/envsetup.sh >>>>>>> lunch 2
>>>>>>> This configures you tobuildfor the desktop, linking against glibc. >>>>>>> This mode is NOT recommended for anything but experimental use. It >>>>>>> may go away. Don't use it; forget you saw it. Thanks.
>>>>>>> Buildthe world:
>>>>>>> make
>>>>>> When I try this (on Ubuntu 8.04, 32 bit), I get a bunch of errors >>>>>> similar to this:
>>>>>> out/debug/host/linux-x86/product/sim/obj/SHARED_LIBRARIES/ >>>>>> libmedia_intermediates/mediametadataretriever.o:/media/disk/jim/ >>>>>> projects/mydroid/external/skia/include/corecg/SkMath.h:180: more >>>>>> undefined references to `Android_SkDebugf(char const*, int, char >>>>>> const*, char const*, ...)' follow >>>>>> collect2: ld returned 1 exit status >>>>>> make: *** [out/debug/host/linux-x86/product/sim/obj/SHARED_LIBRARIES/ >>>>>> libmedia_intermediates/LINKED/libmedia.so] Error 1
>>>>>> I can fix them by adding
>>>>>> LOCAL_SHARED_LIBRARIES += libcorecg
>>>>>> to the relevant Android.mk files, but I'm curious if anyone else is >>>>>> seeing this, or if this is a problem with my environment.
You mentioned on Oct 21 that Google has done some native x86 port of
Android. Do you know when the code related to the native x86 port will
be released to the Android Open Source Project? We are interested in
getting Android to run on various x86-based devices and are willing to
contiribute toward the native x86 port effort. But it will be better
to base it on top of the native x86 port that Google has done.
> You mentioned on Oct 21 that Google has done some native x86 port of > Android. Do you know when the code related to the native x86 port will > be released to the Android Open Source Project? We are interested in > getting Android to run on various x86-based devices and are willing to > contiribute toward the native x86 port effort. But it will be better > to base it on top of the native x86 port that Google has done.
The engineer responsible for this project has been out of the office for a couple weeks and is travelling this week. He's working with our team to get his patches into the open source tree, but I think we're still a couple weeks away from completion there. We know people are excited about building android for x86 targets and will try to get this code cleaned up and submitted soon.
On Nov 7, 6:42 pm, Brian Swetland <swetl...@google.com> wrote:
> The engineer responsible for this project has been out of the office for
> a couple weeks and is travelling this week. He's working with our team
> to get his patches into the open source tree, but I think we're still a
> couple weeks away from completion there. We know people are excited
> about building android for x86 targets and will try to get this code
> cleaned up and submitted soon.
Brian,
Thanks for the update. I look forward to the release of x86 patches
that will enable us to run Android natively on x86 devices or PC.
Do you know how the project repositories will be structured to
accommodate the support of various x86 devices or targets? Are we
going to see different branches for x86 port? Are we expect to see
macros (such as #ifdef X86) guarding x86 related code in the source?
I'm looking for some guidelines on how x86 related code should be
integrated with the existing Android source. I haven't seen any
guideline regarding coding style or repository structures for hosting
device or architecture specific code yet. Maybe I haven't looked hard
enough. Any pointer is greatly appreciated.
Just to make it clear, the x86 Android port, at that point, requires running an Android kernel on a x86 device with flash storage. This is very different from running Dalvik under Windows or a pre-existing Linux installation (though with time these things will be possible to)
On Sun, Nov 9, 2008 at 10:01 AM, DYChen <dong-yuan.c...@intel.com> wrote:
> On Nov 7, 6:42 pm, Brian Swetland <swetl...@google.com> wrote:
> > The engineer responsible for this project has been out of the office for > > a couple weeks and is travelling this week. He's working with our team > > to get his patches into the open source tree, but I think we're still a > > couple weeks away from completion there. We know people are excited > > about building android for x86 targets and will try to get this code > > cleaned up and submitted soon.
> Brian,
> Thanks for the update. I look forward to the release of x86 patches > that will enable us to run Android natively on x86 devices or PC.
> Do you know how the project repositories will be structured to > accommodate the support of various x86 devices or targets? Are we > going to see different branches for x86 port? Are we expect to see > macros (such as #ifdef X86) guarding x86 related code in the source? > I'm looking for some guidelines on how x86 related code should be > integrated with the existing Android source. I haven't seen any > guideline regarding coding style or repository structures for hosting > device or architecture specific code yet. Maybe I haven't looked hard > enough. Any pointer is greatly appreciated.
Why is flash storage necessary? We were able to run Android over NFS, and others have used ext2 or ext3. So there should be no direct requirement for using a flash device specific filesystem like yaffs. As far as I know the only specific requirement is that read-write mmap has to be possible.
Are there other dependencies on flash storage?
Best Regards, Gergely
On Tue, Nov 11, 2008 at 10:28 AM, David Turner <di...@android.com> wrote: > Just to make it clear, the x86 Android port, at that point, requires running > an Android kernel on a x86 device with flash storage. > This is very different from running Dalvik under Windows or a pre-existing > Linux installation (though with time these things > will be possible to)
> On Sun, Nov 9, 2008 at 10:01 AM, DYChen <dong-yuan.c...@intel.com> wrote:
On Thu, Nov 13, 2008 at 9:39 AM, Gergely Kis <gergely....@gmail.com> wrote:
> Hello,
> Why is flash storage necessary? We were able to run Android over NFS,
> and others have used ext2 or ext3. So there should be no direct
> requirement for using a flash device specific filesystem like yaffs.
> As far as I know the only specific requirement is that read-write mmap
> has to be possible.
> Are there other dependencies on flash storage?
> Best Regards,
> Gergely
> On Tue, Nov 11, 2008 at 10:28 AM, David Turner <di...@android.com> wrote:
> > Just to make it clear, the x86 Android port, at that point, requires
> running
> > an Android kernel on a x86 device with flash storage.
> > This is very different from running Dalvik under Windows or a
> pre-existing
> > Linux installation (though with time these things
> > will be possible to)
> > On Sun, Nov 9, 2008 at 10:01 AM, DYChen <dong-yuan.c...@intel.com>
> wrote:
> [...]
We have been looking into this and we are in the process of internal
legal review and will be starting an AndroidOnIA project within the
context of the Android open source project soon.
We have a few interesting targets we are working on, but initially we
hope to get a KVM (or your VTx enabled VMM of choice) guest image
build working for people to play with,and then start pushing out
targets for real hardware.
--mgross
On Oct 21, 8:44 am, David Simmons <simm...@davidsimmons.com> wrote:
> Has anyone looked into what it would take to port Android to x86? I'm
> interested in taking a crack at porting Android to an x86-based
> embedded platform I work with. I'm going to download the source later
> today and have a look. My main concern is that Dalvik may be tied to
> special ARM optimizations...
Although I can compile with the command line:
make -j2 TARGET_ARCH=x86 TARGET_PRODUCT=generic
TARGET_SIMULATOR=true TARGET_BUILD_TYPE=release TARGET_OS=linux
LOCAL_PRELINK_MODULE=false
but I found lot of modules cannot be compiled with
"TARGET_SIMULATOR=true", if set false,the bionic(libc) met some files
(.h files) missing and compile failed.
Has anyone compiled the bionic successful?
Another question, Does any one knows more detail information about the
official x86 porting? for example:
Does the x86 porting support OpenGL?
Does the x86 porting still use openCore as the Media Framework? and
the openCore can be replaced by others(just like Hilex or GStreamer)?
Do not use TARGET_SIMULATOR=true, this flag should only be set when building
the Android simulator,
which doesn't require all system libraries and runs the Android "system"
into a single process on the host
machine.
that's why you have problems when building certain libraries (e.g. the
simulator uses the host's C library, not Bionic)
the x86 port only uses Android's own software OpenGL renderer. There is no
support for hardware-accelerated graphics
yet (and it's not like there is any kind of standard API for that on Linux).
OpenCore is supposed to be portable, so I
assume it runs (but I may be mistaken)
you can't easily replace OpenCore with something else, unless you modify all
the framework code that depends on it.
(this has never been tested internally)
On Fri, Nov 14, 2008 at 2:52 AM, Gang lee <ligang...@gmail.com> wrote:
> Hi all:
> Although I can compile with the command line:
> make -j2 TARGET_ARCH=x86 TARGET_PRODUCT=generic
> TARGET_SIMULATOR=true TARGET_BUILD_TYPE=release TARGET_OS=linux
> LOCAL_PRELINK_MODULE=false
> but I found lot of modules cannot be compiled with
> "TARGET_SIMULATOR=true", if set false,the bionic(libc) met some files
> (.h files) missing and compile failed.
> Has anyone compiled the bionic successful?
> Another question, Does any one knows more detail information about the
> official x86 porting? for example:
> Does the x86 porting support OpenGL?
> Does the x86 porting still use openCore as the Media Framework? and
> the openCore can be replaced by others(just like Hilex or GStreamer)?
I'm sorry for my copy&paste mistake.
I can compile with TARGET_SIMULATOR=true without any problem.
but when set "TARGET_SIMULATOR=false" in compile command, error below
happend
make: *** No rule to make target `out/host/linux-x86/bin/emulator',
needed by `out/host/linux-x86/bin/dexpreopt.py'. Stop.
Then I want to compile the bionic first.I did as follow.
1. Modify the Android.mk in mydroid/bionic to compile bionic in
simulator target
2. Compile all again with TARGET_SIMULATOR=true
the output as follow:
-------------------output------------------------
target thumb C: linker <= bionic/linker/linker.c
target thumb C: linker <= bionic/linker/dlfcn.c
bionic/linker/linker.c:15:25: error: sys/atomics.h: No such file or
directory
bionic/linker/linker.c:16:21: error: sys/tls.h: No such file or
directory
In file included from bionic/linker/dlfcn.c:18:
bionic/linker/linker.h:20: error: expected specifier-qualifier-list
before 'uintptr_t'
In file included from bionic/linker/linker.c:18:
bionic/linker/linker.h:20: error: expected specifier-qualifier-list
before 'uintptr_t'
bionic/linker/linker.h:50: error: expected specifier-qualifier-list
before 'uintptr_t'
bionic/linker/linker.h:50: error: expected specifier-qualifier-list
before 'uintptr_t'
---------------copy end(firest several lines)------------------
How can I compile bionic and other modules(init etc.)??
On 11月14日, 下午7时24分, "David Turner" <di...@android.com> wrote:
> Do not use TARGET_SIMULATOR=true, this flag should only be set when building
> the Android simulator,
> which doesn't require all system libraries and runs the Android "system"
> into a single process on the host
> machine.
> that's why you have problems when building certain libraries (e.g. the
> simulator uses the host's C library, not Bionic)
> the x86 port only uses Android's own software OpenGL renderer. There is no
> support for hardware-accelerated graphics
> yet (and it's not like there is any kind of standard API for that on Linux).
> OpenCore is supposed to be portable, so I
> assume it runs (but I may be mistaken)
> you can't easily replace OpenCore with something else, unless you modify all
> the framework code that depends on it.
> (this has never been tested internally)
> On Fri, Nov 14, 2008 at 2:52 AM, Gang lee <ligang...@gmail.com> wrote:
> > Hi all:
> > Although I can compile with the command line:
> > make -j2 TARGET_ARCH=x86 TARGET_PRODUCT=generic
> > TARGET_SIMULATOR=true TARGET_BUILD_TYPE=release TARGET_OS=linux
> > LOCAL_PRELINK_MODULE=false
> > but I found lot of modules cannot be compiled with
> > "TARGET_SIMULATOR=true", if set false,the bionic(libc) met some files
> > (.h files) missing and compile failed.
> > Has anyone compiled the bionic successful?
> > Another question, Does any one knows more detail information about the
> > official x86 porting? for example:
> > Does the x86 porting support OpenGL?
> > Does the x86 porting still use openCore as the Media Framework? and
> > the openCore can be replaced by others(just like Hilex or GStreamer)?
when I compiled whit TARGET_SIMULATOR=false, the output said "find:
prebuilt/android-x86: No such file or directory"
the make try to find prebuilt/android-x86 directory, and there is no
such directory,only have linux-x86 directory.
In the mydroid/build/core/envsetup.mk
--------------------------------
envsetup.mk-----------------------------
ifeq ($(TARGET_SIMULATOR),true)
TARGET_PREBUILT_TAG := $(TARGET_OS)-$(TARGET_ARCH)
else
TARGET_PREBUILT_TAG := android-$(TARGET_ARCH)
endif
--------------------------------copy end-----------------------------
Say in other words,If I set TARGET_SIMULATOR=false, I cannot use the
prebuild content??
On 11月14日, 下午7时24分, "David Turner" <di...@android.com> wrote:
> Do not use TARGET_SIMULATOR=true, this flag should only be set when building
> the Android simulator,
> which doesn't require all system libraries and runs the Android "system"
> into a single process on the host
> machine.
> that's why you have problems when building certain libraries (e.g. the
> simulator uses the host's C library, not Bionic)
> the x86 port only uses Android's own software OpenGL renderer. There is no
> support for hardware-accelerated graphics
> yet (and it's not like there is any kind of standard API for that on Linux).
> OpenCore is supposed to be portable, so I
> assume it runs (but I may be mistaken)
> you can't easily replace OpenCore with something else, unless you modify all
> the framework code that depends on it.
> (this has never been tested internally)
> On Fri, Nov 14, 2008 at 2:52 AM, Gang lee <ligang...@gmail.com> wrote:
> > Hi all:
> > Although I can compile with the command line:
> > make -j2 TARGET_ARCH=x86 TARGET_PRODUCT=generic
> > TARGET_SIMULATOR=true TARGET_BUILD_TYPE=release TARGET_OS=linux
> > LOCAL_PRELINK_MODULE=false
> > but I found lot of modules cannot be compiled with
> > "TARGET_SIMULATOR=true", if set false,the bionic(libc) met some files
> > (.h files) missing and compile failed.
> > Has anyone compiled the bionic successful?
> > Another question, Does any one knows more detail information about the
> > official x86 porting? for example:
> > Does the x86 porting support OpenGL?
> > Does the x86 porting still use openCore as the Media Framework? and
> > the openCore can be replaced by others(just like Hilex or GStreamer)?
markgross wrote:
> We have been looking into this and we are in the process of internal
> legal review and will be starting an AndroidOnIA project within the
> context of the Android open source project soon.
> We have a few interesting targets we are working on, but initially we
> hope to get a KVM (or your VTx enabled VMM of choice) guest image
> build working for people to play with,and then start pushing out
> targets for real hardware.
> --mgross
> On Oct 21, 8:44 am, David Simmons <simm...@davidsimmons.com> wrote:
>> Has anyone looked into what it would take to port Android to x86? I'm
>> interested in taking a crack at porting Android to an x86-based
>> embedded platform I work with. I'm going to download the source later
>> today and have a look. My main concern is that Dalvik may be tied to
>> special ARM optimizations...
Good afternoon everyone,
there is a problem during my Android kernel compiling .
I followed the guideline which is
https://sites.google.com/a/android.com/opensource/download and searched google for the answer, but still it cannot be solved.
===
Cannot locate File/ Basename.pm in @INC
( @INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/
share
/perl/5.8.8 /usr/lib/perl5 /usr/lib/perl/5.8 /usr/share/perl/
5.8 /usr/local
/lib/site_perl. )
at external/webkit/JavaScriptCore/pcre/dftables line 47
BEGIN failed--compilation aborted at external/webkit/JavaScriptCore/
pcre/dftables line 47
make" ***[out/target/product/generic/obj/STATIC_LIBRARIES/
libkjs_intermediates/chartables.c]Error2
===
Can anyone give me some advice? I'll appreciate u very much.
My ubuntu is 8.10. I try the tips to compile android for x86. But it
seem envsetup.sh does not work. Would you like to help me? Thank you
very much. The log is as below.
thomast@ubuntu:~/mydroid/build$ echo $SHELL
/bin/bash
thomast@ubuntu:~/mydroid/build$ bash --version
GNU bash, version 3.2.39(1)-release (i486-pc-linux-gnu)
Copyright (C) 2007 Free Software Foundation, Inc.
thomast@ubuntu:~/mydroid/build$ ./envsetup.sh lunch 2
thomast@ubuntu:~/mydroid/build$ ./envsetup.sh help
thomast@ubuntu:~/mydroid/build$
On Oct 24, 7:26 am, fadden <thefad...@gmail.com> wrote:
> On Oct 23, 9:52 am, kapare <kevyn.alexandre.p...@gmail.com> wrote:
> > Can you give me clue or example of how to compile the dalvik for x86
> > or PPC.
> Start with:
> . build/envsetup.sh
> lunch 2
> This configures you to build for the desktop, linking against glibc.
> This mode is NOT recommended for anything but experimental use. It
> may go away. Don't use it; forget you saw it. Thanks.
> Build the world:
> make
> When that completes, you have a working dalvikm on your desktop
> machine:
> To actually do something, you need to specify the bootstrap class path
> and give it a place to put DEX data that it uncompresses from jar
> files. You can do that with a script like this:
> ----- snip & save -----
> #!/bin/sh
> # base directory, at top of source tree; replace with absolute path
> base=`pwd`
> # configure root dir of interesting stuff
> root=$base/out/debug/host/linux-x86/product/sim/system
> export ANDROID_ROOT=$root
> # this is where we create the dalvik-cache directory; make sure it
> exists
> export ANDROID_DATA=/tmp/dalvik_$USER
> mkdir -p $ANDROID_DATA/dalvik_cache
> exec dalvikvm $@
> -----
> Of course, you can't just run this against javac output, since it's
> not a Java VM. You have to run your class files through "dx":
> % cat > Foo.java
> class Foo { public static void main(String[] args) {
> System.out.println("Hello, world");
> } }
> (ctrl-D)
> % javac Foo.java
> % dx --dex --output=foo.jar Foo.class
> % ./rund -cp foo.jar Foo
> Hello, world
> I/dalvikvm(19564): DestroyJavaVM shutting VM down
> (I really ought to get rid of that DestroyJavaVM line -- it's supposed
> to be in the log file, but on the desktop the "log file" is stderr.)
> Get some info about valid arguments like this:
> % ./rund -help
> This also shows what options the VM was configured with. The "lunch
> 2" build has all sorts of additional assertions and checks enabled,
> which slows the VM down, but since this is just for experiments it
> doesn't matter.
> All of the above applies to x86 Linux. Anything else will likely
> require a porting effort.
On Mon, Dec 1, 2008 at 2:30 PM, Lucky-dog <Honglian...@gmail.com> wrote:
> My ubuntu is 8.10. I try the tips to compile android for x86. But it
> seem envsetup.sh does not work. Would you like to help me? Thank you
> very much. The log is as below.
> thomast@ubuntu:~/mydroid/build$ echo $SHELL
> /bin/bash
> thomast@ubuntu:~/mydroid/build$ bash --version
> GNU bash, version 3.2.39(1)-release (i486-pc-linux-gnu)
> Copyright (C) 2007 Free Software Foundation, Inc.
> thomast@ubuntu:~/mydroid/build$ ./envsetup.sh lunch 2
> thomast@ubuntu:~/mydroid/build$ ./envsetup.sh help
> thomast@ubuntu:~/mydroid/build$
> On Oct 24, 7:26 am, fadden <thefad...@gmail.com> wrote:
>> On Oct 23, 9:52 am, kapare <kevyn.alexandre.p...@gmail.com> wrote:
>> > Can you give me clue or example of how to compile the dalvik for x86
>> > or PPC.
>> Start with:
>> . build/envsetup.sh
>> lunch 2
>> This configures you to build for the desktop, linking against glibc.
>> This mode is NOT recommended for anything but experimental use. It
>> may go away. Don't use it; forget you saw it. Thanks.
>> Build the world:
>> make
>> When that completes, you have a working dalvikm on your desktop
>> machine:
>> To actually do something, you need to specify the bootstrap class path
>> and give it a place to put DEX data that it uncompresses from jar
>> files. You can do that with a script like this:
>> ----- snip & save -----
>> #!/bin/sh
>> # base directory, at top of source tree; replace with absolute path
>> base=`pwd`
>> # configure root dir of interesting stuff
>> root=$base/out/debug/host/linux-x86/product/sim/system
>> export ANDROID_ROOT=$root
>> # this is where we create the dalvik-cache directory; make sure it
>> exists
>> export ANDROID_DATA=/tmp/dalvik_$USER
>> mkdir -p $ANDROID_DATA/dalvik_cache
>> exec dalvikvm $@
>> -----
>> Of course, you can't just run this against javac output, since it's
>> not a Java VM. You have to run your class files through "dx":
>> % cat > Foo.java
>> class Foo { public static void main(String[] args) {
>> System.out.println("Hello, world");
>> } }
>> (ctrl-D)
>> % javac Foo.java
>> % dx --dex --output=foo.jar Foo.class
>> % ./rund -cp foo.jar Foo
>> Hello, world
>> I/dalvikvm(19564): DestroyJavaVM shutting VM down
>> (I really ought to get rid of that DestroyJavaVM line -- it's supposed
>> to be in the log file, but on the desktop the "log file" is stderr.)
>> Get some info about valid arguments like this:
>> % ./rund -help
>> This also shows what options the VM was configured with. The "lunch
>> 2" build has all sorts of additional assertions and checks enabled,
>> which slows the VM down, but since this is just for experiments it
>> doesn't matter.
>> All of the above applies to x86 Linux. Anything else will likely
>> require a porting effort.
hi all
when i try to compile the source on DEBUG x86. A error is reported
out as below. Would you like to let me know how to fix it? Thank you
very much.
thomast@ubuntu:~/mydroid$ make
build/core/product_config.mk:229: WARNING: adding test OTA key
build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
============================================
TARGET_PRODUCT=sim
TARGET_SIMULATOR=true
TARGET_BUILD_TYPE=debug
TARGET_ARCH=x86
TARGET_OS=linux
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=TC3
============================================
target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp
In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
from /usr/include/c++/4.3/utility:68,
from external/webkit/JavaScriptCore/wtf/
VectorTraits.h:27,
from external/webkit/JavaScriptCore/kjs/
LocalStorage.h:29,
from external/webkit/JavaScriptCore/kjs/
JSVariableObject.h:32,
from external/webkit/JavaScriptCore/kjs/
JSGlobalObject.h:26,
from external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp:32:
/usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
previously declared here
make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
libkjs_intermediates/bindings/NP_jsobject.o] Error 1
thomast@ubuntu:~/mydroid$
thomast@ubuntu:~/mydroid$ make
build/core/product_config.mk:229: WARNING: adding test OTA key
build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
============================================
TARGET_PRODUCT=sim
TARGET_SIMULATOR=true
TARGET_BUILD_TYPE=debug
TARGET_ARCH=x86
TARGET_OS=linux
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=TC3
============================================
target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp
In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
from /usr/include/c++/4.3/utility:68,
from external/webkit/JavaScriptCore/wtf/
VectorTraits.h:27,
from external/webkit/JavaScriptCore/kjs/
LocalStorage.h:29,
from external/webkit/JavaScriptCore/kjs/
JSVariableObject.h:32,
from external/webkit/JavaScriptCore/kjs/
JSGlobalObject.h:26,
from external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp:32:
/usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
previously declared here
make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
libkjs_intermediates/bindings/NP_jsobject.o] Error 1
thomast@ubuntu:~/mydroid$
thomast@ubuntu:~/mydroid$ make
build/core/product_config.mk:229: WARNING: adding test OTA key
build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
============================================
TARGET_PRODUCT=sim
TARGET_SIMULATOR=true
TARGET_BUILD_TYPE=debug
TARGET_ARCH=x86
TARGET_OS=linux
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=TC3
============================================
target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp
In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
from /usr/include/c++/4.3/utility:68,
from external/webkit/JavaScriptCore/wtf/
VectorTraits.h:27,
from external/webkit/JavaScriptCore/kjs/
LocalStorage.h:29,
from external/webkit/JavaScriptCore/kjs/
JSVariableObject.h:32,
from external/webkit/JavaScriptCore/kjs/
JSGlobalObject.h:26,
from external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp:32:
/usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
previously declared here
make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
libkjs_intermediates/bindings/NP_jsobject.o] Error 1
thomast@ubuntu:~/mydroid$
thomast@ubuntu:~/mydroid$ make
build/core/product_config.mk:229: WARNING: adding test OTA key
build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
============================================
TARGET_PRODUCT=sim
TARGET_SIMULATOR=true
TARGET_BUILD_TYPE=debug
TARGET_ARCH=x86
TARGET_OS=linux
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=TC3
============================================
target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp
In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
from /usr/include/c++/4.3/utility:68,
from external/webkit/JavaScriptCore/wtf/
VectorTraits.h:27,
from external/webkit/JavaScriptCore/kjs/
LocalStorage.h:29,
from external/webkit/JavaScriptCore/kjs/
JSVariableObject.h:32,
from external/webkit/JavaScriptCore/kjs/
JSGlobalObject.h:26,
from external/webkit/JavaScriptCore/bindings/
NP_jsobject.cpp:32:
/usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
previously declared here
make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
libkjs_intermediates/bindings/NP_jsobject.o] Error 1
thomast@ubuntu:~/mydroid$
hi all
I fixed it with renaming swap to swapab. But now I have another
question needed your help. I can't let the following command get to be
run.
dx --dex --output=foo.jar Foo.class
What is the dx command and where is it? Would you like to help me
out? Thank you very much.
On Dec 3, 10:12 pm, Lucky-dog <Honglian...@gmail.com> wrote:
> hi all
> when i try to compile the source on DEBUG x86. A error is reported
> out as below. Would you like to let me know how to fix it? Thank you
> very much.
> thomast@ubuntu:~/mydroid$ make
> build/core/product_config.mk:229: WARNING: adding test OTA key
> build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
> ============================================
> TARGET_PRODUCT=sim
> TARGET_SIMULATOR=true
> TARGET_BUILD_TYPE=debug
> TARGET_ARCH=x86
> TARGET_OS=linux
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=TC3
> ============================================
> target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp
> In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
> from /usr/include/c++/4.3/utility:68,
> from external/webkit/JavaScriptCore/wtf/
> VectorTraits.h:27,
> from external/webkit/JavaScriptCore/kjs/
> LocalStorage.h:29,
> from external/webkit/JavaScriptCore/kjs/
> JSVariableObject.h:32,
> from external/webkit/JavaScriptCore/kjs/
> JSGlobalObject.h:26,
> from external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp:32:
> /usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
> ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
> algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> previously declared here
> make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
> libkjs_intermediates/bindings/NP_jsobject.o] Error 1
> thomast@ubuntu:~/mydroid$
> thomast@ubuntu:~/mydroid$ make
> build/core/product_config.mk:229: WARNING: adding test OTA key
> build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
> ============================================
> TARGET_PRODUCT=sim
> TARGET_SIMULATOR=true
> TARGET_BUILD_TYPE=debug
> TARGET_ARCH=x86
> TARGET_OS=linux
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=TC3
> ============================================
> target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp
> In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
> from /usr/include/c++/4.3/utility:68,
> from external/webkit/JavaScriptCore/wtf/
> VectorTraits.h:27,
> from external/webkit/JavaScriptCore/kjs/
> LocalStorage.h:29,
> from external/webkit/JavaScriptCore/kjs/
> JSVariableObject.h:32,
> from external/webkit/JavaScriptCore/kjs/
> JSGlobalObject.h:26,
> from external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp:32:
> /usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
> ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
> algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> previously declared here
> make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
> libkjs_intermediates/bindings/NP_jsobject.o] Error 1
> thomast@ubuntu:~/mydroid$
> thomast@ubuntu:~/mydroid$ make
> build/core/product_config.mk:229: WARNING: adding test OTA key
> build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
> ============================================
> TARGET_PRODUCT=sim
> TARGET_SIMULATOR=true
> TARGET_BUILD_TYPE=debug
> TARGET_ARCH=x86
> TARGET_OS=linux
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=TC3
> ============================================
> target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp
> In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
> from /usr/include/c++/4.3/utility:68,
> from external/webkit/JavaScriptCore/wtf/
> VectorTraits.h:27,
> from external/webkit/JavaScriptCore/kjs/
> LocalStorage.h:29,
> from external/webkit/JavaScriptCore/kjs/
> JSVariableObject.h:32,
> from external/webkit/JavaScriptCore/kjs/
> JSGlobalObject.h:26,
> from external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp:32:
> /usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
> ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
> algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> previously declared here
> make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
> libkjs_intermediates/bindings/NP_jsobject.o] Error 1
> thomast@ubuntu:~/mydroid$
> thomast@ubuntu:~/mydroid$ make
> build/core/product_config.mk:229: WARNING: adding test OTA key
> build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
> ============================================
> TARGET_PRODUCT=sim
> TARGET_SIMULATOR=true
> TARGET_BUILD_TYPE=debug
> TARGET_ARCH=x86
> TARGET_OS=linux
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=TC3
> ============================================
> target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp
> In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
> from /usr/include/c++/4.3/utility:68,
> from external/webkit/JavaScriptCore/wtf/
> VectorTraits.h:27,
> from external/webkit/JavaScriptCore/kjs/
> LocalStorage.h:29,
> from external/webkit/JavaScriptCore/kjs/
> JSVariableObject.h:32,
> from external/webkit/JavaScriptCore/kjs/
> JSGlobalObject.h:26,
> from external/webkit/JavaScriptCore/bindings/
> NP_jsobject.cpp:32:
> /usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
> ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
> algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> previously declared here
> make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
> libkjs_intermediates/bindings/NP_jsobject.o] Error 1
> thomast@ubuntu:~/mydroid$
> hi all
> I fixed it with renaming swap to swapab. But now I have another
> question needed your help. I can't let the following command get to be
> run.
> dx --dex --output=foo.jar Foo.class
> What is the dx command and where is it? Would you like to help me
> out? Thank you very much.
> On Dec 3, 10:12 pm, Lucky-dog <Honglian...@gmail.com> wrote:
> > hi all
> > when i try to compile the source on DEBUG x86. A error is reported
> > out as below. Would you like to let me know how to fix it? Thank you
> > very much.
> > thomast@ubuntu:~/mydroid$ make
> > build/core/product_config.mk:229: WARNING: adding test OTA key
> > build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
> > ============================================
> > TARGET_PRODUCT=sim
> > TARGET_SIMULATOR=true
> > TARGET_BUILD_TYPE=debug
> > TARGET_ARCH=x86
> > TARGET_OS=linux
> > HOST_ARCH=x86
> > HOST_OS=linux
> > HOST_BUILD_TYPE=release
> > BUILD_ID=TC3
> > ============================================
> > target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
> > NP_jsobject.cpp
> > In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
> > from /usr/include/c++/4.3/utility:68,
> > from external/webkit/JavaScriptCore/wtf/
> > VectorTraits.h:27,
> > from external/webkit/JavaScriptCore/kjs/
> > LocalStorage.h:29,
> > from external/webkit/JavaScriptCore/kjs/
> > JSVariableObject.h:32,
> > from external/webkit/JavaScriptCore/kjs/
> > JSGlobalObject.h:26,
> > from external/webkit/JavaScriptCore/bindings/
> > NP_jsobject.cpp:32:
> > /usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
> > ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> > external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
> > algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> > previously declared here
> > make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
> > libkjs_intermediates/bindings/NP_jsobject.o] Error 1
> > thomast@ubuntu:~/mydroid$
Does anyone have an idea why I get this error?
============================================
TARGET_PRODUCT=generic
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=x86
TARGET_OS=linux
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=TC3
============================================
host C++: simulator <= development/simulator/app/DeviceManager.cpp
In file included from /usr/include/wx-2.6/wx/memory.h:20,
from /usr/include/wx-2.6/wx/object.h:25,
from /usr/include/wx-2.6/wx/wx.h:16,
from development/simulator/app/DeviceManager.cpp:12:
/usr/include/wx-2.6/wx/string.h:771: error: âwxChar& wxString::operator
[](unsigned int)â cannot be overloaded
/usr/include/wx-2.6/wx/string.h:768: error: with âwxChar&
wxString::operator[](size_t)â
In file included from /usr/include/wx-2.6/wx/stream.h:26,
from /usr/include/wx-2.6/wx/image.h:24,
from /usr/include/wx-2.6/wx/gtk/cursor.h:23,
from /usr/include/wx-2.6/wx/cursor.h:24,
from /usr/include/wx-2.6/wx/event.h:32,
from /usr/include/wx-2.6/wx/wx.h:23,
from development/simulator/app/DeviceManager.cpp:12:
/usr/include/wx-2.6/wx/filefn.h:322: error: zero width for bit-field
âwxAssert_323::BadFileSizeTypeâ
In file included from /usr/include/wx-2.6/wx/utils.h:38,
from /usr/include/wx-2.6/wx/cursor.h:37,
from /usr/include/wx-2.6/wx/event.h:32,
from /usr/include/wx-2.6/wx/wx.h:23,
from development/simulator/app/DeviceManager.cpp:12:
/usr/include/wx-2.6/wx/longlong.h: In constructor
âwxLongLongNative::wxLongLongNative(long int, long unsigned int)â:
/usr/include/wx-2.6/wx/longlong.h:115: warning: left shift count >=
width of type
/usr/include/wx-2.6/wx/longlong.h: In member function âlong int
wxLongLongNative::GetHi() constâ:
pe
/usr/include/wx-2.6/wx/longlong.h: In constructor
âwxULongLongNative::wxULongLongNative(long unsigned int, long unsigned
int)â:
/usr/include/wx-2.6/wx/longlong.h:333: warning: left shift count >=
width of type
/usr/include/wx-2.6/wx/longlong.h: In member function âlong unsigned
int wxULongLongNative::GetHi() constâ:
/usr/include/wx-2.6/wx/longlong.h:351: warning: right shift count >=
width of type
In file included from development/simulator/app/LogWindow.h:13,
from development/simulator/app/MainFrame.h:11,
from development/simulator/app/MyApp.h:12,
from development/simulator/app/DeviceManager.cpp:17:
development/simulator/app/LogPrefsDialog.h: At global scope:
development/simulator/app/LogPrefsDialog.h:28: warning: âtypedefâ was
ignored in this declaration
make: *** [out/host/linux-x86/obj/EXECUTABLES/simulator_intermediates/
DeviceManager.o] Error 1
Is this maybe a x86_64 specific problem? I followed the description
for x86_64 and could do the "normal" build. But if I try to do the x86
"application-like" build I get that error... I'm trying this on a
Ubuntu 8.10 system...
Thanks, for any help
On Dec 6, 12:49 am, Lucky-dog <Honglian...@gmail.com> wrote:
> I got it. it located in out/host/linux-x86/bin. Thanks.
> On Dec 4, 10:28 am, Lucky-dog <Honglian...@gmail.com> wrote:
> > hi all
> > I fixed it with renaming swap to swapab. But now I have another
> > question needed your help. I can't let the following command get to be
> > run.
> > dx --dex --output=foo.jar Foo.class
> > What is the dx command and where is it? Would you like to help me
> > out? Thank you very much.
> > On Dec 3, 10:12 pm, Lucky-dog <Honglian...@gmail.com> wrote:
> > > hi all
> > > when i try to compile the source on DEBUGx86. A error is reported
> > > out as below. Would you like to let me know how to fix it? Thank you
> > > very much.
> > > thomast@ubuntu:~/mydroid$ make
> > > build/core/product_config.mk:229: WARNING: adding test OTA key
> > > build/core/main.mk:177: implicitly installing apns-conf_sdk.xml
> > > ============================================
> > > TARGET_PRODUCT=sim
> > > TARGET_SIMULATOR=true
> > > TARGET_BUILD_TYPE=debug
> > > TARGET_ARCH=x86
> > > TARGET_OS=linux
> > > HOST_ARCH=x86
> > > HOST_OS=linux
> > > HOST_BUILD_TYPE=release
> > > BUILD_ID=TC3
> > > ============================================
> > > target thumb C++: libkjs <= external/webkit/JavaScriptCore/bindings/
> > > NP_jsobject.cpp
> > > In file included from /usr/include/c++/4.3/bits/stl_pair.h:65,
> > > from /usr/include/c++/4.3/utility:68,
> > > from external/webkit/JavaScriptCore/wtf/
> > > VectorTraits.h:27,
> > > from external/webkit/JavaScriptCore/kjs/
> > > LocalStorage.h:29,
> > > from external/webkit/JavaScriptCore/kjs/
> > > JSVariableObject.h:32,
> > > from external/webkit/JavaScriptCore/kjs/
> > > JSGlobalObject.h:26,
> > > from external/webkit/JavaScriptCore/bindings/
> > > NP_jsobject.cpp:32:
> > > /usr/include/c++/4.3/bits/stl_move.h:80: error: redefinition of
> > > ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> > > external/webkit/JavaScriptCore/../WebCore/platform/android/stl/
> > > algorithm:65: error: ‘template<class _Tp> void std::swap(_Tp&, _Tp&)’
> > > previously declared here
> > > make: *** [out/debug/host/linux-x86/product/sim/obj/STATIC_LIBRARIES/
> > > libkjs_intermediates/bindings/NP_jsobject.o] Error 1
> > > thomast@ubuntu:~/mydroid$
The most exciting update yet comes the day before I leave for a two
week vacation. Hopefully I will be able to try it before I leave. I
have been trying to repo init and repo sync to this since yesterday
but am getting a ton of socket errors. It could be an issue with our
SOCKs proxies but I have tried a number of different proxy servers in
our company (they do not usually all go down at the same time). I am
not sure how many others are having similar problems.
Thanks for the details,
Chris Elford
Intel Software Services Group
> > Boot from the usb stick. The installer is a bit crude, and needs polishing
> > and generalizing but it works. Note: It WILL WIPE your EeePC drive. :)
> > --Dima
> > On Thu, Dec 18, 2008 at 12:10 PM, Piethein Strengholt <
> > pietheinstrengh...@gmail.com> wrote:
> The most exciting update yet comes the day before I leave for a two
> week vacation. Hopefully I will be able to try it before I leave. I
> have been trying to repo init and repo sync to this since yesterday
> but am getting a ton of socket errors. It could be an issue with our
> SOCKs proxies but I have tried a number of different proxy servers in
> our company (they do not usually all go down at the same time). I am
> not sure how many others are having similar problems.
> Thanks for the details,
> Chris Elford
> Intel Software Services Group
> Dima Zavin wrote:
>> Argh, forgot to mention that you'll need a local_manifest.xml that looks
>> something like this:
>> On Thu, Dec 18, 2008 at 12:23 PM, Dima Zavin <d...@android.com> wrote:
>>> Try this (only tested on EeePC 701):
>>> repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
>>> repo sync
>>> TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -j8
>>> installer_img
>>> dd if=out/target/product/eee_701/installer.img of=/dev/<usbstick of your
>>> choice> ; sync
>>> Boot from the usb stick. The installer is a bit crude, and needs polishing
>>> and generalizing but it works. Note: It WILL WIPE your EeePC drive. :)
>>> --Dima
>>> On Thu, Dec 18, 2008 at 12:10 PM, Piethein Strengholt <
>>> pietheinstrengh...@gmail.com> wrote: