Skip to content
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

uClibc Compile has an error: #2

Open
dssds opened this issue Apr 5, 2017 · 6 comments
Open

uClibc Compile has an error: #2

dssds opened this issue Apr 5, 2017 · 6 comments

Comments

@dssds
Copy link

dssds commented Apr 5, 2017

No description provided.

@dssds
Copy link
Author

dssds commented Apr 5, 2017

LD ld-uClibc-0.9.34-git.so
ldso/ldso/ld-uClibc_so.a(ldso.oS): In function _dl_get_ready_to_run': ldso.c:(.text+0x44bc): undefined reference to abort'
collect2: error: ld returned 1 exit status
make: *** [lib/ld-uClibc.so] Error 1

@stffrdhrn
Copy link
Member

Hello, I am not sure sure about this issue or how you tested it. But we do have some people working on uclibc-ng. (next gen). You can try building it with openADK.

https://openrisc.io/software.html#openadk

@jm2000
Copy link

jm2000 commented Jun 8, 2017

I meet the same problem. dssds, How did you solve it?

@dssds
Copy link
Author

dssds commented Jun 12, 2017 via email

@jm2000
Copy link

jm2000 commented Jun 13, 2017

Thanks dssds. I had compiled uClibc-ng and runned or1ksim too.
but I have some problem. My target is or1k-linux-uclibc, How do I get GDB for openrisc?
I don't know the difference between or1k-linux-uclibc- and or32-linux-, because the dbg do not support or1k-linux* (see or1k-src\sim\or1k\configurate.ac line 7). So if I want get gdb, I must use target or32- or or1k-elf, etc?

@dssds
Copy link
Author

dssds commented Jun 14, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants