-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile for arm-linux-gnueabihf? #26
Comments
I've solved this, it required a little more than a "make clean" since it didn't actually remove all the cruft. In the end I also changed to ARM_ARCH:=-march=armv6j -mtune=arm1136jf-s -mfpu=vfp -mfloat-abi=hard -marm |
oh, cool, do we also need to adapt the makefile? |
Hm. Shouldn't specifying CHOST on the make command line be enough? like e.g. $ make CHOST=arm-linux-gnueabihf That way, all subsequent definitions via ?= and := should be overridden, I BTW, we should identify what cruft is left by "make clean" - as that may |
It looked like thirdparty libs and luajit were not properly cleaned. Yes, specifying CHOST looks to be enough, but I don't think you can change to -mfloat-abi=hard by a command line switch, right? |
Yes, that may pose some problems, I guess. I'm not too sure, though. Isn't |
it is but in Makefile.defs it is specified: |
Oh, right. It probably won't run, no - unsure if it would even link... |
yeah, we can change ARM_ARCH according to environment. So if you think it's necessary, we should do so. btw, what command did you run to clean? |
Hi! since Kobo switched to armhf from armel in their latest firmware release, I'm trying to compile koreader for this architecture. I tried to simply modify Makefile.defs putting CHOST?=arm-linux-gnueabihf in it, but it looks like this setting is respected only partially since in the end the linker seems to complain that part of the binaries are for armhf and part of them are for armel (looks like thirdparty libraries are still built for armel). What else should I change?
The text was updated successfully, but these errors were encountered: