search for: smolski

Hello Aaron, Aaron Gray wrote on 14/10/2005 at 5:50 a.m.: >> Also, it would be really nice if an official cygwin build (the >> binary) was published too. I spent quite a bit of time screwing >> with it a few months ago, and it was quite a bastard to get >> going... > I had quite a time with it too, could only get the debug version to > build as there seemed to be an

> Also, it would be really nice if an official > cygwin build (the binary) was published too. I spent quite a bit of > time screwing with it a few months ago, and it was quite a bastard to > get going... I had quite a time with it too, could only get the debug version to build as there seemed to be an internal problem with ld. I would very interested in how you got it running and

Oleg, > - llvm/make tools-only worked ok Good. > - llvm-gcc/make all failed with the following message (2nd try): > make[2]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > make[1]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > Checking multilib configuration... > multilib.out is unchanged > Configuring in i686-pc-cygwin/libstdc++-v3 >

Hi all, Any news on the cygwin front? What needs to be done? Can I help? Oleg.

Hello all, John Criswell wrote on Wednesday, 11 May 2005: > If other developers (especially those for platforms which we don't have > here at UIUC) could test the release branch, we would be most > appreciative. I will send out another email detailing when the release > branch is finished and how to get it out of CVS. I've just tried building CVS/HEAD of llvm using gcc 4.0.0

Oleg Smolsky wrote: > I've just tried building CVS/HEAD of llvm using gcc 4.0.0 that I have > installed to /opt/gcc ... then you should either add /opt/gcc/lib to /etc/ld.so.conf and rerun ldconfig, or add /opt/gcc/lib to your LD_LIBRARY_PATH . However, GCC 4.x definitely has issues building LLVM, at least on ia64. If you want to use LLVM in anger, I'd stick with 3.4 for now.

Dear LLVMers, Here is the current, tentative schedule for LLVM 1.5: 1. We are hoping to have all relevant features and bug fixes into mainline CVS by Friday of this week. For those of you with commit access, please plan to have all of your changes for LLVM 1.5 committed by 9 am (CST) this Friday. If you need more time, please email the list. 2. On Friday, I will be making the 1.5 release

On Wed, Dec 08, 2004 at 11:23:39AM +1300, Oleg Smolsky wrote: > > 1. Make sure your path now includes <builddir>/Debug/bin instead of > > <builddir>/tools/Debug. This changed a little while back. > > Interesting. I don't have llvm/Debug/ after building "tools-only". Is > that a symlink? Do symlinks work under cygwin? (I run xp and both of my >

On Tue, Dec 21, 2004 at 10:24:29AM +1300, Oleg Smolsky wrote: > Any news on the cygwin front? What needs to be done? Can I help? At some point, LLVM built and ran on Cygwin, however, the only user at the time (Chris) no longer uses Cygwin, so it may or may not currently build on Cygwin. Please try it out, if it doesn't work, please tell us what's wrong, or, better yet, submit a patch.

Thanks! That helps! Reid. On Thu, 2004-12-23 at 12:07, Oleg Smolsky wrote: > Hi Reid, > > > Jeff, can you provide a test case that we can use to > > reproduce this problem? Looks like I'm finally going to > > force myself into a windows build (i.e. cough up the money > > for VC++ 7.1). > You can also download MS Visual C++ Toolkit 2003 - contains the

Oleg Smolsky wrote: > Hey all, > > is anyone gonna make a debian package for stable or testing? It's just > that building llvm/cfrontend drives me crazy :) We don't have Debian packages for LLVM 1.5, but we do have a pre-compiled GCC frontend for i386/Linux. Does that not work on Debian? > > Best regards, > Oleg. > >

Hey all, is anyone gonna make a debian package for stable or testing? It's just that building llvm/cfrontend drives me crazy :) Best regards, Oleg.

Hi Reid, > Jeff, can you provide a test case that we can use to > reproduce this problem? Looks like I'm finally going to > force myself into a windows build (i.e. cough up the money > for VC++ 7.1). You can also download MS Visual C++ Toolkit 2003 - contains the VC++ 7.1 compiler/linker as well as all the standard libraries and headers. No gui, no debugger though:

Hi Reid, > 1. Make sure your path now includes <builddir>/Debug/bin instead of > <builddir>/tools/Debug. This changed a little while back. Interesting. I don't have llvm/Debug/ after building "tools-only". Is that a symlink? Do symlinks work under cygwin? (I run xp and both of my partitions are ntfs) > If those don't clear the problem, please tell me

On Wed, 11 May 2005, Oleg Smolsky wrote: > Hello all, > > John Criswell wrote on Wednesday, 11 May 2005: >> If other developers (especially those for platforms which we don't have >> here at UIUC) could test the release branch, we would be most >> appreciative. I will send out another email detailing when the release >> branch is finished and how to get it out

Hello Duraid, Duraid Madina wrote on Wednesday, 11 May 2005: >> I've just tried building CVS/HEAD of llvm using gcc 4.0.0 that I >> have installed to /opt/gcc > ... then you should either add /opt/gcc/lib to /etc/ld.so.conf and > rerun ldconfig, or add /opt/gcc/lib to your LD_LIBRARY_PATH . > However, GCC 4.x definitely has issues building LLVM, at least on > ia64. Oh,

Hi all, > Please try it out, if it doesn't work, please tell us what's > wrong, or, better yet, submit a patch. :) Alright, here are the results of building the latest llvm from CVS under cygwin: lib\Debugger\SourceFile.cpp needs #include <assert.h> when building with gcc 3.3.3 tools\gccld\gccld.cpp line 128 tools\llvm-ld\llvm-ld line 318 need

Hi Reid, > I've been doing a Cygwin build today too. All these problems > have been updated in the current CVS. Please update your tree > and give it another try. Alright, this time everything works quite a bit better. However: tools\llvm-ld\llvm-ld.cpp needs the CopyFile() invocation fix identical to gccld.cpp Also, it turns out gcc 3.3.3 in cygwin is buggy and it's unable

Hi all, After successfully building llvm tools-only and cfontend, I went back to llvm directory and ran configure --with-llvmgccdir=$CFEINSTALL Unfortunately, at the end of the process I got the following configure: WARNING: ***** llvm C/C++ front end was not found, or does not configure: WARNING: ***** appear to be working. And I do have CFEINSTALL environment variable.... BTW, I have noticed