title: Linking libraries with gcc: order of arguments
body: <p>As soon as I upgraded my Ubuntu distro to 11.10, I started seeing strange linker behavior with gcc. I was able to fix the problem by moving my <code>-l</code> arguments to the end of the gcc command (my problem was similar to the one described in <a href="https://stackoverflow.com/questions/7824439/c-math-linker-problems-on-ubuntu-11-10">this thread</a>, and the proposed solution worked for me...thanks!).</p>
  
  <p>My question is...why did I have this problem only now? I've been developing and testing this code on OS X and Ubuntu for a while: I never knew that <code>-l</code> commands are supposed to go after your .c files, but even so, this never gave me problems before. I'm guessing it has more to do with the version of GCC than the Ubuntu release version.</p>
  
  <p>Is this newer version simply enforcing this requirement more strictly than earlier versions?</p>