/usr/lib/gcc/i486-linux-gnu/4.2.3/cc1plus

It seems to be using the gcc that I happen to have installed on my
Ubuntu 8.04 system...

celf...@celford-ubuntu:~/cupcake$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c+
+,fortran,objc,obj-c++,treelang --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.2
--program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --
enable-objc-gc --enable-mpfr --enable-targets=all --enable-
checking=release --build=i486-linux-gnu --host=i486-linux-gnu --
target=i486-linux-gnu
Thread model: posix
gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)

Part of the build may also be using the bits at cupcake/prebuilt/linux-
x86/toolchain/i686-unknown-linux-gnu-4.2.1...

Thx,
Chris

On Dec 19, 2:05 pm, Huan Truong <huan...@gmail.com> wrote:
> Chris et al,
>
> Can you tell me the version of gcc you're using to compile. Seems like
> gcc-4.3 has many problems with cupcake.
>
> On Dec 19, 3:44 pm, Chris <chris.l.elf...@intel.com> wrote:
>
> > I have been able to successfully run the eee701 cupcake build on an
> > MSI Wind.  I have a _VERY_ preliminary script that takes the
> > installer.img and a USB stick and creates a "live" USB stick that can
> > be booted.  Running off of USB will make some apps timeout a bit more
> > because its not as fast as internal storage but it makes it easy to
> > try it out.
>
> > If anyone is interested in the liveUSB conversion script, I can submit
> > a changeset (probably to put in vendor/asus/eee_701 for now).  Bear in
> > mind this version of the script is very preliminary and I plan to
> > update it some after my vacation.
>
> > Thx,
>
> > Chris Elford
> > Intel Software Services Group
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to