search for: pr845

All, Thanks to Chris' recent changes, PR845 is now resolved and there are currently no cycles in LLVM's library dependencies. This means you can link all LLVM software visiting each archive only once. To get the correct order for linking LLVM libraries, use the command: llvm-config --libs >From here on out, cycles in the library dep...

...You may redistribute copies of it under the terms of the GNU General Public License < http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. Written by Mike Haertel and Paul Eggert. I've updated llvm and llvm-gcc4 ant trying to build it again after PR845 was resolved. According to Reid's letter this PR coud be the reason of my problem. When I'll have the results of llvm-gcc4 build I'll report. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/2006080...

Hello Anton Thu, 3 Aug 2006 23:13:52 +0400 you wrote: > I won't be available for the next 10-12 hours if you'll need some more > files. Well. I have one idea. Could you please execute "sort --version" from your cygwin shell and let me know, whether it's GNU one (it should reply with the words "textutils") or windows-supplied one (it should just give you and

In order to solve PR845, I had to move some files in the cvs repository. As such, you might get link errors if you're working out of cvs and do a cvs up. To fix this, remove your 'llvm/Debug/lib' directory and rebuild, which will force the libraries to be relinked. Thanks, -Chris -- http://nondot.org/s...

Hello Anton Fri, 4 Aug 2006 21:45:19 +0400 you wrote: > Written by Mike Haertel and Paul Eggert. > I've updated llvm and llvm-gcc4 ant trying to build it again after > PR845 was resolved. According to Reid's letter this PR coud be the > reason of my problem. Anyway, "sort" call can cause large problems depending, where in your PATH cygwin directory is (before %SystemRoot%, or after). Another question: is your perl a cygwin's supplied one? -- With...

> > If you're building llvm-gcc4, you don't need the runtime libraries, so > I'd just stick with the "tools-only" build and declare success. If > you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) I switched to llvm-gcc4 but when I run make from obj folder i run into folowing errors: Can't find a library with no dependencies at