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

__enable_spi_locking_ret not defined #65

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments
Open

__enable_spi_locking_ret not defined #65

GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
Using update from code.google.com  from this morning

Try compiling/linking the "Console and File system driver initialization" 
listed in the documentation at
https://sites.google.com/site/propellergcc/documentation/libraries#TOC-Stdio-Dev
ices-Library

It fails to link with undefined reference to __enable_spi_locking_ret.  It 
looks like it need to be defined
as global in crt0_xmm.s

propeller-elf-gcc -Wall -I../include -mno-fcache -Os -mxmmc -Wall -I../include 
-mno-fcache -Os -mxmmc  -c -o file.o file.c
file.c:25:6: warning: return type of 'main' is not 'int' [-Wmain]
propeller-elf-gcc -o fopentest2 file.o   -mxmmc
/opt/parallax/lib/gcc/propeller-elf/4.6.1/../../../../propeller-elf/lib/xmmc/lib
c.a(file_io.o): In function `_dfs_use_lock':
(.text+0x14): undefined reference to `__enable_spi_locking_ret'
collect2: ld returned 1 exit status
make: *** [fopentest2] Error 1

Likewise, compilation under lmm fails with both `__enable_spi_locking_ret' and 
`__enable_spi_locking'
being undefined. Maybe null definitions need to be made for the other crt0s.

Original issue reported on code.google.com by [email protected] on 23 Jan 2014 at 6:11

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

No branches or pull requests

1 participant