We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 350

Summary: Change of behaviour: existing apps now want a joystick
Product: SDL Reporter: Laurent Blume <laurent>
Component: joystickAssignee: Ryan C. Gordon <icculus>
Status: RESOLVED DUPLICATE QA Contact: Sam Lantinga <slouken>
Severity: major    
Priority: P2    
Version: 1.2.11   
Hardware: Other   
OS: Solaris   

Description Laurent Blume 2006-10-27 07:29:47 UTC 
After updating from SDL 1.2.9 to 1.2.11, it seems that applications that used to start without problem now won't because there's no joystick.

For example, lbreakout2
Fatal STK Error!
SDL not built with joystick support

And dosbox:
Exit to error: Can't init SDL SDL not built with
joystick support

Putting back SDL 1.2.9, they do start again.
Since there is still no joystick support on Solaris at this point, I suppose some internal behaviour changed in SDL?
Comment 1 Laurent Blume 2006-10-27 07:30:26 UTC 
Ooops, sorry, clicked on commit too quickly.
It's Solaris 10 x86, SDL built with Sun Studio 11.
Comment 2 Ryan C. Gordon 2006-10-27 14:51:29 UTC 
This suggests that SDL was built without the joystick subsystem at all, and the application is calling SDL_Init(SDL_INIT_JOYSTICK), which will immediately fail (SDL/src/SDL.c, around line 125).

You can build SDL with the joystick subsystem, in which case it will pass initialization, even if there are no joysticks found, or not pass SDL_INIT_JOYSTICK to SDL_Init()...this includes avoiding SDL_INIT_EVERYTHING.

Leaving this bug open for further comment, in case this was a prebuilt SDL package that we provided, or a breakage in a project file we supplied.

--ryan.
Comment 3 Ryan C. Gordon 2006-11-03 12:23:56 UTC 
Does "Sun Studio" use the configure scripts? If so, this is probably the same issue as Bug #356.

--ryan.
Comment 4 Ryan C. Gordon 2007-02-12 06:57:24 UTC 
Having heard no further comment, I'm inclined to believe this really was a dupe of Bug #356...please reopen this bug if you feel this hasn't actually been fixed.

--ryan.



*** This bug has been marked as a duplicate of 356 ***