similar to: [LLVMdev] RESOLVED: [LLVMbugs] [Bug 451] Libtool does not create libNAME.$(SHLIBEXT) files when building dynamic libs

Anton, I didn't know that EQUIVALENCE is the only unsupported major Fortran feature, as this bug says. Can you give me an update on the status of the Fortran front-end and what the near-term goals are? I am getting more requests from academics doing HPC compilers and it would be useful to know where Fortran support stands. Other llvmdev'ers may be interested too. Thanks,

Currently the LLVMbugs list only receives emails when a new bug is filed or an existing bug gets finally resolved. The gcc-bugs list on the other hand receives an email for every new comment in bugzilla. This leads to much better transparency, because you can easily see which bugs are currently being worked on; while the current LLVMbugs setup left you totally in the dark. So my suggestion would

FYI, The changes to make libtool appear as mklib have now also been committed. If you want to have support for mklib in your build tree, here's what you do: cd $objdir rm libtool $srcdir/configure --prefix=... --llvmgccdir=... After configure runs, you should have a "mklib" script in your $objdir and the Makefile.rules have been configured to use it. Reid. On Sun, 2004-09-19 at

Hi, I get this error: ------------------ ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) ToolRunner.cpp:396: error: (Each undeclared identifier is reported only once for each function it appears in.) ------------------ And the config.log shows that configure has detected that ld on my platform (Interix) doesn't support shared libraries: ------------------

Hi John, Please see below, too >From: John Criswell <criswell at cs.uiuc.edu> >Date: Tue, 27 Jul 2004 14:57:02 -0500 > >Henrik Bach wrote: >>Hi, > >Please see below. > >> >>I get this error: >>------------------ >>ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >>ToolRunner.cpp:396: error: (Each

Hi again Does cygwin support shared libraries. And if not, how did you port llvm on this issue? /Henrik >From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Tue, 27 Jul 2004 00:41:53 +0200 > >Hi, > >I get this error: >------------------ >ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >ToolRunner.cpp:396:

> Anyone seeing this failure? > > FAIL: /Volumes/Gir/devel/llvm/llvm.src/test/CodeGen/Generic/2007-04-14-EHSelectorCrash.ll > for PR1326 Seems it was due to my changes. Investigating. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Tom > * Intel and AMD machines running on Win32 using MinGW libraries > (native) As you can see here, LLVM is happy on win32. > without installing third-party libraries? Do these libraries need to > be distributed along with the generated executables? It depends on, how exactly you're compiling LLVM. If you'll go with Cygwin-generated binaries, then yes

It looks like something has gotten its clock off by 12 hours; this arrived at 5:37 PM local time, and the clock on my local machine is correct... On Jan 3, 2008, at 5:37 AM, bugzilla-daemon at cs.uiuc.edu wrote: > http://llvm.org/bugs/show_bug.cgi?id=1896 > > Summary: Global Variable Optimizer fails assertion in > OptimizeAwayTrappingUsesOfLoads

Vikram, > I didn't know that EQUIVALENCE is the only unsupported major Fortran > feature, as this bug says. Can you give me an update on the status of > the Fortran front-end and what the near-term goals are? Ok. I was going to post something soon after 2.2 release, but let's do it now. LLVM 2.2 will contain (as a part of llvm-gcc 4.2) a port of gfortran compiler to the LLVM

Hi All, I did something dumb and bugzilla is sending out a ton of spam. We're working on it, I apologize for the email! -Chris

On Mon, 7 Nov 2005, Bill Wendling wrote: > What's the config.log from this run? its attached. -Tanya > > -bw > > On 11/3/05, Tanya Lattner <tonic at nondot.org> wrote: >> >> Following the instructions here: >> http://llvm.cs.uiuc.edu/docs/TestingGuide.html#run >> >> I get an error running configure in the llvm-test directory. >>

Hi, I am trying to install llvm 2.5 in my PowerPC machine. I have already installed XCode Tools 2.4.1. I can compile programs using gcc run them. I try to configure llvm 2.5, the configuration aborts with following message: checking build system type... powerpc-apple-darwin8.11.0 checking host system type... powerpc-apple-darwin8.11.0 checking target system type... powerpc-apple-darwin8.11.0

I can configure it now. Thank You! --- On Wed, 6/17/09, Bill Wendling <isanbard at gmail.com> wrote: From: Bill Wendling <isanbard at gmail.com> Subject: Re: [LLVMdev] Configure problem of llvm2.5 in Mac OS X 10.4.11 To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Date: Wednesday, June 17, 2009, 6:26 PM Hi Murat, This looks suspicious:  

Reid, Thank you for all your help. I think that I have AutoRegen.sh working now. (I still get the warning about GOB2_HOOK, but I'm assuming that's not a problem.) I'll explain the scenario that led to the problem. I copied the sample project to ~/work/myproject/src/sample. Then I renamed it to ~/work/myproject/src/llvm, indicating that this was the llvm part of my project.

Hi Ryan, The output from autoconf doesn't look familiar (but then, does it ever?). Note that it thinks that AC_CONFIG_MAKEFILE isn't defined which is likely if you didn't get the LLVM_SRC_ROOT correct. Here's the only things I can think of: 1. You also need to cvs update llvm/autoconf/m4 to get the new definition of LLVM_CONFIG_PROJECT. 2. You typed in the LLVM source root

Ryan, Rather than fix the documentation to match reality, I decided to fix reality to match the documentation. I have just committed (CVS head) changes to the sample project's AutoRegen.sh script that will prompt the user for the path to the LLVM source root and the LLVM object root, if it can't automatically determine the location (because your project is not located in the llvm/projects

It's complaining about the LLVM autoconf/m4 directory which contains the m4 macros that are used in your project's configure.ac. By convention, your project should be in the llvm/projects directory so that you have: 1. llvm/autoconf 2. llvm/projects/yourProj/autoconf The AutoRegen.sh in #2 is looking for #1. By convention that should be located at ../../../autoconf/m4. AC_CONFIG_AUX_DIR

On Sat, Apr 12, 2008 at 1:26 PM, Lane Schwartz <dowobeha at gmail.com> wrote: > John, > > Thanks for the advice. The script you sent gives me the same problem. > I am now able to work around the issue by making the following change > to the AutoRegen.sh script that comes with the sample project: > > 16,17c16,17 > < llvm_src_root=../../.. > <

Reid, Thanks for the help. I am trying out the fixes you checked into CVS. I seem to be getting some errors running AutoRegen.sh. I am a bit inexperienced with autoconf and m4. The errors I'm getting are below. Do you know what the problem is? I am using machines running FC3. The autoconf version is 2.59, the aclocal version is 1.9.2, and the m4 version is 1.4.1.