I just downloaded the Android source from the repo for the first time,
and now when I attempt to make it I get the following error. All the
tools I have are up to date as far as I know, and I followed the guide
here precisely.
Hi. I have not seen this error for myself, but it looks java related
error along with gcc. Not being able to find the 64 bit stub file
probably means you need to double check how many bits your platform
is. I've read that the new build requires java 1.6 and 64 bit. I know
itusually cried if you have the wrong version of java, but idk if it
checks for 64 if you do have 64 make sure you have the correct
version of gcc
On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote:
> I just downloaded the Android source from the repo for the first time,
> and now when I attempt to make it I get the following error. All the
> tools I have are up to date as far as I know, and I followed the guide
> here precisely.
Yes, the build system assumes you are building on a 64-bit host (maybe mistakenly, does other parts enforce a 64-bit environment?). I can make a fix, however, I can't verify it for I don't have a 32-bit host available.
On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
> Hi. I have not seen this error for myself, but it looks java related > error along with gcc. Not being able to find the 64 bit stub file > probably means you need to double check how many bits your platform > is. I've read that the new build requires java 1.6 and 64 bit. I know > itusually cried if you have the wrong version of java, but idk if it > checks for 64 if you do have 64 make sure you have the correct > version of gcc
> On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote: > > I just downloaded the Android source from the repo for the first time, > > and now when I attempt to make it I get the following error. All the > > tools I have are up to date as far as I know, and I followed the guide > > here precisely.
> -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
+# This forces a 64-bit build for Java6
+ifneq ($(filter 1.6%,$(java_version)),)
+ LOCAL_CFLAGS += -m64
+ LOCAL_LDFLAGS += -m64
+endif
+
(Logic: if Java 1.6 is installed, assume that the host is a 64-bit
machine)
Downgrading Java to 1.5 allows compilation to succeed for the generic-
eng / full-eng build. So, I think I can safely say that nothing else
enforces a 64-bit environment. If there was a 64-bit enforcement,
wouldn't it be enforced in build/core/main.mk?
Frank, where did you read that the new build requires a 64-bit host?
On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
> Yes, the build system assumes you are building on a 64-bit host (maybe
> mistakenly, does other parts enforce a 64-bit environment?).
> I can make a fix, however, I can't verify it for I don't have a 32-bit host
> available.
> On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
> > Hi. I have not seen this error for myself, but it looks java related
> > error along with gcc. Not being able to find the 64 bit stub file
> > probably means you need to double check how many bits your platform
> > is. I've read that the new build requires java 1.6 and 64 bit. I know
> > itusually cried if you have the wrong version of java, but idk if it
> > checks for 64 if you do have 64 make sure you have the correct
> > version of gcc
> > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote:
> > > I just downloaded the Android source from the repo for the first time,
> > > and now when I attempt to make it I get the following error. All the
> > > tools I have are up to date as far as I know, and I followed the guide
> > > here precisely.
> > --
> > You received this message because you are subscribed to the "Android
> > Building" mailing list.
> > To post to this group, send email to android-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
> Yes, the build system assumes you are building on a 64-bit host (maybe
> mistakenly, does other parts enforce a 64-bit environment?).
> I can make a fix, however, I can't verify it for I don't have a 32-bit host
> available.
> +# This forces a 64-bit build for Java6
> +ifneq ($(filter 1.6%,$(java_version)),)
> + LOCAL_CFLAGS += -m64
> + LOCAL_LDFLAGS += -m64
> +endif
> +
> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit
> machine)
> Downgrading Java to 1.5 allows compilation to succeed for the generic-
> eng / full-eng build. So, I think I can safely say that nothing else
> enforces a 64-bit environment. If there was a 64-bit enforcement,
> wouldn't it be enforced in build/core/main.mk?
> Frank, where did you read that the new build requires a 64-bit host?
> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
> > Yes, the build system assumes you are building on a 64-bit host (maybe
> > mistakenly, does other parts enforce a 64-bit environment?).
> > I can make a fix, however, I can't verify it for I don't have a 32-bit host
> > available.
> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
> > > Hi. I have not seen this error for myself, but it looks java related
> > > error along with gcc. Not being able to find the 64 bit stub file
> > > probably means you need to double check how many bits your platform
> > > is. I've read that the new build requires java 1.6 and 64 bit. I know
> > > itusually cried if you have the wrong version of java, but idk if it
> > > checks for 64 if you do have 64 make sure you have the correct
> > > version of gcc
> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote:
> > > > I just downloaded the Android source from the repo for the first time,
> > > > and now when I attempt to make it I get the following error. All the
> > > > tools I have are up to date as far as I know, and I followed the guide
> > > > here precisely.
> > > --
> > > You received this message because you are subscribed to the "Android
> > > Building" mailing list.
> > > To post to this group, send email to android-building@googlegroups.com
> > > To unsubscribe from this group, send email to
> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@googlegroups.com>
> > > For more options, visit this group at
> > >http://groups.google.com/group/android-building?hl=en
Sorry to but in but Java6 is available for 32 and 64 bit. There is no correlation between them that necessitates this. What would be the reason to force 64 bit?
On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote: > Joe said that the build now requires a 64 bit environment. > So maybe we have to stop supporting 32-bit build environment since > Java6?
>> +# This forces a 64-bit build for Java6 >> +ifneq ($(filter 1.6%,$(java_version)),) >> + LOCAL_CFLAGS += -m64 >> + LOCAL_LDFLAGS += -m64 >> +endif >> +
>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit >> machine)
>> Downgrading Java to 1.5 allows compilation to succeed for the generic- >> eng / full-eng build. So, I think I can safely say that nothing else >> enforces a 64-bit environment. If there was a 64-bit enforcement, >> wouldn't it be enforced in build/core/main.mk?
>> Frank, where did you read that the new build requires a 64-bit host?
>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
>> > Yes, the build system assumes you are building on a 64-bit host (maybe >> > mistakenly, does other parts enforce a 64-bit environment?). >> > I can make a fix, however, I can't verify it for I don't have a 32-bit host >> > available.
>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
>> > > Hi. I have not seen this error for myself, but it looks java related >> > > error along with gcc. Not being able to find the 64 bit stub file >> > > probably means you need to double check how many bits your platform >> > > is. I've read that the new build requires java 1.6 and 64 bit. I know >> > > itusually cried if you have the wrong version of java, but idk if it >> > > checks for 64 if you do have 64 make sure you have the correct >> > > version of gcc
>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote: >> > > > I just downloaded the Android source from the repo for the first time, >> > > > and now when I attempt to make it I get the following error. All the >> > > > tools I have are up to date as far as I know, and I followed the guide >> > > > here precisely.
>> > > -- >> > > You received this message because you are subscribed to the "Android >> > > Building" mailing list. >> > > To post to this group, send email to android-building@googlegroups.com >> > > To unsubscribe from this group, send email to >> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
Java6 is not available in 32-bit on all platforms.
Given that all of Google's development and testing happens on builds created on 64-bit machines, there's some level of risk in letting device manufacturers use 32-bit environments as we don't know what happens in those cases. Java6 allows us to standardize on 64-bit and eliminate that risk.
On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote: > Sorry to but in but Java6 is available for 32 and 64 bit. There is no > correlation between them that necessitates this. What would be the > reason to force 64 bit?
> On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote: >> Joe said that the build now requires a 64 bit environment. >> So maybe we have to stop supporting 32-bit build environment since >> Java6?
>>> +# This forces a 64-bit build for Java6 >>> +ifneq ($(filter 1.6%,$(java_version)),) >>> + LOCAL_CFLAGS += -m64 >>> + LOCAL_LDFLAGS += -m64 >>> +endif >>> +
>>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit >>> machine)
>>> Downgrading Java to 1.5 allows compilation to succeed for the generic- >>> eng / full-eng build. So, I think I can safely say that nothing else >>> enforces a 64-bit environment. If there was a 64-bit enforcement, >>> wouldn't it be enforced in build/core/main.mk?
>>> Frank, where did you read that the new build requires a 64-bit host?
>>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
>>> > Yes, the build system assumes you are building on a 64-bit host (maybe >>> > mistakenly, does other parts enforce a 64-bit environment?). >>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host >>> > available.
>>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
>>> > > Hi. I have not seen this error for myself, but it looks java related >>> > > error along with gcc. Not being able to find the 64 bit stub file >>> > > probably means you need to double check how many bits your platform >>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know >>> > > itusually cried if you have the wrong version of java, but idk if it >>> > > checks for 64 if you do have 64 make sure you have the correct >>> > > version of gcc
>>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote: >>> > > > I just downloaded the Android source from the repo for the first time, >>> > > > and now when I attempt to make it I get the following error. All the >>> > > > tools I have are up to date as far as I know, and I followed the guide >>> > > > here precisely.
>>> > > -- >>> > > You received this message because you are subscribed to the "Android >>> > > Building" mailing list. >>> > > To post to this group, send email to android-building@googlegroups.com >>> > > To unsubscribe from this group, send email to >>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com >> To unsubscribe from this group, send email to >> android-building+unsubscribe@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-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
On Wed, Jul 7, 2010 at 3:36 PM, Jean-Baptiste Queru <j...@android.com> wrote: > Java6 is not available in 32-bit on all platforms.
> Given that all of Google's development and testing happens on builds > created on 64-bit machines, there's some level of risk in letting > device manufacturers use 32-bit environments as we don't know what > happens in those cases. Java6 allows us to standardize on 64-bit and > eliminate that risk.
> JBQ
> On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote: >> Sorry to but in but Java6 is available for 32 and 64 bit. There is no >> correlation between them that necessitates this. What would be the >> reason to force 64 bit?
>> On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote: >>> Joe said that the build now requires a 64 bit environment. >>> So maybe we have to stop supporting 32-bit build environment since >>> Java6?
>>>> +# This forces a 64-bit build for Java6 >>>> +ifneq ($(filter 1.6%,$(java_version)),) >>>> + LOCAL_CFLAGS += -m64 >>>> + LOCAL_LDFLAGS += -m64 >>>> +endif >>>> +
>>>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit >>>> machine)
>>>> Downgrading Java to 1.5 allows compilation to succeed for the generic- >>>> eng / full-eng build. So, I think I can safely say that nothing else >>>> enforces a 64-bit environment. If there was a 64-bit enforcement, >>>> wouldn't it be enforced in build/core/main.mk?
>>>> Frank, where did you read that the new build requires a 64-bit host?
>>>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
>>>> > Yes, the build system assumes you are building on a 64-bit host (maybe >>>> > mistakenly, does other parts enforce a 64-bit environment?). >>>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host >>>> > available.
>>>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
>>>> > > Hi. I have not seen this error for myself, but it looks java related >>>> > > error along with gcc. Not being able to find the 64 bit stub file >>>> > > probably means you need to double check how many bits your platform >>>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know >>>> > > itusually cried if you have the wrong version of java, but idk if it >>>> > > checks for 64 if you do have 64 make sure you have the correct >>>> > > version of gcc
>>>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote: >>>> > > > I just downloaded the Android source from the repo for the first time, >>>> > > > and now when I attempt to make it I get the following error. All the >>>> > > > tools I have are up to date as far as I know, and I followed the guide >>>> > > > here precisely.
>>>> > > -- >>>> > > You received this message because you are subscribed to the "Android >>>> > > Building" mailing list. >>>> > > To post to this group, send email to android-building@googlegroups.com >>>> > > To unsubscribe from this group, send email to >>>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com >>> To unsubscribe from this group, send email to >>> android-building+unsubscribe@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-building@googlegroups.com >> To unsubscribe from this group, send email to >> android-building+unsubscribe@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en
> 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-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> Java6 is not available in 32-bit on all platforms.
> Given that all of Google's development and testing happens on builds
> created on 64-bit machines, there's some level of risk in letting
> device manufacturers use 32-bit environments as we don't know what
> happens in those cases. Java6 allows us to standardize on 64-bit and
> eliminate that risk.
> JBQ
> On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote:
> > Sorry to but in but Java6 is available for 32 and 64 bit. There is no
> > correlation between them that necessitates this. What would be the
> > reason to force 64 bit?
> > On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote:
> >> Joe said that the build now requires a 64 bit environment.
> >> So maybe we have to stop supporting 32-bit build environment since
> >> Java6?
> >>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit
> >>> machine)
> >>> Downgrading Java to 1.5 allows compilation to succeed for the generic-
> >>> eng / full-eng build. So, I think I can safely say that nothing else
> >>> enforces a 64-bit environment. If there was a 64-bit enforcement,
> >>> wouldn't it be enforced in build/core/main.mk?
> >>> Frank, where did you read that the new build requires a 64-bit host?
> >>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
> >>> > Yes, the build system assumes you are building on a 64-bit host (maybe
> >>> > mistakenly, does other parts enforce a 64-bit environment?).
> >>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host
> >>> > available.
> >>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
> >>> > > Hi. I have not seen this error for myself, but it looks java related
> >>> > > error along with gcc. Not being able to find the 64 bit stub file
> >>> > > probably means you need to double check how many bits your platform
> >>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know
> >>> > > itusually cried if you have the wrong version of java, but idk if it
> >>> > > checks for 64 if you do have 64 make sure you have the correct
> >>> > > version of gcc
> >>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote:
> >>> > > > I just downloaded the Android source from the repo for the first time,
> >>> > > > and now when I attempt to make it I get the following error. All the
> >>> > > > tools I have are up to date as far as I know, and I followed the guide
> >>> > > > here precisely.
> >>> > > --
> >>> > > You received this message because you are subscribed to the "Android
> >>> > > Building" mailing list.
> >>> > > To post to this group, send email to android-building@googlegroups.com
> >>> > > To unsubscribe from this group, send email to
> >>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com
> >> To unsubscribe from this group, send email to
> >> android-building+unsubscribe@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-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> 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.
So let's enforce a 64-bit build environment?
Just like what have enforced Java6, check if the host is 64-bit system
before doing any build.
I will be happy to make the change.. :-)
On Jul 7, 3:36 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Java6 is not available in 32-bit on all platforms.
> Given that all of Google's development and testing happens on builds
> created on 64-bit machines, there's some level of risk in letting
> device manufacturers use 32-bit environments as we don't know what
> happens in those cases. Java6 allows us to standardize on 64-bit and
> eliminate that risk.
> JBQ
> On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote:
> > Sorry to but in but Java6 is available for 32 and 64 bit. There is no
> > correlation between them that necessitates this. What would be the
> > reason to force 64 bit?
> > On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote:
> >> Joe said that the build now requires a 64 bit environment.
> >> So maybe we have to stop supporting 32-bit build environment since
> >> Java6?
> >>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit
> >>> machine)
> >>> Downgrading Java to 1.5 allows compilation to succeed for the generic-
> >>> eng / full-eng build. So, I think I can safely say that nothing else
> >>> enforces a 64-bit environment. If there was a 64-bit enforcement,
> >>> wouldn't it be enforced in build/core/main.mk?
> >>> Frank, where did you read that the new build requires a 64-bit host?
> >>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
> >>> > Yes, the build system assumes you are building on a 64-bit host (maybe
> >>> > mistakenly, does other parts enforce a 64-bit environment?).
> >>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host
> >>> > available.
> >>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
> >>> > > Hi. I have not seen this error for myself, but it looks java related
> >>> > > error along with gcc. Not being able to find the 64 bit stub file
> >>> > > probably means you need to double check how many bits your platform
> >>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know
> >>> > > itusually cried if you have the wrong version of java, but idk if it
> >>> > > checks for 64 if you do have 64 make sure you have the correct
> >>> > > version of gcc
> >>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote:
> >>> > > > I just downloaded the Android source from the repo for the first time,
> >>> > > > and now when I attempt to make it I get the following error. All the
> >>> > > > tools I have are up to date as far as I know, and I followed the guide
> >>> > > > here precisely.
> >>> > > --
> >>> > > You received this message because you are subscribed to the "Android
> >>> > > Building" mailing list.
> >>> > > To post to this group, send email to android-building@googlegroups.com
> >>> > > To unsubscribe from this group, send email to
> >>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com
> >> To unsubscribe from this group, send email to
> >> android-building+unsubscribe@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-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> 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.
On 7 Jul 2010, at 23:36, Jean-Baptiste Queru wrote:
> Java6 is not available in 32-bit on all platforms.
> Given that all of Google's development and testing happens on builds > created on 64-bit machines, there's some level of risk in letting > device manufacturers use 32-bit environments as we don't know what > happens in those cases. Java6 allows us to standardize on 64-bit and > eliminate that risk.
Ah! So, that explains the problem I'm getting with the libz.so as well. I'm trying to build on a 32bits Ubuntu.
> 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-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
But for platforms that have 32-bit java6? Just let the compile fail?
A warning about untested 32-bit builds would be sufficient enough.
Forcing 32/64 compiles without any documentation or printouts of
warnings is not a very flexible way to code IMO.
There needs to be more data to suggest that it is mandatory
On Jul 8, 7:34 am, Tiago Vieira <ti...@tvieira.com> wrote:
> On 7 Jul 2010, at 23:36, Jean-Baptiste Queru wrote:
> > Java6 is not available in 32-bit on all platforms.
> > Given that all of Google's development and testing happens on builds
> > created on 64-bit machines, there's some level of risk in letting
> > device manufacturers use 32-bit environments as we don't know what
> > happens in those cases. Java6 allows us to standardize on 64-bit and
> > eliminate that risk.
> Ah! So, that explains the problem I'm getting with the libz.so as well. I'm trying to build on a 32bits Ubuntu.
> > 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-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
manningr@dell-devpc:~/mydroid-2.2_r1.1$ uname -a
Linux dell-devpc 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 02:41:03
UTC 2010 x86_64 GNU/Linux
manningr@dell-devpc:~/mydroid-2.2_r1.1$ repo init -u
git://android.git.kernel.org/platform/manifest.git -b android-2.2_r1.1
<snip>
manningr@dell-devpc:~/mydroid-2.2_r1.1$ mm sdk
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.2
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=FRF91
============================================
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of java.
Your version is: java version "1.6.0_14".
The correct version is: 1.5.
Please follow the machine setup instructions at
http://source.android.com/download ************************************************************
build/core/main.mk:117: *** stop. Stop.
On Jul 7, 6:36 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Java6 is not available in 32-bit on all platforms.
> Given that all of Google's development and testing happens on builds
> created on 64-bit machines, there's some level of risk in letting
> device manufacturers use 32-bit environments as we don't know what
> happens in those cases. Java6 allows us to standardize on 64-bit and
> eliminate that risk.
> JBQ
> On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote:
> > Sorry to but in but Java6 is available for 32 and 64 bit. There is no
> > correlation between them that necessitates this. What would be the
> > reason to force 64 bit?
> > On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote:
> >> Joe said that the build now requires a 64 bit environment.
> >> So maybe we have to stop supporting 32-bit build environment since
> >> Java6?
> >>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit
> >>> machine)
> >>> Downgrading Java to 1.5 allows compilation to succeed for the generic-
> >>> eng / full-eng build. So, I think I can safely say that nothing else
> >>> enforces a 64-bit environment. If there was a 64-bit enforcement,
> >>> wouldn't it be enforced in build/core/main.mk?
> >>> Frank, where did you read that the new build requires a 64-bit host?
> >>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
> >>> > Yes, the build system assumes you are building on a 64-bit host (maybe
> >>> > mistakenly, does other parts enforce a 64-bit environment?).
> >>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host
> >>> > available.
> >>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
> >>> > > Hi. I have not seen this error for myself, but it looks java related
> >>> > > error along with gcc. Not being able to find the 64 bit stub file
> >>> > > probably means you need to double check how many bits your platform
> >>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know
> >>> > > itusually cried if you have the wrong version of java, but idk if it
> >>> > > checks for 64 if you do have 64 make sure you have the correct
> >>> > > version of gcc
> >>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote:
> >>> > > > I just downloaded the Android source from the repo for the first time,
> >>> > > > and now when I attempt to make it I get the following error. All the
> >>> > > > tools I have are up to date as far as I know, and I followed the guide
> >>> > > > here precisely.
> >>> > > --
> >>> > > You received this message because you are subscribed to the "Android
> >>> > > Building" mailing list.
> >>> > > To post to this group, send email to android-building@googlegroups.com
> >>> > > To unsubscribe from this group, send email to
> >>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com
> >> To unsubscribe from this group, send email to
> >> android-building+unsubscribe@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-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> 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.
<robert.m.mann...@gmail.com> wrote: > Hmmm.... Did I miss something ?
> manningr@dell-devpc:~/mydroid-2.2_r1.1$ uname -a > Linux dell-devpc 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 02:41:03 > UTC 2010 x86_64 GNU/Linux > manningr@dell-devpc:~/mydroid-2.2_r1.1$ repo init -u > git://android.git.kernel.org/platform/manifest.git -b android-2.2_r1.1
> <snip>
> manningr@dell-devpc:~/mydroid-2.2_r1.1$ mm sdk > ============================================ > PLATFORM_VERSION_CODENAME=REL > PLATFORM_VERSION=2.2 > TARGET_PRODUCT=generic > TARGET_BUILD_VARIANT=eng > TARGET_SIMULATOR= > TARGET_BUILD_TYPE=release > TARGET_BUILD_APPS= > TARGET_ARCH=arm > HOST_ARCH=x86 > HOST_OS=linux > HOST_BUILD_TYPE=release > BUILD_ID=FRF91 > ============================================ > Checking build tools versions... > ************************************************************ > You are attempting to build with the incorrect version > of java.
> Your version is: java version "1.6.0_14". > The correct version is: 1.5.
> Please follow the machine setup instructions at > http://source.android.com/download > ************************************************************ > build/core/main.mk:117: *** stop. Stop.
> On Jul 7, 6:36 pm, Jean-Baptiste Queru <j...@android.com> wrote: >> Java6 is not available in 32-bit on all platforms.
>> Given that all of Google's development and testing happens on builds >> created on 64-bit machines, there's some level of risk in letting >> device manufacturers use 32-bit environments as we don't know what >> happens in those cases. Java6 allows us to standardize on 64-bit and >> eliminate that risk.
>> JBQ
>> On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote: >> > Sorry to but in but Java6 is available for 32 and 64 bit. There is no >> > correlation between them that necessitates this. What would be the >> > reason to force 64 bit?
>> > On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote: >> >> Joe said that the build now requires a 64 bit environment. >> >> So maybe we have to stop supporting 32-bit build environment since >> >> Java6?
>> >>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit >> >>> machine)
>> >>> Downgrading Java to 1.5 allows compilation to succeed for the generic- >> >>> eng / full-eng build. So, I think I can safely say that nothing else >> >>> enforces a 64-bit environment. If there was a 64-bit enforcement, >> >>> wouldn't it be enforced in build/core/main.mk?
>> >>> Frank, where did you read that the new build requires a 64-bit host?
>> >>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
>> >>> > Yes, the build system assumes you are building on a 64-bit host (maybe >> >>> > mistakenly, does other parts enforce a 64-bit environment?). >> >>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host >> >>> > available.
>> >>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
>> >>> > > Hi. I have not seen this error for myself, but it looks java related >> >>> > > error along with gcc. Not being able to find the 64 bit stub file >> >>> > > probably means you need to double check how many bits your platform >> >>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know >> >>> > > itusually cried if you have the wrong version of java, but idk if it >> >>> > > checks for 64 if you do have 64 make sure you have the correct >> >>> > > version of gcc
>> >>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote: >> >>> > > > I just downloaded the Android source from the repo for the first time, >> >>> > > > and now when I attempt to make it I get the following error. All the >> >>> > > > tools I have are up to date as far as I know, and I followed the guide >> >>> > > > here precisely.
>> >>> > > -- >> >>> > > You received this message because you are subscribed to the "Android >> >>> > > Building" mailing list. >> >>> > > To post to this group, send email to android-building@googlegroups.com >> >>> > > To unsubscribe from this group, send email to >> >>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com >> >> To unsubscribe from this group, send email to >> >> android-building+unsubscribe@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-building@googlegroups.com >> > To unsubscribe from this group, send email to >> > android-building+unsubscribe@googlegroups.com >> > For more options, visit this group at >> >http://groups.google.com/group/android-building?hl=en
>> 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-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
> > On Jul 7, 6:36 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> >> Java6 is not available in 32-bit on all platforms.
> >> Given that all of Google's development and testing happens on builds
> >> created on 64-bit machines, there's some level of risk in letting
> >> device manufacturers use 32-bit environments as we don't know what
> >> happens in those cases. Java6 allows us to standardize on 64-bit and
> >> eliminate that risk.
> >> JBQ
> >> On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote:
> >> > Sorry to but in but Java6 is available for 32 and 64 bit. There is no
> >> > correlation between them that necessitates this. What would be the
> >> > reason to force 64 bit?
> >> > On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote:
> >> >> Joe said that the build now requires a 64 bit environment.
> >> >> So maybe we have to stop supporting 32-bit build environment since
> >> >> Java6?
> >> >>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit
> >> >>> machine)
> >> >>> Downgrading Java to 1.5 allows compilation to succeed for the generic-
> >> >>> eng / full-eng build. So, I think I can safely say that nothing else
> >> >>> enforces a 64-bit environment. If there was a 64-bit enforcement,
> >> >>> wouldn't it be enforced in build/core/main.mk?
> >> >>> Frank, where did you read that the new build requires a 64-bit host?
> >> >>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
> >> >>> > Yes, the build system assumes you are building on a 64-bit host (maybe
> >> >>> > mistakenly, does other parts enforce a 64-bit environment?).
> >> >>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host
> >> >>> > available.
> >> >>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
> >> >>> > > Hi. I have not seen this error for myself, but it looks java related
> >> >>> > > error along with gcc. Not being able to find the 64 bit stub file
> >> >>> > > probably means you need to double check how many bits your platform
> >> >>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know
> >> >>> > > itusually cried if you have the wrong version of java, but idk if it
> >> >>> > > checks for 64 if you do have 64 make sure you have the correct
> >> >>> > > version of gcc
> >> >>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote:
> >> >>> > > > I just downloaded the Android source from the repo for the first time,
> >> >>> > > > and now when I attempt to make it I get the following error. All the
> >> >>> > > > tools I have are up to date as far as I know, and I followed the guide
> >> >>> > > > here precisely.
> >> >>> > > --
> >> >>> > > You received this message because you are subscribed to the "Android
> >> >>> > > Building" mailing list.
> >> >>> > > To post to this group, send email to android-building@googlegroups.com
> >> >>> > > To unsubscribe from this group, send email to
> >> >>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com
> >> >> To unsubscribe from this group, send email to
> >> >> android-building+unsubscribe@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-building@googlegroups.com
> >> > To unsubscribe from this group, send email to
> >> > android-building+unsubscribe@googlegroups.com
> >> > For more options, visit this group at
> >> >http://groups.google.com/group/android-building?hl=en
> >> 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-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> 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.
All the open-source codelines that mirror Google's internal froyo branches (i.e. froyo and the various android-2.2) use 1.5 like Google's matching internal codelines do, since that is the version that Google developed and tested with through the entire froyo development cycle.
We backported the changes to switch to version 1.6 (64-bit) from our internal master branch to the open-source master just as we switched our internal master branch to 1.6, since from that point there was no requirement for contributions to the open-source master branch to build under 1.5 any more.
JBQ
On Fri, Jul 9, 2010 at 6:56 PM, Robert.M.Mann...@gmail.com
>> > On Jul 7, 6:36 pm, Jean-Baptiste Queru <j...@android.com> wrote: >> >> Java6 is not available in 32-bit on all platforms.
>> >> Given that all of Google's development and testing happens on builds >> >> created on 64-bit machines, there's some level of risk in letting >> >> device manufacturers use 32-bit environments as we don't know what >> >> happens in those cases. Java6 allows us to standardize on 64-bit and >> >> eliminate that risk.
>> >> JBQ
>> >> On Wed, Jul 7, 2010 at 3:31 PM, Manfred Moser <mosa...@gmail.com> wrote: >> >> > Sorry to but in but Java6 is available for 32 and 64 bit. There is no >> >> > correlation between them that necessitates this. What would be the >> >> > reason to force 64 bit?
>> >> > On Wed, Jul 7, 2010 at 3:07 PM, Ying Wang <wangy...@android.com> wrote: >> >> >> Joe said that the build now requires a 64 bit environment. >> >> >> So maybe we have to stop supporting 32-bit build environment since >> >> >> Java6?
>> >> >>> (Logic: if Java 1.6 is installed, assume that the host is a 64-bit >> >> >>> machine)
>> >> >>> Downgrading Java to 1.5 allows compilation to succeed for the generic- >> >> >>> eng / full-eng build. So, I think I can safely say that nothing else >> >> >>> enforces a 64-bit environment. If there was a 64-bit enforcement, >> >> >>> wouldn't it be enforced in build/core/main.mk?
>> >> >>> Frank, where did you read that the new build requires a 64-bit host?
>> >> >>> On Jul 7, 11:50 am, Ying Wang <wangy...@android.com> wrote:
>> >> >>> > Yes, the build system assumes you are building on a 64-bit host (maybe >> >> >>> > mistakenly, does other parts enforce a 64-bit environment?). >> >> >>> > I can make a fix, however, I can't verify it for I don't have a 32-bit host >> >> >>> > available.
>> >> >>> > On Wed, Jul 7, 2010 at 11:39 AM, frank.sposaro <frank.spos...@gmail.com>wrote:
>> >> >>> > > Hi. I have not seen this error for myself, but it looks java related >> >> >>> > > error along with gcc. Not being able to find the 64 bit stub file >> >> >>> > > probably means you need to double check how many bits your platform >> >> >>> > > is. I've read that the new build requires java 1.6 and 64 bit. I know >> >> >>> > > itusually cried if you have the wrong version of java, but idk if it >> >> >>> > > checks for 64 if you do have 64 make sure you have the correct >> >> >>> > > version of gcc
>> >> >>> > > On Jul 6, 9:58 am, Rudster816 <rudster...@gmail.com> wrote: >> >> >>> > > > I just downloaded the Android source from the repo for the first time, >> >> >>> > > > and now when I attempt to make it I get the following error. All the >> >> >>> > > > tools I have are up to date as far as I know, and I followed the guide >> >> >>> > > > here precisely.
>> >> >>> > > -- >> >> >>> > > You received this message because you are subscribed to the "Android >> >> >>> > > Building" mailing list. >> >> >>> > > To post to this group, send email to android-building@googlegroups.com >> >> >>> > > To unsubscribe from this group, send email to >> >> >>> > > android-building+unsubscribe@googlegroups.com<android-building%2Bunsubscrib e@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-building@googlegroups.com >> >> >> To unsubscribe from this group, send email to >> >> >> android-building+unsubscribe@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-building@googlegroups.com >> >> > To unsubscribe from this group, send email to >> >> > android-building+unsubscribe@googlegroups.com >> >> > For more options, visit this group at >> >> >http://groups.google.com/group/android-building?hl=en
>> >> 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-building@googlegroups.com >> > To unsubscribe from this group, send email to >> > android-building+unsubscribe@googlegroups.com >> > For more options, visit this group at >> >http://groups.google.com/group/android-building?hl=en
>> 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-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
So, I'm probably not getting what's going on here, but how does this
work out for building ARM code? Seems compiling things like external/
clearsilver/java-jni/j_neo_cs.c, which uses jlongs for pointers, could
be rough.
The code in question is purely host-side (i.e. x86_64). Target-side aspects are unchanged.
JBQ
On Mon, Jul 12, 2010 at 11:00 AM, mrie...@nii.net <mrie...@nii.net> wrote: > So, I'm probably not getting what's going on here, but how does this > work out for building ARM code? Seems compiling things like external/ > clearsilver/java-jni/j_neo_cs.c, which uses jlongs for pointers, could > be rough.
> -- > You received this message because you are subscribed to the "Android Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
If it is of interest to anyone, simply commenting out the many:
+# This forces a 64-bit build for Java6
+ifneq ($(filter 1.6%,$(java_version)),)
+ LOCAL_CFLAGS += -m64
+ LOCAL_LDFLAGS += -m64
+endif
blocks lets it build just fine on a 32-bit system (at least the
emulator seems to run ok).
Sun does have a Java 1.6 for 32-bit systems (jdk-6u21-linux-i586.bin).
Mike
I have posted about this patch as well, but have not gotten any feedback from the maintainers about it that much. It seems very plausible to allow a check for 32bit and issue a warning about "possible" irregularities in doing a 32bit build. This patch seems very constrictive to me.
[mailto:android-building@googlegroups.com] On Behalf Of mrie...@nii.net Sent: Tuesday, July 13, 2010 8:23 AM To: Android Building Subject: [android-building] Re: Build Error during Make
If it is of interest to anyone, simply commenting out the many:
+# This forces a 64-bit build for Java6 +ifneq ($(filter 1.6%,$(java_version)),) + LOCAL_CFLAGS += -m64 + LOCAL_LDFLAGS += -m64 +endif
blocks lets it build just fine on a 32-bit system (at least the emulator seems to run ok). Sun does have a Java 1.6 for 32-bit systems (jdk-6u21-linux-i586.bin). Mike
-- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en
As far as I know there are still some issues (which may or may not be related to the version of XCode used locally), but the switch to JDK 1.6 should remove one of the hurdles.
JBQ
On Thu, Jul 29, 2010 at 2:55 PM, Chris C. <ccfl...@gmail.com> wrote: > So, does this mean that development under Snow Leopard will now become > supported with the addition of Java 6?
> Chris
> -- > You received this message because you are subscribed to the "Android Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en
I know, its not supported to build with Snow Leopard. I just wanted to
let you know that I did successfully built master (as of some hours
ago) with my MacBook running Snow Leopard (64bit).
At first glance it looks the same as the Ubuntu (32bit) build. Wifi
and GSM are working
Dirk
On Jul 29, 11:59 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> As far as I know there are still some issues (which may or may not be
> related to the version of XCode used locally), but the switch to JDK
> 1.6 should remove one of the hurdles.
> JBQ
> On Thu, Jul 29, 2010 at 2:55 PM, Chris C. <ccfl...@gmail.com> wrote:
> > So, does this mean that development under Snow Leopard will now become
> > supported with the addition of Java 6?
> > Chris
> > --
> > You received this message because you are subscribed to the "Android Building" mailing list.
> > To post to this group, send email to android-building@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-building?hl=en
> 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.
