search for: tool_verbose

Reid, Looks like the "make TOOL_VERBOSE=1 -C tools install" was fine. I have got :- install (GNU coreutils) 5.3.0 The copyright is 2005 so I would have thought it would be allright ??? Thanks, Aaron

Okay, this is totally bizarre. Your "make TOOL_VERBOSE=1 install" output was perfect, no errors and all the commands look the way I'd expect them to look. My version of install is 5.2.1, older than yours.But I'd expect 5.3 would not change such basic functionality. When you do "make install" without the TOOL_VERBOSE=1, you get...

...snuff. It should be doing a command like: /usr/bin/install -c -m 0755 \ /proj/llvm/build/Debug/bin/llvm-ranlib /proj/install/bin/llvm-ranlib Its not supposed to create an llvm-ranlib directory, the second argument is the name of the file to create. This works fine on linux. Can you "make TOOL_VERBOSE=1 -C tools install" and send me some of the output. I'd like to know what install is doing on Cygwin. Thanks, Reid. On Thu, 2005-05-19 at 18:29 +0100, Aaron Gray wrote: > Am back to the same llvm 'make install' errors as I had before :- > > Two trivial ones, of uncrea...

Am back to the same llvm 'make install' errors as I had before :- Two trivial ones, of uncreated directories :- llvm[2]: Installing Debug /usr/llvm/bin/llvm-ranlib /usr/bin/install: target `/usr/llvm/bin/llvm-ranlib' is not a directory make[2]: *** [/usr/llvm/bin/llvm-ranlib] Error 1 make[2]: Leaving directory `/usr/build/llvm/tools/llvm-ranlib' make[1]: ***

...one back to the older Cygwin environment that worked before > >> but am now getting the same results as with the newer Cygwin > >> installation. Why it worked before but not now I do not know. > > > >Hrm. That's not good. > > > >Can you build with "TOOL_VERBOSE=1" and capture the output and send it > >to me. Something like: > > > >make TOOL_VERBOSE=1 2>&1 >make.out > > Okay, that was quicker than I thought. This didn't really show much. You built the X86 target and linked llc. All worked fine. > > >S...

...============= --- Makefile.rules (revision 71041) +++ Makefile.rules (working copy) @@ -472,6 +476,9 @@ ifneq ($(DARWIN_MAJVERS),4) LD.Flags += $(RPATH) -Wl,$(LibDir) endif + ifeq ($(OS),Darwin) + EXTRA_OPTIONS := $(filter-out -mdynamic-no-pic,$(EXTRA_OPTIONS)) + endif endif ifdef TOOL_VERBOSE can be used to strip the option out in the places it won't work. This mirrors the style used in other parts of the file. If the experiment goes well, I'd like to check this in, if no objections. If someone wants to approve it (pending testing), let me know...

I did not report this first error earlier as I thought it trivial. Basically it looks like something odd is happening with the configuration and 'include/llvm/config/config.h' Getting this error on building the tools on a fresh Cygwin install and update :- $ make tools-only make[1]: Entering directory `/usr/build/llvm/lib/System' llvm[1]: Compiling Path.cpp for Debug build In file

I'm now getting this trying to 'make check' on llvm: ./bin/runtest 1 --ignore "llvm2cpp.exp ocaml.exp" ) WARNING: Couldn't find the global config file. Illegal Argument "1" try "runtest --help" for option list Anyone else seeing this? I just did a full clean and rebuild and still get the problem. -Dave

Hi Tom, > I didn't dig into the Makefiles... are the libraries and whatnot built > -fPIC? If you do `make Verb=' then you'll see all the actual command invocations and can grep for bits of interest. Cheers, Ralph.

...passing > CPPFLAGS through from my Makefiles to the llvm compile command line. It > seems that anything I set in CPPFLAGS is set in the llvm Makefiles > themselves (seen through 'make printvars'), however they don't make it > to the gcc command line (see using 'make TOOL_VERBOSE=1'). > > I'm trying to add extra include paths to my build to modularise my > source better. > > Dominic > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs....

Chris> Are you using a debug or a release build? A release build (built with Chris> make ENABLE_OPTIMIZED=1) is often 10x to 20x smaller than a debug Chris> build, and links correspondingly faster. On some machines, a release Chris> build builds *faster* than a debug build because the debug symbols are Chris> so huge. The only thing you lose with a release build is the ability

...> +++ Makefile.rules (working copy) > @@ -472,6 +476,9 @@ > ifneq ($(DARWIN_MAJVERS),4) > LD.Flags += $(RPATH) -Wl,$(LibDir) > endif > + ifeq ($(OS),Darwin) > + EXTRA_OPTIONS := $(filter-out -mdynamic-no-pic,$(EXTRA_OPTIONS)) > + endif > endif > > ifdef TOOL_VERBOSE > > > can be used to strip the option out in the places it won't work. This > mirrors the style used in other parts of the file. If the experiment > goes well, I'd like to check this in, if no objections. If someone > wants to approve it (pending testing), let me know.....

Hi!! It's me again. I guess that there is a problem in the Makefile of my source code. But I don't know where. Could you please verify it? The Makefile is written like this: # Makefile for Genetic Algorithm Pass CXXFLAGS = -Wall -I/iss/fpga3/nicole/galib247/ LDFLAGS= -L/iss/fpga3/nicole/galib247/ga/ -lga -Wl,-E # Path to top level of LLVM heirarchy LEVEL=../../../ # Name of the

On May 14, 2008, at 4:46 AM, Dominic Hamon wrote: > Bill Wendling wrote: >> On Tue, May 13, 2008 at 2:24 AM, Joachim Durchholz >> <jo at durchholz.org> wrote: >> >>> Am Dienstag, den 13.05.2008, 00:42 -0700 schrieb Bill Wendling: >>> >>>> Sorry to step into this in the middle of a thread, but what >>>> exactly is

>From: Reid Spencer Date: Wed, 26 Jan 2005 12:23:49 -0800 > >Nope, unless "make" is an alias for "make -j 4" (like I have) make is make for me. > >Could you try using TOOL_VERBOSE=1 with make to get more output ? I've attached an output. Henrik. >Did you try just running the llvm-ar command by itself ? >If not, could you and give it the V (capital v) option to get lots of >verbose output? > >Thanks, > >Reid. > >On Wed, 2005-01-26 at 12:15, H...

Bill Wendling wrote: > On Tue, May 13, 2008 at 2:24 AM, Joachim Durchholz <jo at durchholz.org> wrote: > >> Am Dienstag, den 13.05.2008, 00:42 -0700 schrieb Bill Wendling: >> >>> Sorry to step into this in the middle of a thread, but what exactly is >>> LLVM's autoconf doing that "autoconf shouldn't do if properly set up"?

..._ROOT=~/llvm/obj $ export LLVM_GCC_DIR=~/llvm/cfrontend/x86/llvm-gcc $ export LLVM_LIB_SEARCH_PATH=~/llvm/obj/lib $ PATH=${PATH}:${LLVM_GCC_DIR}/bin # (using the prebuilt 1.5 llvm-gcc) $ cd $LLVM_OBJ_ROOT $ $LLVM_SRC_ROOT/configure --enable-targets=host-only ++++++++++++++ gmake stderr... $ gmake TOOL_VERBOSE=1 >../make2.log Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exc...

Hi Andrew, I seem to be making good progress on the P5600 scheduler using the new machine model but I've got a few questions about it. How would you represent an instruction that splits into two micro-ops and is dispatched to two different reservation stations? For example, I have two reservation stations (AGQ and FPQ). An FPU load instruction is split into a load micro-op which is

Hi Reid, I don't think I've initiated a parallel build by this command: ------------------------ make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi LDFLAGS+='-Wl,--no-keep-memory' -r VERBOSE=1 ------------------------ Henrik. >From: Reid Spencer Date: Wed, 26 Jan 2005 12:05:51 -0800 > >It looks like what you're getting is a sharing violation. Although, I

Chris, Thanks for your answer Here is the verbose output: =========================== gmake tools-only VERBOSE=1 TOOL_VERBOSE=1 for dir in lib/System lib/Support utils lib tools ; do \ if [ ! -f $dir/Makefile ]; then \ /home/myuser/LLVM/objdir/../srcdir/autoconf/mkinstalldirs $dir; \ cp /home/myuser/LLVM/objdir/../srcdir//$dir/Makefile $dir/Makefile; \ fi; \ (gmake -C $dir all ) || exit 1; \ done gmake[1]: E...