Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 353993 - dev-util/android-sdk-update-manager - SWT folder '//opt/android-sdk-update-manager/tools/lib/x86_64' does not exist
Summary: dev-util/android-sdk-update-manager - SWT folder '//opt/android-sdk-update-ma...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Richard Freeman
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-07 17:55 UTC by Bartosz Krzeszewski
Modified: 2011-02-12 14:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bartosz Krzeszewski 2011-02-07 17:55:02 UTC
After upgrading dev-util/android-sdk-update-manager-8-r2 [6-r2] when I run android command from console I get this error:
$ android 
SWT folder '//opt/android-sdk-update-manager/tools/lib/x86_64' does not exist.
Please export ANDROID_SWT to point to the folder containing swt.jar for your platform.

Reproducible: Always

Steps to Reproduce:
1. emerge =dev-util/android-sdk-update-manager-8-r2
2. run android as user
3. read error message
Comment 1 Richard Freeman gentoo-dev 2011-02-12 12:27:05 UTC
Did you run env-update and source /etc/profile in your shell before running android?  

I guess I can add a warning to the build that you need to do this the first time...

Try echo $ANDROID_SWT .
Comment 2 ProTech 2011-02-12 13:59:47 UTC
I run into the same problem testing the version 9 ebuild, as I see it's now working with the ebuild in portage. I needed to completely log out of GNOME and back in for the group and environment changes take effect. I also run a world update that might run an env-update.
Comment 3 Richard Freeman gentoo-dev 2011-02-12 14:41:44 UTC
Ok, I added a notice to the ebuild to source /etc/profile in any open shells if you get the error.  I'm not going to bump it for a notice.

If you run android from a shell after sourcing /etc/profile that should fix your problem.  You probably don't need to completely log out and in.  Of course, logging out and in will fix the problem.