I too am using screen with multiple sessions and may have also lost my lunch ;)

Since nothing else breaks in the build, wouldn't this be something that should 
be fixed in the SE build? Or is there just some latent issue in the upstream 
build that this brought out?

----
Tom Palarz
Security Consultant
Neohapsis, Inc.
773-269-6300 x301
312-231-9834 m
773-394-8314 f
[email protected]<mailto:[email protected]>

www.neohapsis.com<http://www.neohapsis.com/>

The contents of this transmitted message are confidential and may be subject to 
privilege.  Disclosure, copying, distribution, or use of the contents of this 
transmission or information it contains is prohibited if you have received this 
transmission in error.  If you are not the named recipient, please immediately 
notify the sender and destroy all copies you have received.

From: Spencer Shimko [mailto:[email protected]]
Sent: Tuesday, April 09, 2013 6:01 PM
To: Tom Palarz
Cc: Stephen Smalley; [email protected]
Subject: Re: Seandroid 4.2.2 release repo sync error - bad merge?

On Tue, Apr 9, 2013 at 5:58 PM, Tom Palarz 
<[email protected]<mailto:[email protected]>> wrote:
<snip>/seandroid_4_2_2/system/extras/ext4_utils/make_ext4fs_main.c:142: 
undefined reference to `selinux_android_file_context_handle'

I used to get similar SELinux-specific ext4fs symbol errors when I forgot to 
lunch for the appropriate device.  I use screen sessions very heavily so it 
would pop up fairly regularly where, in one of the sessions, I would forget my 
lunch :)  My .bash_aliases file on my build system now runs lunch for my 
current target and it only introduces a few seconds lag during login with 
RAID'd SSDs.

FWIW I never figured out the exact cause.  I suspect it might be something to 
do with what is used and cached when building the host binaries vs. lunch'ing 
for a different target.  E.g. building for the x86 emulator first w/out SELinux 
which gens the host binaries, lunch'ing for a different target, then building 
again without a clobber/clean w/ a target w/ SELinux enabled.

Thanks,
--Spencer


----
Tom Palarz
Security Consultant
Neohapsis, Inc.
773-269-6300 x301<tel:773-269-6300%20x301>
312-231-9834<tel:312-231-9834> m
773-394-8314<tel:773-394-8314> f
[email protected]<mailto:[email protected]>

www.neohapsis.com<http://www.neohapsis.com>

The contents of this transmitted message are confidential and may be subject to 
privilege.  Disclosure, copying, distribution, or use of the contents of this 
transmission or information it contains is prohibited if you have received this 
transmission in error.  If you are not the named recipient, please immediately 
notify the sender and destroy all copies you have received.


-----Original Message-----
From: Stephen Smalley [mailto:[email protected]<mailto:[email protected]>]
Sent: Tuesday, April 09, 2013 2:56 PM
To: Tom Palarz
Cc: [email protected]<mailto:[email protected]>
Subject: Re: Seandroid 4.2.2 release repo sync error - bad merge?
On 04/09/2013 03:09 PM, Tom Palarz wrote:
> One other note. I'm not sure if this is just not supported, but I seem to 
> have a dependency issue when I do parallel make (-j 16 in this case). For 
> whatever reason, make_ext4fs seems to consistently fail when I do. Is there a 
> tweak needed to the appropriate Android.mk to fix that?

What output do you get from make?




--
This message was distributed to subscribers of the seandroid-list mailing list.
If you no longer wish to subscribe, send mail to 
[email protected]<mailto:[email protected]> with
the words "unsubscribe seandroid-list" without quotes as the message.

Reply via email to