| Summary: | undefined externals in SDL_atomic.c on linux | ||
|---|---|---|---|
| Product: | SDL | Reporter: | marty leisner <martyleisner> |
| Component: | thread | Assignee: | Sam Lantinga <slouken> |
| Status: | RESOLVED INVALID | QA Contact: | Sam Lantinga <slouken> |
| Severity: | critical | ||
| Priority: | P2 | CC: | realburner |
| Version: | HG 2.0 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
|
Description
marty leisner
2009-08-15 00:16:48 UTC
Can you retest with the current SDL snapshot? http://www.libsdl.org/tmp/SDL-1.3.zip Thanks! *** Bug 799 has been marked as a duplicate of this bug. *** you can fix this by applying -march=native to the cflags Still waiting to hear if this issue is still present in the current snapshot. I've tested on both 32-bit and 64-bit Linux with no problems. (In reply to comment #4) > Still waiting to hear if this issue is still present in the current snapshot. > I've tested on both 32-bit and 64-bit Linux with no problems. I'll look into this some more -- after a configure/make/make install and trying to configure tests I'm getting: configure:3241: result: no configure:3285: gcc -o conftest -g -O2 -I/usr/local/SDL-5384/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT conftest.c -L/usr/local/SDL-5384/lib -Wl,-rpath,/usr/local/SDL-5384/lib -lSDL -lpthread >&5 /usr/local/SDL-5384/lib/libSDL.so: undefined reference to `__sync_fetch_and_sub_4' /usr/local/SDL-5384/lib/libSDL.so: undefined reference to `__sync_sub_and_fetch_4' /usr/local/SDL-5384/lib/libSDL.so: undefined reference to `__sync_fetch_and_add_4' /usr/local/SDL-5384/lib/libSDL.so: undefined reference to `__sync_add_and_fetch_4' collect2: ld returned 1 exit status configure:3292: $? = 1 configure: failed program was: These are in SDL_atomic.c, I'll investigate more. I'm using a ubuntu 7.10 on a PIII for this instance... marty What's the version of gcc you're using? Hey Marty, I haven't been able to reproduce this and I haven't heard from you in a while. What's the status of this? I did not experience this on Ubuntu 9.04, so either the issue was fixed in GCC before then? but IIRC those are GCC intrinsics and should have been available. The atomic code has changed significantly, and if this is still an issue, let's enter a new bug for it. |