Fwd: [android-building] Is there an official recommended way of building vbox_x86-eng target?

[Ron M]

Platform and Kernel groups: Sorry for cross-posting.

I would appreciate help with this issue.

And would LOVE to know (JBQ?) why isn't /proc/config.gz  available for the ICS x86-emulator build. 

I can't tell (at the moment) what is wrong with my configuration as i can't get a reference configuration from the ICS kernel as I could in the past (Well, at least for the ARM goldfish variant).

What I see in the kernel listing:

 ~/Android/ICS_Master/kernel/goldfish/arch/x86/configs$ ls

goldfish_defconfig  i386_defconfig  vbox_defconfig  x86_64_defconfig

And none of those compile (Used the vbox_defconfig).

More information on my host (Ubuntu X86 11.10):

~/Android/ICS_Master/kernel/goldfish/arch/x86/configs$ cat /proc/version

Linux version 3.0.0-12-generic (buildd@crested) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011

Thanks.

On Sun, Nov 20, 2011 at 3:58 PM, Ron M <ron...@gmail.com> wrote:

Dan, I followed your instructions but I  am having problems with the kernel build:

 ~/Android/ICS_Master/kernel/goldfish$ make ARCH=x86

scripts/kconfig/conf -s arch/x86/Kconfig

  CHK     include/linux/version.h

  CHK     include/linux/utsrelease.h

  SYMLINK include/asm -> include/asm-x86

  CALL    scripts/checksyscalls.sh

  CHK     include/linux/compile.h

  VDSO    arch/x86/vdso/vdso32-int80.so.dbg

gcc: error: elf_i386: No such file or directory

make[1]: *** [arch/x86/vdso/vdso32-int80.so.dbg] Error 1

make: *** [arch/x86/vdso] Error 2

Attached my .config .

Any idea?

Thanks,

Ron

On Sun, Nov 20, 2011 at 2:40 PM, Ron M <ron...@gmail.com> wrote:

Thanks Dan, I'm going to give it a shot.

Just to double check, did you have the same problem before rebuilding the kernel from sources?

Also, does anyone know why the "Disable mouse pointer integration" is disabled in this project?

JBQ:

As for this specific post I was actually wondering about an official "build recipe", so I think it actually goes here. (lunch <config>  and make <target options...> )

However, I think it would be useful to have some clarifications about the "recommended google-groups" for the various topics.

People, (and of course myself) sin to cross-post or mis-post just because we are not sure what goes where.

Would be great to have some sort of "index" in  source.android.com,  on this mailing list, or wherever you think it should go.

-Ron

On Fri, Nov 18, 2011 at 12:00 AM, Doug Schaefer <cdt...@gmail.com> wrote:

And I have a mouse pointer. Thanks for the help guys!

On Thu, Nov 17, 2011 at 2:05 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> Yup. Sorry the kernels are a bit hard to find without gitweb. Once I
> have the relevant projects created, I'll create a proper list on
> source.android.com.
>
> JBQ
>
> On Thu, Nov 17, 2011 at 10:55 AM, Daniel FAGES <dfa...@gmail.com> wrote:
>> Quoting JBQ :
>>
>> The emulator kernel source is available:
>>
>> git clone https://android.googlesource.com/kernel/goldfish
>> cd goldfish
>> git checkout origin/android-goldfish-2.6.29
>>
>> 2011/11/17 Doug Schaefer <cdt...@gmail.com>
>>>
>>> Sorry guys, I lost track of where the kernel source is. Could you repeat
>>> that?
>>>
>>> Thanks,
>>> Doug.
>>>
>>> On Thu, Nov 17, 2011 at 1:43 PM, Daniel FAGES <dfa...@gmail.com> wrote:
>>> > Yes, and you have to add the "PS/2 mouse" support to the vbox_defconfig
>>> > to
>>> > have the mouse working using VirtualBox.
>>> >
>>> > Dan.
>>> >
>>> > 2011/11/17 Jean-Baptiste Queru <j...@android.com>
>>> >>
>>> >> Just as an FYI, the prebuilt vbox kernel exactly matches the sources
>>> >> that I've released, so a straight rebuild as-is should get the same
>>> >> results (fingers crossed), and you'll need to actually make changes in
>>> >> order to make progress.
>>> >>
>>> >> JBQ
>>> >>
>>> >> On Thu, Nov 17, 2011 at 10:28 AM, Nathaniel Husted <nhu...@gmail.com>
>>> >> wrote:
>>> >> > I'll try that later as well. I know with a bit of searching there's a
>>> >> > link JBQ posted to the 4.0.1 kernel sources that were released in the
>>> >> > SDK. I figure that could be easily rebuild as well with appropriate
>>> >> > x86 support.
>>> >> >
>>> >> > Cheers,
>>> >> > Nathaniel
>>> >> >
>>> >> > On Thu, Nov 17, 2011 at 12:30 PM, Daniel FAGES <dfa...@gmail.com>
>>> >> > wrote:
>>> >> >> Hi,
>>> >> >> I'm not sure you saw my post few hours ago but to get the mouse
>>> >> >> pointer
>>> >> >> you
>>> >> >> have to rebuild the kernel with the good driver.
>>> >> >>
>>> >> >> Dan.
>>> >> >>
>>> >> >> 2011/11/17 Doug Schaefer <cdt...@gmail.com>
>>> >> >>>
>>> >> >>> From what I've seen, the graphics are pretty good (i.e fast
>>> >> >>> enough).
>>> >> >>> It's really an input issue I suppose. Android-x86 used to have a
>>> >> >>> patch
>>> >> >>> to make it work. Given I've seen a mouse pointer on the
>>> >> >>> Transformer, I
>>> >> >>> was hoping it would be part of the base and not a driver that ASUS
>>> >> >>> had
>>> >> >>> added (who seems to be quasi involved with android-x86 now that I
>>> >> >>> think about it, hmmm).
>>> >> >>>
>>> >> >>> On Thu, Nov 17, 2011 at 11:41 AM, Jean-Baptiste Queru
>>> >> >>> <j...@android.com>
>>> >> >>> wrote:
>>> >> >>> > I haven't been looking at the state of vbox in ICS other than
>>> >> >>> > making
>>> >> >>> > sure that it'd compile. I wouldn't go as far as calling it a
>>> >> >>> > hack,
>>> >> >>> > but
>>> >> >>> > it probably fell behind a bit, especially in the domain of
>>> >> >>> > graphics
>>> >> >>> > (where things have evolved a lot) and input (where things have
>>> >> >>> > changed
>>> >> >>> > as well). Let's call it "work in progress".
>>> >> >>> >
>>> >> >>> > JBQ
>>> >> >>> >
>>> >> >>> > On Thu, Nov 17, 2011 at 5:05 AM, Ron M <ron...@gmail.com> wrote:
>>> >> >>> >> The VDI's resulted from these "make vdi-installer"  and  "make
>>> >> >>> >> android_disk_vdi" -
>>> >> >>> >> Result with a VM which does not have the "Machine->Disable Mouse
>>> >> >>> >> Integration"  (it is grayed out in the "Machine" menu).
>>> >> >>> >> Without enabling it - you cannot use mouse on Android-X86 - and
>>> >> >>> >> I
>>> >> >>> >> suspect
>>> >> >>> >> that the same thing applies to Google's   vbox_x86  target.
>>> >> >>> >>
>>> >> >>> >> That means we (assuming you have the same problem) can't use
>>> >> >>> >> mouse
>>> >> >>> >> within
>>> >> >>> >> the vbox ICS - which deems this configuration useless :-(
>>> >> >>> >> Anyone for the save?
>>> >> >>> >>
>>> >> >>> >>
>>> >> >>> >>
>>> >> >>> >> On Thu, Nov 17, 2011 at 12:49 PM, Ron M <ron...@gmail.com>
>>> >> >>> >> wrote:
>>> >> >>> >>>
>>> >> >>> >>> I was just curious about whether there is an "official" way.
>>> >> >>> >>> BUT - I am also experiencing the same problems you guys are -
>>> >> >>> >>> Can't
>>> >> >>> >>> see my
>>> >> >>> >>> mouse pointer!
>>> >> >>> >>> I think it is a system configuration issue thought, and has
>>> >> >>> >>> nothing to
>>> >> >>> >>> do
>>> >> >>> >>> with ICS - as the same problem happened to me on GIngerbread.
>>> >> >>> >>> Must be some Ubuntu 11.10/virtualbox 4.1.6/a combination of
>>> >> >>> >>> hard
>>> >> >>> >>> luck
>>> >> >>> >>>  stuff, as I was able to run X86-Android with mouse pointer
>>> >> >>> >>> support on
>>> >> >>> >>> another configuration in the past.
>>> >> >>> >>> What I do get, is launcher crashes. How about you guys?
>>> >> >>> >>>
>>> >> >>> >>> I'd be very happy to have someone from google responding in
>>> >> >>> >>> this
>>> >> >>> >>> thread.
>>> >> >>> >>> Otherwise I may assume that the vbox varient is just an
>>> >> >>> >>> unmaintained
>>> >> >>> >>> Hack,
>>> >> >>> >>> which would be quite sad-  as it is gzaillion times faster
>>> >> >>> >>> than the qemu builds.
>>> >> >>> >>> Ron
>>> >> >>> >>>
>>> >> >>> >>>
>>> >> >>> >>>
>>> >> >>> >>>
>>> >> >>> >>> On Thu, Nov 17, 2011 at 4:17 AM, Doug Schaefer
>>> >> >>> >>> <cdt...@gmail.com>
>>> >> >>> >>> wrote:
>>> >> >>> >>>>
>>> >> >>> >>>> That and there's no network access (reinstalled to get back to
>>> >> >>> >>>> the
>>> >> >>> >>>> home screen where keyboard navigation works).
>>> >> >>> >>>>
>>> >> >>> >>>> It's use is pretty limited. I think this turns into an
>>> >> >>> >>>> android-porting, or android-x86.org discussion pretty quickly.
>>> >> >>> >>>>
>>> >> >>> >>>> :D
>>> >> >>> >>>>
>>> >> >>> >>>> On Wed, Nov 16, 2011 at 8:30 PM, Nathaniel Husted
>>> >> >>> >>>> <nhu...@gmail.com>
>>> >> >>> >>>> wrote:
>>> >> >>> >>>> > I am currently having the exact same issue. I am in the
>>> >> >>> >>>> > middle
>>> >> >>> >>>> > of a
>>> >> >>> >>>> > development server rebuild so I will not be able to play
>>> >> >>> >>>> > around
>>> >> >>> >>>> > with
>>> >> >>> >>>> > Android and VirtualBox until tomorrow eve. However, if you
>>> >> >>> >>>> > happen
>>> >> >>> >>>> > to
>>> >> >>> >>>> > find a solution I will be most interested. I'm curious as it
>>> >> >>> >>>> > does
>>> >> >>> >>>> > not
>>> >> >>> >>>> > seem that the previous post I linked to earlier had the
>>> >> >>> >>>> > mouse
>>> >> >>> >>>> > issues.
>>> >> >>> >>>> > I'd love to know what step I have either conveniently left
>>> >> >>> >>>> > out
>>> >> >>> >>>> > or
>>> >> >>> >>>> > if
>>> >> >>> >>>> > there's something different about ICS when it comes to mouse
>>> >> >>> >>>> > interaction.
>>> >> >>> >>>> >
>>> >> >>> >>>> > Hopefully someone comes up with a solution for this one!
>>> >> >>> >>>> >
>>> >> >>> >>>> > Cheers,
>>> >> >>> >>>> > Nathaniel
>>> >> >>> >>>> >
>>> >> >>> >>>> > On Wed, Nov 16, 2011 at 8:23 PM, Doug Schaefer
>>> >> >>> >>>> > <cdt...@gmail.com>
>>> >> >>> >>>> > wrote:
>>> >> >>> >>>> >> A-ha, that did it. Now back to your original point. How do
>>> >> >>> >>>> >> I
>>> >> >>> >>>> >> get a
>>> >> >>> >>>> >> mouse pointer.
>>> >> >>> >>>> >>
>>> >> >>> >>>> >> One cool thing I saw on the first boot, it put me right
>>> >> >>> >>>> >> into
>>> >> >>> >>>> >> the
>>> >> >>> >>>> >> home
>>> >> >>> >>>> >> screen and I was able to use the keyboard to select things,
>>> >> >>> >>>> >> including
>>> >> >>> >>>> >> a very nice swap to another page that showed very
>>> >> >>> >>>> >> acceptable
>>> >> >>> >>>> >> graphics
>>> >> >>> >>>> >> performance. Now, just need to get a mouse pointer.
>>> >> >>> >>>> >>
>>> >> >>> >>>> >> :D
>>> >> >>> >>>> >>
>>> >> >>> >>>> >> On Wed, Nov 16, 2011 at 6:47 PM, Nathaniel Husted
>>> >> >>> >>>> >> <nhu...@gmail.com>
>>> >> >>> >>>> >> wrote:
>>> >> >>> >>>> >>> This is the closest thing I've found in the archive that
>>> >> >>> >>>> >>> discusses
>>> >> >>> >>>> >>> instructions for running the VirtualBox option. It appears
>>> >> >>> >>>> >>> that
>>> >> >>> >>>> >>> Android just will not function with SATA drives.
>>> >> >>> >>>> >>> Virtualbox
>>> >> >>> >>>> >>> MUST
>>> >> >>> >>>> >>> be
>>> >> >>> >>>> >>> set up with an IDE controller.
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>> Link:
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>> https://groups.google.com/group/android-building/browse_thread/thread/5053edfbcfe9f057/8c98f10a1537e49e?lnk=gst&q=vbox+x86#8c98f10a1537e49e
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>> Cheers,
>>> >> >>> >>>> >>> Nathaniel
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>> On Wed, Nov 16, 2011 at 4:45 PM, Mark Renouf
>>> >> >>> >>>> >>> <mre...@google.com>
>>> >> >>> >>>> >>> wrote:
>>> >> >>> >>>> >>>> Here's what I'm seeing. I tried both the "Install to"
>>> >> >>> >>>> >>>> option
>>> >> >>> >>>> >>>> and
>>> >> >>> >>>> >>>> the
>>> >> >>> >>>> >>>> "Boot
>>> >> >>> >>>> >>>> from" option.
>>> >> >>> >>>> >>>> "Install to" stops, waiting for a /dev/sdb2 (which
>>> >> >>> >>>> >>>> apparently
>>> >> >>> >>>> >>>> never
>>> >> >>> >>>> >>>> appears)
>>> >> >>> >>>> >>>> "Boot from" fails to boot fully because there is no
>>> >> >>> >>>> >>>> /system
>>> >> >>> >>>> >>>> partition
>>> >> >>> >>>> >>>> mounted (or so it seems).
>>> >> >>> >>>> >>>>
>>> >> >>> >>>> >>>> I've also included a screenshot of my VirtualBox
>>> >> >>> >>>> >>>> settings, I
>>> >> >>> >>>> >>>> believe
>>> >> >>> >>>> >>>> I have
>>> >> >>> >>>> >>>> these correct.
>>> >> >>> >>>> >>>>
>>> >> >>> >>>> >>>> I'm hoping somebody can figure this out :-)
>>> >> >>> >>>> >>>>
>>> >> >>> >>>> >>>> --
>>> >> >>> >>>> >>>> You received this message because you are subscribed to
>>> >> >>> >>>> >>>> the
>>> >> >>> >>>> >>>> "Android
>>> >> >>> >>>> >>>> Building" mailing list.
>>> >> >>> >>>> >>>> To post to this group, send email to
>>> >> >>> >>>> >>>> android-...@googlegroups.com
>>> >> >>> >>>> >>>> To unsubscribe from this group, send email to
>>> >> >>> >>>> >>>> android-buildi...@googlegroups.com
>>> >> >>> >>>> >>>> For more options, visit this group at
>>> >> >>> >>>> >>>> http://groups.google.com/group/android-building?hl=en
>>> >> >>> >>>> >>>>
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>> --
>>> >> >>> >>>> >>> You received this message because you are subscribed to
>>> >> >>> >>>> >>> the
>>> >> >>> >>>> >>> "Android
>>> >> >>> >>>> >>> Building" mailing list.
>>> >> >>> >>>> >>> To post to this group, send email to
>>> >> >>> >>>> >>> android-...@googlegroups.com
>>> >> >>> >>>> >>> To unsubscribe from this group, send email to
>>> >> >>> >>>> >>> android-buildi...@googlegroups.com
>>> >> >>> >>>> >>> For more options, visit this group at
>>> >> >>> >>>> >>> http://groups.google.com/group/android-building?hl=en
>>> >> >>> >>>> >>>
>>> >> >>> >>>> >>
>>> >> >>> >>>> >> --
>>> >> >>> >>>> >> You received this message because you are subscribed to the
>>> >> >>> >>>> >> "Android
>>> >> >>> >>>> >> Building" mailing list.
>>> >> >>> >>>> >> To post to this group, send email to
>>> >> >>> >>>> >> android-...@googlegroups.com
>>> >> >>> >>>> >> To unsubscribe from this group, send email to
>>> >> >>> >>>> >> android-buildi...@googlegroups.com
>>> >> >>> >>>> >> For more options, visit this group at
>>> >> >>> >>>> >> http://groups.google.com/group/android-building?hl=en
>>> >> >>> >>>> >>
>>> >> >>> >>>> >
>>> >> >>> >>>> > --
>>> >> >>> >>>> > You received this message because you are subscribed to the
>>> >> >>> >>>> > "Android
>>> >> >>> >>>> > Building" mailing list.
>>> >> >>> >>>> > To post to this group, send email to
>>> >> >>> >>>> > android-...@googlegroups.com
>>> >> >>> >>>> > To unsubscribe from this group, send email to
>>> >> >>> >>>> > android-buildi...@googlegroups.com
>>> >> >>> >>>> > For more options, visit this group at
>>> >> >>> >>>> > http://groups.google.com/group/android-building?hl=en
>>> >> >>> >>>> >
>>> >> >>> >>>>
>>> >> >>> >>>> --
>>> >> >>> >>>> You received this message because you are subscribed to the
>>> >> >>> >>>> "Android
>>> >> >>> >>>> Building" mailing list.
>>> >> >>> >>>> To post to this group, send email to
>>> >> >>> >>>> android-...@googlegroups.com
>>> >> >>> >>>> To unsubscribe from this group, send email to
>>> >> >>> >>>> android-buildi...@googlegroups.com
>>> >> >>> >>>> For more options, visit this group at
>>> >> >>> >>>> http://groups.google.com/group/android-building?hl=en
>>> >> >>> >>>
>>> >> >>> >>
>>> >> >>> >> --
>>> >> >>> >> You received this message because you are subscribed to the
>>> >> >>> >> "Android
>>> >> >>> >> Building" mailing list.
>>> >> >>> >> To post to this group, send email to
>>> >> >>> >> android-...@googlegroups.com
>>> >> >>> >> To unsubscribe from this group, send email to
>>> >> >>> >> android-buildi...@googlegroups.com
>>> >> >>> >> For more options, visit this group at
>>> >> >>> >> http://groups.google.com/group/android-building?hl=en
>>> >> >>> >>
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> > --
>>> >> >>> > Jean-Baptiste M. "JBQ" Queru
>>> >> >>> > Software Engineer, Android Open-Source Project, Google.
>>> >> >>> >
>>> >> >>> > Questions sent directly to me that have no reason for being
>>> >> >>> > private
>>> >> >>> > will likely get ignored or forwarded to a public forum with no
>>> >> >>> > further
>>> >> >>> > warning.
>>> >> >>> >
>>> >> >>> > --
>>> >> >>> > You received this message because you are subscribed to the
>>> >> >>> > "Android
>>> >> >>> > Building" mailing list.
>>> >> >>> > To post to this group, send email to
>>> >> >>> > android-...@googlegroups.com
>>> >> >>> > To unsubscribe from this group, send email to
>>> >> >>> > android-buildi...@googlegroups.com
>>> >> >>> > For more options, visit this group at
>>> >> >>> > http://groups.google.com/group/android-building?hl=en
>>> >> >>> >
>>> >> >>>
>>> >> >>> --
>>> >> >>> You received this message because you are subscribed to the
>>> >> >>> "Android
>>> >> >>> Building" mailing list.
>>> >> >>> To post to this group, send email to
>>> >> >>> android-...@googlegroups.com
>>> >> >>> To unsubscribe from this group, send email to
>>> >> >>> android-buildi...@googlegroups.com
>>> >> >>> For more options, visit this group at
>>> >> >>> http://groups.google.com/group/android-building?hl=en
>>> >> >>
>>> >> >> --
>>> >> >> You received this message because you are subscribed to the "Android
>>> >> >> Building" mailing list.
>>> >> >> To post to this group, send email to
>>> >> >> android-...@googlegroups.com
>>> >> >> To unsubscribe from this group, send email to
>>> >> >> android-buildi...@googlegroups.com
>>> >> >> For more options, visit this group at
>>> >> >> http://groups.google.com/group/android-building?hl=en
>>> >> >>
>>> >> >
>>> >> > --
>>> >> > You received this message because you are subscribed to the "Android
>>> >> > Building" mailing list.
>>> >> > To post to this group, send email to
>>> >> > android-...@googlegroups.com
>>> >> > To unsubscribe from this group, send email to
>>> >> > android-buildi...@googlegroups.com
>>> >> > For more options, visit this group at
>>> >> > http://groups.google.com/group/android-building?hl=en
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Jean-Baptiste M. "JBQ" Queru
>>> >> Software Engineer, Android Open-Source Project, Google.
>>> >>
>>> >> Questions sent directly to me that have no reason for being private
>>> >> will likely get ignored or forwarded to a public forum with no further
>>> >> warning.
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the "Android
>>> >> Building" mailing list.
>>> >> To post to this group, send email to android-...@googlegroups.com
>>> >> To unsubscribe from this group, send email to
>>> >> android-buildi...@googlegroups.com
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/android-building?hl=en
>>> >
>>> > --
>>> > You received this message because you are subscribed to the "Android
>>> > Building" mailing list.
>>> > To post to this group, send email to android-...@googlegroups.com
>>> > To unsubscribe from this group, send email to
>>> > android-buildi...@googlegroups.com
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/android-building?hl=en
>>> >
>>>
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-buildi...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>
>> --
>> You received this message because you are subscribed to the "Android
>> Building" mailing list.
>> To post to this group, send email to android-...@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-buildi...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>>
>
>
>
> --
> Jean-Baptiste M. "JBQ" Queru
> Software Engineer, Android Open-Source Project, Google.
>
> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.
>
> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

[Ron M]

What toolchain are you using? I tried to use the prebuilt from the AOSP master's, as I would in ARM compilation for the emulator - but it failed:

 ~/Android/ICS_Master/kernel/goldfish$ make ARCH=x86 CROSS_COMPILE=~/Android/ICS_Master/prebuilt/linux-x86/toolchain/i686-android-linux-4.4.3/bin/i686-android-linux- 2>&1 | tee BuildOut.log &

[1] 2624

   HOSTLD  scripts/kconfig/conf

scripts/kconfig/conf -s arch/x86/Kconfig

  CHK     include/linux/version.h

  CHK     include/linux/utsrelease.h

  SYMLINK include/asm -> include/asm-x86

  CC      kernel/bounds.s

kernel/bounds.c:1: warning: SSE instruction set disabled, using 387 arithmetics

  GEN     include/linux/bounds.h

  CC      arch/x86/kernel/asm-offsets.s

arch/x86/kernel/asm-offsets.c:1: warning: SSE instruction set disabled, using 387 arithmetics

  GEN     include/asm/asm-offsets.h

  CALL    scripts/checksyscalls.sh

cc1: warning: SSE instruction set disabled, using 387 arithmetics

  CC      scripts/mod/empty.o

scripts/mod/empty.c:1: warning: SSE instruction set disabled, using 387 arithmetics

  HOSTCC  scripts/mod/mk_elfconfig

  MKELF   scripts/mod/elfconfig.h

  HOSTCC  scripts/mod/file2alias.o

  HOSTCC  scripts/mod/modpost.o

scripts/mod/modpost.c: In function ‘get_markers’:

scripts/mod/modpost.c:1542:12: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result [-Wunused-result]

scripts/mod/modpost.c: In function ‘add_marker’:

scripts/mod/modpost.c:1962:10: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result [-Wunused-result]

  HOSTCC  scripts/mod/sumversion.o

  HOSTLD  scripts/mod/modpost

  HOSTCC  scripts/ihex2fw

scripts/ihex2fw.c: In function ‘output_records’:

scripts/ihex2fw.c:261:8: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]

scripts/ihex2fw.c:266:7: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]

  HOSTCC  scripts/kallsyms

scripts/kallsyms.c: In function ‘read_symbol’:

scripts/kallsyms.c:74:9: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result [-Wunused-result]

  HOSTCC  scripts/conmakehash

  CC      init/main.o

init/main.c:1: warning: SSE instruction set disabled, using 387 arithmetics

init/main.c: In function 'unknown_bootoption':

init/main.c:267: warning: asm operand 0 probably doesn't match constraints

init/main.c:267: error: impossible constraint in 'asm'

make[1]: *** [init/main.o] Error 1

make: *** [init] Error 2

[Daniel FAGES]

Hi Ron,

I think your problem is not due to your .config nor to Android.
It should be related to your version of gcc - according to https://bbs.archlinux.org/viewtopic.php?id=119341

You have 2 options :

- Use gcc <= 4.5

- Apply a patch to arch/x86/vdso/Makefile as explained at the bottom of the above URL

Regards,

Dan.

2011/11/20 Ron M <ron...@gmail.com>

--
unsubscribe: android-kerne...@googlegroups.com
website: http://groups.google.com/group/android-kernel

[Ron M]

This post is very old - but nothing has changes as far as AOSP is concerned, so  in case anyone is interested and runs into this problem when building for QEMU:

There is actually a nice and shorter way to build the kernel for your QEMU target provided by the AOSP:

1. cd to your kernel source dir (Only goldfish 2.6.29 works out of the box for the emulator)

2. ${ANDROID_BUILD_TOP}/external/qemu/distrib/build-kernel.sh -j=64 --arch=x86 --out=$YourOutDir

3. emulator -kernel ${YourOutDir}/kernel-qemu # run emulator:  

Step #2 calls the  toolbox.sh wrapper scripts which works around the SSE disabling gcc warning - which happens for GCC < 4.5 (as in the AOSP prebuilt X86 toolchain).

This script adds the   " -mfpmath=387 -fno-pic" in case it is an X86 and that in turn eliminates the compilation errors seen above.

To have finer control over the build process, you can use the "toolbox.sh" wrapper and set some other stuff without modifying the script files.

An example for building the same emulator is below:

# Set arch

export ARCH=x86

# Have make refer to the QEMU wrapper script for building android over x86 (eliminates the errors listed above)

export CROSS_COMPILE=${ANDROID_BUILD_TOP}/external/qemu/distrib/kernel-toolchain/android-kernel-toolchain-

# Put your cross compiler here. I am using the AOSP prebuilt one in this example

export REAL_CROSS_COMPILE=${ANDROID_BUILD_TOP}/prebuilt/linux-x86/toolchain/i686-android-linux-4.4.3/bin/i686-android-linux-

# Configure your kernel - here I am taking the default goldfish_defconfig

make goldfish_defconfig

# build

make -j64

# Run emulator:

emulator -kernel arch/x86/boot/bzImage -show-kernel

This works for the 2.6.29 goldfish branch. If anyone is using the emulator with a 3+ kernel I would be like to hear about it.