similar to: [LLVMdev] -fPIC warning on every compile on Cygwin

Displaying 20 results from an estimated 50000 matches similar to: "[LLVMdev] -fPIC warning on every compile on Cygwin"

2009 Feb 19
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > Hi, > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > went. But after doing a svn update today I am getting the following > warning on every compile :- > > > llvm[3]: Compiling LowerAllocations.cpp for Debug build > /usr/src/llvm/lib/Transforms/Utils/LowerAllocations.cpp:1: warning: > -fPIC ignored for
2009 Feb 19
2
[LLVMdev] -fPIC warning on every compile on Cygwin
On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > Hi, > > > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > > went. But after doing a svn update today I am getting the following > > warning on every compile :- > > > > > > llvm[3]: Compiling LowerAllocations.cpp
2010 Oct 02
2
[LLVMdev] tblgen(75451) malloc: *** error for object 0x7fff5fbfcbd0: pointer being reallocated was not allocated
Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. #!/bin/bash -ev export LD=`xcode-select -print-path`/usr/bin/ld xcode-select -print-path ulimit -s `ulimit -s` ulimit -s mv ../clang-2.8 ./tools/clang mkdir ../llvm_objdir cd ../llvm_objdir ../llvm-2.8/configure --prefix=/sw --prefix=/sw --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw
2009 Feb 19
2
[LLVMdev] -fPIC warning on every compile on Cygwin
On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > Hi, > > > > > > I partly built LLVM on Cygwin yesterday and it was fine
2009 Feb 25
3
[LLVMdev] -fPIC warning on every compile on Cygwin
On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > >
2009 Feb 21
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca> > > <mailto:nicholas at mxc.ca <mailto:nicholas at mxc.ca>>> wrote:
2010 Oct 04
0
[LLVMdev] tblgen(75451) malloc: *** error for object 0x7fff5fbfcbd0: pointer being reallocated was not allocated
Hi Jack, I didn't get this error. Could you try again? Is it one of the release candidates in particular that's failing? -bw On Oct 2, 2010, at 8:04 AM, Jack Howarth wrote: > Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. > > #!/bin/bash -ev > export LD=`xcode-select -print-path`/usr/bin/ld > xcode-select -print-path > ulimit -s
2009 Feb 19
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > Hi, > > > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > > went. But after doing a svn update today I am getting the following > > warning
2009 Feb 27
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca> > > <mailto:nicholas at mxc.ca <mailto:nicholas at mxc.ca>>> wrote:
2012 May 29
3
[LLVMdev] make error
Hello, I am currently trying to install vmkit from source. I am running archlinux i686 with the 3.1.9-2 kernel. This output is from the directions given on the llvm site. Below is the configureation output along with the make output. I run ./configure with the following parameters ./configure --with-llvmsrc=../llvm --with-gnu-classpath-glibj=../classpath-0.97.2/lib/glibj.zip
2009 Feb 27
1
[LLVMdev] -fPIC warning on every compile on Cygwin
On Fri, Feb 27, 2009 at 7:14 AM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > >
2004 Sep 24
4
[LLVMdev] Little win32/Signals.cpp patch
It would be great to avoid STLPort and use plain vanilla VC... as I told, the biggest difference it's how the hash_map and hash_set are implemented, but I'm not so strong in C++ for resolving the iussue. About the build procedure, it's based on scons, and it's still at a very preliminary stage... Right now I'm trying to build TableGen with it, as till now I've always
2004 Aug 06
1
ices 0.3 on FreeBSD
I have successfully compiled Ices 0.3 on FreeBSD (4.7 and 4.9). You need to make sure that ALL the dependicies are installed (some depend on others) and when compiling them, that they compile with no problems. <p>Include some output of what errors you are getting and I #should# be able to help you on your way. <p>>From: "dave" <dmehler26@woh.rr.com>
2009 Mar 09
2
[LLVMdev] hash_set and hash_map?
Hi, I saw that Nick Lewycky removed the LLVM portable hash_map and hash_sets. My research group was relying on those classes. What replaces hash_map and hash_set? The LLVM implementation was very convenient as there is no equivalent in STL, and Microsoft's implementation had a different name, as does the C++ 0X implementation. Thanks. Tom Jablin
2019 Feb 04
5
Removing deprecated <ext/hash_set>, <ext/hash_map> and <ext/__hash>
Hi, Libc++ has been shipping the <ext/hash_set>, <ext/hash_map> and <ext/__hash> headers for a while and they are deprecated. Those headers contain data structures like __gnu_cxx::hash_map that have replacements like std::unordered_map. I would like to remove those headers. I've put up a patch for review but I won't commit it until we have a sort of plan because I know
2009 Feb 27
3
[LLVMdev] -fPIC warning on every compile on Cygwin
> Could you please rig Makefile.rules or something to print out the value > of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if > that's erroneously false. The configure script sets LLVM_ON_UNIX, not LLVM_ON_WIN32, for Cygwin: case $host in ... *-*-cygwin*) llvm_cv_link_all_option="-Wl,--whole-archive"
2009 Feb 27
0
[LLVMdev] -fPIC warning on every compile on Cygwin
>> Could you please rig Makefile.rules or something to print out the value >> of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if >> that's erroneously false. This works for me: Index: Makefile.rules =================================================================== --- Makefile.rules (revision 65633) +++ Makefile.rules (working copy) @@ -298,6
2009 May 19
6
[LLVMdev] -fPIC troubles on Linux x86 (32 bit)
Hi all, I noticed that now that --enable-pic is the default in svn, there's also some logic in Makefiles.rules to eliminate -fPIC for the case of mingw and cygwin: ifeq ($(ENABLE_PIC),1) ifeq ($(OS), $(filter $(OS), Cygwin MingW)) # Nothing. Win32 defaults to PIC and warns when given -fPIC else ... I would suggest that it should be done this way (i.e., eliminating -fPIC)
2016 Apr 29
4
Trying to build ices-0.4 on ubuntu and "libshout not usable"
Hello: I hope someone can take a look at this and give me a little push to get me past this logjam. I've been running icecast + ices-0.4 + a perl application developed internally which runs an mp3 stream for a number of years. I am migrating my server from CentOS to ubuntu so I can upgrade to Perl 5.18 (so as to get clean unicode processing for another application.) I have installed
2004 Sep 24
0
[LLVMdev] Little win32/Signals.cpp patch
Uh... this may be a silly question, but why can't you include <stdio.h>? It'd be much better than <iostream>. Anyway, I think I'll try this weekend to come up with my own way of building on Win32. I prefer that building on Windows depends only on Microsoft and GNU tools, and the fewer of the latter the better. My gut instinct is to capture all the files generated by