Re: [android-building] Build sandboxing disabled due to nsjail error on lxc

['Dan Willemsen' via Android Building]

> 1. How fatal is it, do I need a machine running Ubuntu natively.

It's not fatal, the build should continue and work successfully. I know
that there are problems with docker-like systems (eventually tracking down
to some workarounds for a kernel bug -- turning off a lot of the security
helps, but doesn't get you all the way there), and there are problems with
systems that don't enable user namespaces (which means we'd need root ).
Between those problems it's likely not to become fatal anytime in the near
future, I should probably remove those messages from master.

Right now it's only giving us two benefits: (1) disabling networking for
the build and (2) preventing processes from staying alive after the build
exits (either normally, or on a failure). I'd like to do some more changes
(hiding / making visible different portions of the source tree, ensuring
that the current output directory is always out/, making the source tree
readonly, etc), but with enough people not being able to use it, we'll need
to find other ways to satisfy those goals.

2. If the build system is being containerized, can i just rub the build on
> my fedora machine and not care about build environment as much?
>

Yes, I'd expect that to work. Please let us know if you have any problems
doing that.

We're not fully containerizing, but we do include our own versions of most
of the tools that we use. The list of host tools that we're using is
shrinking, but bug reports would help us identify which ones should be
prioritized.

- Dan

On Mon, Dec 9, 2019 at 12:20 PM Sahaj Sarup  wrote:

> AOSP master.
>
> Getting the following warnings:
>
> 18:54:25 Build sandboxing disabled due to nsjail error. This may become
> fatal in the future.
> 18:54:25 Please let us know why nsjail doesn't work in your environment
> at:
> 18:54:25   https://groups.google.com/forum/#!forum/android-building
> 18:54:25   https://issuetracker.google.com/issues/new?component=381517
> 18:54:25 Build sandboxing disabled due to nsjail error. This may become
> fatal in the future.
> 18:54:25 Please let us know why nsjail doesn't work in your environment
> at:
> 18:54:25   https://groups.google.com/forum/#!forum/android-building
> 18:54:25   https://issuetracker.google.com/issues/new?component=381517
>
> My best guess is that since this _might_ be related to nsjail container
> and apparmour, these warnings appear because I am running ubuntu inside a
> lxc container.
>
> I have two questions regarding this:
>
> 1. How fatal is it, do I need a machine running Ubuntu natively.
> 2. If the build system is being containerized, can i just rub the build on
> my fedora machine and not care about build environment as much?
>
> --
> --
> 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+unsubscr...@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 Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/c2d1ec8a-d092-4731-9db9-ed9ca1708d56%40googlegroups.com
> 
> .
>

-- 
-- 
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+unsubscr...@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 Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CALQgHdn7nbOV62v6h_FB%3DW3CXxCtCkxC97-6fVJN87izPRt2vw%40mail.gmail.com.

[android-building] Build sandboxing disabled due to nsjail error on lxc

[Sahaj Sarup]

AOSP master. 
 
Getting the following warnings: 
 
18:54:25 Build sandboxing disabled due to nsjail error. This may become 
fatal in the future. 
18:54:25 Please let us know why nsjail doesn't work in your environment at: 
18:54:25   https://groups.google.com/forum/#!forum/android-building 
18:54:25   https://issuetracker.google.com/issues/new?component=381517 
18:54:25 Build sandboxing disabled due to nsjail error. This may become 
fatal in the future. 
18:54:25 Please let us know why nsjail doesn't work in your environment at: 
18:54:25   https://groups.google.com/forum/#!forum/android-building 
18:54:25   https://issuetracker.google.com/issues/new?component=381517 
 
My best guess is that since this _might_ be related to nsjail container and 
apparmour, these warnings appear because I am running ubuntu inside a lxc 
container. 
 
I have two questions regarding this: 
 
1. How fatal is it, do I need a machine running Ubuntu natively. 
2. If the build system is being containerized, can i just rub the build on 
my fedora machine and not care about build environment as much?

-- 
-- 
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+unsubscr...@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 Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/c2d1ec8a-d092-4731-9db9-ed9ca1708d56%40googlegroups.com.

[android-building] Re: Android Wear 9.0 released

['Bill Yi' via Android Building]

We pushed the kernel project for the following device:

Tag  Project Branch
  Device
android-wear-9.0.0_r0.35 kernel/msm  
android-msm-triggerfish-4.9-pie-wear-dr triggerfish

bill

-- 
-- 
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+unsubscr...@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 Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/fe844d39-445f-460a-a4ed-f6b59217af9b%40googlegroups.com.

[android-building] Re: Building Kernel for Pixel4 AOSP 10

[Peter Weir]

I have been doing some more comparisons between the the handbuilt kernel 
and the one that comes in the prebuilt.

The prebuilt one shows several modules in lsmod, 

Module  Size  Used by
ftm5  364544  0 
heatmap28672  2 ftm5
videobuf2_vmalloc  28672  1 heatmap
videobuf2_memops   24576  1 videobuf2_vmalloc
lkdtm  61440  0 
adsp_loader_dlkm   24576  0 
stub_dlkm  24576  1 
usf_dlkm   86016  0 
native_dlkm   233472  0 
machine_dlkm  229376  0 
platform_dlkm2588672  59 native_dlkm
wcd_cpe_dlkm  151552  0 
wsa881x_dlkm   73728  1 machine_dlkm
wcd934x_dlkm  503808  1 machine_dlkm
wcd9360_dlkm  348160  0 
mbhc_dlkm 102400  1 wcd934x_dlkm
wcd9xxx_dlkm  110592  2 wcd934x_dlkm,wcd9360_dlkm
swr_ctrl_dlkm  49152  2 wcd934x_dlkm,wcd9360_dlkm
cs35l36_dlkm  311296  2 
q6_dlkm  1318912  10 
usf_dlkm,native_dlkm,machine_dlkm,platform_dlkm,wcd_cpe_dlkm,wcd9xxx_dlkm,swr_ctrl_dlkm,cs35l36_dlkm
swr_dlkm   45056  2 wsa881x_dlkm,swr_ctrl_dlkm
apr_dlkm  253952  5 
adsp_loader_dlkm,usf_dlkm,platform_dlkm,wcd934x_dlkm,q6_dlkm
q6_notifier_dlkm   24576  3 machine_dlkm,q6_dlkm,apr_dlkm
q6_pdr_dlkm24576  1 q6_notifier_dlkm
wglink_dlkm32768  0 
wcd_spi_dlkm   40960  0 
wcd_core_dlkm 188416  6 
machine_dlkm,wcd_cpe_dlkm,wsa881x_dlkm,wcd934x_dlkm,wcd9360_dlkm,wcd9xxx_dlkm
pinctrl_wcd_dlkm   24576  0 
msm_11ad_proxy 45056  0 
wlan11649024  0

and the modules installed in /sys/module look like 

adreno   cam_context_utils cs35l36_dlkm   esoc_mdm_drv  
 hid_magicmouse l2tp_netlink   msm_drm  
 nf_conntrack_netbios_ns ppp_mppe random  snd_pcm  
 tcp_cubic  videobuf2_memops  workqueue
adsp_loader_dlkm cam_cpas_hw   debug_reboot   eud
i2c_algo_bit   l2tp_ppp   msm_performance   nf_conntrack_sane  
 printk   rcupdatesnd_timer ufshcd_core
videobuf2_v4l2wsa881x_dlkm 
apr_dlkm cam_csiphy_core   diagchar   event_timericnss  
libcomposite   msm_poweroff  nf_conntrack_tftp   pstore
   rcutree snd_usb_audio ufshcd_pltfrm  videobuf2_vmalloc 
xhci_hcd 
arm_smmu cam_debug_utildm_bufio   fb
 ip6_tunnel lkdtm  msm_show_resume_irq   oscar  
 q6_dlkm  rfkill  spidevuinput
 vmpressurexpad 
asix cam_ois_core  dm_mod firmware_class ipv6  
 lm36011_module msm_vidc_ar50_dyn_gov overheat_mitigation
 q6_notifier_dlkm rmnet_ipa   spurious  usb_bam
watchdog_v2   xt_quota2
battery  cam_smmu_api  dm_verity  fscrypto   kernel
 loop   msm_vidc_dyn_gov  overlay
 q6_pdr_dlkm  rndis   srcutree  usb_f_gsi  
wcd934x_dlkm  xz_dec   
binder   cdc_ncm   dns_resolver   ftm5   keydebug  
 lpm_levels native_dlkm   pac193x
 qcom_llcc_edac   rng_corest21nfc   usb_f_mtp  
wcd9360_dlkm  
binder_alloc cfg80211  drmfuse   kgsl  
 lpm_stats  nf_conntrack  pci_msm
 qmi_rmnetsch_htb stub_dlkm usb_storage
wcd9xxx_dlkm  
blockconfigfs  drm_kms_helper gasket kgsl_gmu  
 machine_dlkm   nf_conntrack_amanda   peripheral_loader  
 qpnp_power_onscsi_modsubsystem_restart usbcore
wcd_core_dlkm 
bluetoothcore_hang_detect  dummy  glink_pkt  l2tp_core  
mbhc_dlkm  nf_conntrack_ftp  phy_xgene   qpnp_rtc  
   service_locator suspend   usbhid wcd_cpe_dlkm  
bonding  cpufreq   dwc3   heatmapl2tp_eth  
 mhi_qcom   nf_conntrack_h323 pinctrl_wcd_dlkm
qpnp_smb5sg  swr_ctrl_dlkm usf_dlkm  
 wcd_spi_dlkm  
brd  cpuidle   dynamic_debug  hidl2tp_ip
module nf_conntrack_ipv4 platform_dlkm   r8152  
  sit swr_dlkm  v4l2_mem2mem   wglink_dlkm   
bridge   cryptomgr edac_core  hid_apple  l2tp_ip6  
 msm_11ad_proxy nf_conntrack_irc  ppp_generic ramoops  
snd sysrq videobuf2_core wlan   


On the one that I built 

lsmod looks like

lsmod
Module  Size  Used by
flame:/ $ 

and the built in drivers look like

adreno   bridgecore_hang_detect drm
firmware_class ip6_tunnel l2tp_netlink   msm_performance  
 

[android-building] Re: It is possible to build android 1.6 on ubuntu 18.04 ?

[Chang Kyo]

Dear Eliane:
If you still develop android 1.6,
I'll suggest that you can using docker or singularity to build container 
image which include ubuntu 10.04 + Java SDK 5 + android 1.6 require package.
After that, you can build android 1.6 using container on any version OS 
which support docker or singularity.
F.Y.I.

Eliane Fonseca於 2019年12月9日星期一 UTC+8上午8時29分22秒寫道：
>
> Has anyone built android 1.6 (donut) on ununtu 18.04 without any errors? I 
> am trying to build it, but  it probably doesn't support jdk 1.8
>

-- 
-- 
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+unsubscr...@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 Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/bd8240e8-fcff-46ce-9674-64ebd9162b40%40googlegroups.com.