-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ERROR: no readelf found #138
Comments
It seems you are not on a Debian x86 VM, please check the requirements to spksrc. |
it seems readelf is missing in
if i add readelf to
the file exists:
but i've got the error again:
any ideas? |
next try: if i remove
but |
http://en.wikipedia.org/wiki/Executable_and_Linkable_Format "Unlike many proprietary executable file formats, ELF is flexible and extensible, and it is not bound to any particular processor or architecture." Have you installed build-essentials on your Debian ? I think readelf is part of it. |
yes, you are right! but this could only a work-around, because the toolchain contains a readelf, which should be used. |
What are you trying to compile so I give it a shot? |
maybe the hardest software to cross-compile: perl :-) i can compile it in my own environment. actually i use perl-5.14.2 with perlcross from berlios. the following script works for me and i want to switch to spksrc as a new environment.
my extended miniperl_top:
|
as i wrote before: when but it fails on new erros:
and so on...
all described errors in this issue does not occur in my environment. at the moment i'm at the end of the road :-( |
Well I don't know why the configure script doesn't pick the good one but really that's no big deal. Maybe look into the script and hack some stuff or find a way to pass the good variable that will override the detected "readelf" as it seems that READELF doesn't work. You should convert your scripts to makefile targets within the Makefile of "perl". There are several places where you can put your targets : Does it work with the readelf from your local system? Can you cross compile perl? |
I don't know what was your previous process but some stuff is overriden in SPKSRC : environment variables. Try to erase some targets and write them by hand without the $(RUN) so that TC_ENV isn't evaluated.
and so on |
yes, i can cross compile perl in my environment. i provide also a ready-build spk on my homepage (search for "perl mfr spk" on google ;-) ). i need a newer perl on synology for an other open source project im working for. these project need some cpan stuff, that missed at original synology perl. I dont want impose optware to the users. actually my Makefile within spksrc looks like:
|
As I said, get rid of $(RUN) and create a target that can reproduce the exact same environment as you have (without all the TC_ENV variables defined). I think maybe the original CC (from host) is needed to do some native compilation in the process. Environment variables could maybe set certain values on variables that do not belong here. Also, do not hesitate to join #synocommunity on Freenode |
ok.. thanks for now.. i will give it a try... last question: |
another last question: :-) |
By target I just meant redefine the Override As for the paths, don't worry about that just now and hardcode them. You'll replace with the dynamic ones later on when you make a successful build :) |
ok.. thanks again.. |
Any news on that? Good luck. |
no, not yet. i had to switch back to my own environment, because i had to fix a bug in my perl-package for the other open source project i am working on. so it's ok, to close this issue at this moment. |
while running configure, i've got this error:
The text was updated successfully, but these errors were encountered: