Bugzilla – Bug 140
[gccld] When seeing -l<lib>, should add a corresponding -load=<lib> to script
Last modified: 2003-12-12 13:38:52
You need to log in before you can comment on or make changes to this bug.
I'm getting tired of manually adding -load=/usr/lib... lines to every new lli runner script to run applications. This is made worse when an application decides to run an intermediate executable during its full program compilation cycle. In essence, since gccld has all this information on the command line, it should be nice and spit out an appropriate runner file.
That would be a cool feature. :) -Chris
As they say, if it scratches your itch, well, you know... :) This one's mine. Big time. The fix is pretty much done.
Fixed: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20031117/009712.html With this patch, programs magically start working without manual intervention! Life is good.
This is really an enhancement.
One could argue that it's not an enhancement since the programs wouldn't even run in the JIT without this. In testing Xlib apps, I had to manually insert -load=<lib> lines to the runner script to run the program, which may be considered an inconvenience, but in reality, if you can't run the resulting file after compiling it, it's broken.