Error with 'classes.dex' (missing and no known rule to make it.)

4,103 views
Skip to first unread message

DANiO

unread,
Mar 27, 2017, 12:33:11 AM3/27/17
to Android-x86
Hi, i'm here new and as topic says.

From 2 days I have a big error when I try to build android 7 x86 and there is error:
[...]
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp', needed by 'out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex', missing and no known rule to make it
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

#### make failed to build some targets (14:15 (mm:ss)) ####
and I tried to use
USE_NINJA=false
and over and over again... and also I tried to compile bliss x86 with my custom device tree (link).
Maybe this is due to pre-built apps in *.mk files?

I need a help, please!

PS: Sorry for the language!
---

Greetings!
Daniel K.

DANiO

unread,
Mar 28, 2017, 6:11:30 AM3/28/17
to Android-x86
no anyone help me?

Chih-Wei Huang

unread,
Mar 29, 2017, 1:40:10 AM3/29/17
to Android-x86
2017-03-28 0:36 GMT+08:00 DANiO <danio...@gmail.com>:
> no anyone help me?

The error should not happen.
Either your codebase was broken, or
you changed something to break it.

Try to make a clean build:
(on the top of android-x86 tree)

rm -rf out

or re-created your codebase:

rm -rf *
repo sync

(keep the .repo subdir so you won't need
to re-download everything)
--
Chih-Wei
Android-x86 project
http://www.android-x86.org

DANiO

unread,
Mar 29, 2017, 12:07:50 PM3/29/17
to Android-x86
and i tried on both sources android x86 7.1.1 and bliss x86 7.1.1 and error is the same.

DANiO

unread,
Mar 29, 2017, 12:07:58 PM3/29/17
to Android-x86
i tried with the first (with rm -rf out).... When I get home I will try the latter option.


W dniu środa, 29 marca 2017 07:40:10 UTC+2 użytkownik Chih-Wei Huang napisał:

DANiO

unread,
Mar 30, 2017, 9:42:30 PM3/30/17
to Android-x86
I installed a fresh debian 8 with openjdk-8 and error is similar to the last error....
log:
[...]
ninja: Entering directory `.'
ninja: error: '/mnt/serwer-sdc/windroid_7_x86/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp', needed by '/mnt/serwer-sdc/windroid_7_x86/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/src/core/java/android/accessibilityservice/IAccessibilityServiceConnection.java', missing and no known rule to make it
build/core/ninja.mk:152: polecenia dla obiektu 'ninja_wrapper' nie powiodły się
make: *** [ninja_wrapper] Błąd 1

#### make failed to build some targets (01:16:36 (hh:mm:ss)) ####

root@DANiO:/mnt/serwer-sdc/windroid_7_x86#



W dniu poniedziałek, 27 marca 2017 06:33:11 UTC+2 użytkownik DANiO napisał:

Chih-Wei Huang

unread,
Mar 30, 2017, 10:03:27 PM3/30/17
to Android-x86
2017-03-31 5:27 GMT+08:00 DANiO <danio...@gmail.com>:
> I installed a fresh debian 8 with openjdk-8 and error is similar to the last
> error....
> log:
> [...]
> ninja: Entering directory `.'
> ninja: error:
> '/mnt/serwer-sdc/windroid_7_x86/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp',
> needed by
> '/mnt/serwer-sdc/windroid_7_x86/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/src/core/java/android/accessibilityservice/IAccessibilityServiceConnection.java',
> missing and no known rule to make it
> build/core/ninja.mk:152: polecenia dla obiektu 'ninja_wrapper' nie powiodły
> się
> make: *** [ninja_wrapper] Błąd 1

Rules to build framework-res are defined in
frameworks/base/core/res/Android.mk

Do you have this file?

How did you build it exactly?

Try to add showcommands to get full build log
and post it somewhere.

DANiO

unread,
Mar 31, 2017, 1:41:24 PM3/31/17
to Android-x86
1. Yes, i have this file,
2. I try to build using this commands:
. build/envsetup.sh
lunch
WinDroid-userdebug
make
-j`nproc` iso_img
3. When I get home, I will send full logs.

DANiO

unread,
Mar 31, 2017, 1:41:24 PM3/31/17
to Android-x86
btw: maybe it's corrupted my custom device tree?
Can you check my device tree?
Maybe it will be as quick as you check it.


W dniu piątek, 31 marca 2017 04:03:27 UTC+2 użytkownik Chih-Wei Huang napisał:

DANiO

unread,
Apr 1, 2017, 12:16:38 AM4/1/17
to Android-x86
full log file.


W dniu piątek, 31 marca 2017 04:03:27 UTC+2 użytkownik Chih-Wei Huang napisał:
build.log

Chih-Wei Huang

unread,
Apr 1, 2017, 12:23:15 AM4/1/17
to Android-x86
2017-04-01 3:16 GMT+08:00 DANiO <danio...@gmail.com>:
> full log file.

First, don't post such a big file in the forum
Put it elsewhere.

Second, set your language to English,
otherwise most of us can't read.

Is it the full log?
I don't see any error except
the last failed message.

> W dniu piątek, 31 marca 2017 04:03:27 UTC+2 użytkownik Chih-Wei Huang
> napisał:
>>
>> 2017-03-31 5:27 GMT+08:00 DANiO <danio...@gmail.com>:
>> > I installed a fresh debian 8 with openjdk-8 and error is similar to the
>> > last
>> > error....
>> > log:
>> > [...]
>> > ninja: Entering directory `.'
>> > ninja: error:


D.D.

unread,
Apr 2, 2017, 3:03:20 AM4/2/17
to Android-x86
Well, I had the similar issue yesterday when trying to build the recent CM (absolutely clean build) on the latest Ubuntu (17.04 Zesty Zapus Beta 2). But in my case the message was about Gallery2_intermediates. I tried many things, for example:
- multiple calls of repo sync --no-tags --no-clone-bundle --force-sync command;
- switching between userdebug and eng variants;
- cleaning my out folder (rm -rf out);
- disabling and enabling ninja;
- syncing to official Android-x86 server and then syncing to CM;
- removing the entire folder of the app causing the issue.

Nothing helped! So I switched to Bliss-x86 and the error went away.

Anyway I'm wondering what's the exact origin of this error and how this could be fixed.

DANiO

unread,
Apr 4, 2017, 12:13:52 PM4/4/17
to Android-x86
ok, i rewrote all *.mk files and here is the result on screenshot
ss.png

DANiO

unread,
Apr 4, 2017, 12:13:52 PM4/4/17
to Android-x86
Do you use your own device tree?
If yes, you may have errors in this...
Helped me rewrite my custom device tree.

D.D.

unread,
Apr 4, 2017, 1:33:35 PM4/4/17
to Android-x86
DANiO

No, it was absolutely clean and unmodified. That's why it's kinda strange issue... Currently I gave up that CM and am sticking to Bliss.
Reply all
Reply to author
Forward
0 new messages