search for: enable_p

On May 8, 2009, at 1:02 PM, Chris Lattner wrote: > This goes against our general direction for llvm libraries: they > should generally all be built pic. After reviewing yet more of the Makefile,rules file, I believe ENABLE_PIC is the right thing to check. Currently ENABLE_PIC has to be set to get shared bits built, if the user wants them. Given that, we can use that to control wether or not -mdynamic-no-pic is added. Because this _must_ be set, it is safe to use the setting of that flag to make the decision...

...he `<name>' function. */ > #define HAVE_<name> 1 > but in CMake-generated: > #undef HAVE_<name> > This happens because in config.h.cmake (config.h.in analog) these functions just are not checked for. Another difference: autofoo sets this by default: > #define ENABLE_PIC 1 > while CMake not. There are many other differencies, which bother me, so here is the question: is it harmless and if not - should i try to fix it? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201101...

...o: In function `all_symbols_read_hoo > k': > /llvm/llvm-src/tools/gold/gold-plugin.cpp:364: undefined reference to `_lto_code > gen_create' It looks like llvm/tools/lto wasn't built in step 1 (you can check to see if this is so). From the Makefile, it will built tools/lto when ENABLE_PIC is 1. Check to see what ENABLE_PIC is set to in the Makefile.config file. If it's not set, try using the --enable-pic flag during LLVM's configure. -bw

On May 8, 2009, at 12:58 PM, Mike Stump wrote: >> I think the best thing to do >> is to compile LLVM PIC (the default) and then build the clang front- >> end pieces with -mdynamic-no-pic. Does this work for you? > > The proposed patch is more general that that. It avoids the flag, > when it is known it can't work, and leaves it in otherwise. This > allows the

..."Bill Wendling" <wendling at apple.com> Cc: "Anton Korobeynikov" <anton at korobeynikov.info>, llvmdev at cs.uiuc.edu Date: Sunday, 2 January, 2011, 2:59 PM I tried adding --enable-pics but getting the same error. I opened the make file but don't see any flag of enable_pics :-(. Is there any way to get around the problem? Akramul --- On Sun, 2/1/11, Bill Wendling <wendling at apple.com> wrote: From: Bill Wendling <wendling at apple.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "akramul azim" <bijoy123_8 at yahoo.com> Cc: "An...

Hi,     I am planning to follow the steps to install LLVM for the ARM-target (Processor: Xscale, Architecture: armv5te):   1. Install binutils-2.21 (downloaded from gnu.org)   Steps:   $ ./configure --target=arm-unknown-linux-gnueabi --program-prefix=arm- --prefix =/llvm/arm --with-sysroot=/llvm/arms/sys-root   $ make   $ make install   2. Install LLVM   Steps   $ ../llvm-src/configure

On May 8, 2009, at 11:49 AM, Chris Lattner wrote: > On May 7, 2009, at 6:24 PM, Mike Stump wrote: >> I'm toying with building with -mdynamic-no-pic, but for this to work, >> the shared library bits in llvm can't be built with that flag. > > Hi Mike, > > If you're doing this for Clang's benefit, No, not really, I'm doing it for the general benefit of

..."Bill Wendling" <wendling at apple.com> Cc: "Anton Korobeynikov" <anton at korobeynikov.info>, llvmdev at cs.uiuc.edu Date: Sunday, 2 January, 2011, 2:59 PM I tried adding --enable-pics but getting the same error. I opened the make file but don't see any flag of enable_pics :-(. Is there any way to get around the problem? Akramul --- On Sun, 2/1/11, Bill Wendling <wendling at apple.com> wrote: From: Bill Wendling <wendling at apple.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "akramul azim" <bijoy123_8 at yahoo.com> Cc: "An...

On May 8, 2009, at 1:49 PM, Mike Stump wrote: > On May 8, 2009, at 1:02 PM, Chris Lattner wrote: >> This goes against our general direction for llvm libraries: they >> should generally all be built pic. > > After reviewing yet more of the Makefile,rules file, I believe > ENABLE_PIC is the right thing to check. Index: clang/Makefile.rules =================================================================== --- clang/Makefile.rules (revision 71270) +++ clang/Makefile.rules (working copy) @@ -338,6 +338,11 @@ C.Flags += -fPIC endif endif +else...

Try doing a clean build, then doing 'make ENABLE_PIC=1' -Chris On Apr 11, 2010, at 9:13 AM, ambika wrote: > > > From: ambika <ambika at cse.iitb.ac.in> > Date: April 8, 2010 9:10:25 AM PDT > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] Can someone help me with error while i make my own pass > > > Hi, &...

-------------- next part -------------- An embedded message was scrubbed... From: ambika <ambika at cse.iitb.ac.in> Subject: [LLVMdev] Can someone help me with error while i make my own pass Date: Thu, 08 Apr 2010 21:40:25 +0530 Size: 4901 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100411/33876147/attachment.eml>

Tried that but still no success Chris Lattner wrote: > Try doing a clean build, then doing 'make ENABLE_PIC=1' > > -Chris > > On Apr 11, 2010, at 9:13 AM, ambika wrote: > >> >> >> *From: *ambika <ambika at cse.iitb.ac.in <mailto:ambika at cse.iitb.ac.in>> >> *Date: *April 8, 2010 9:10:25 AM PDT >> *To: *llvmdev at cs.uiuc.edu <mailto:llvmd...

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) not only for win32, but for all 32 bit x86 systems. Or has anyone seen any kind of x86 sy...

...that already, so perhaps we can make it the default. But that warning isn't about PIC, it's about the fact that the .o's weren't compiled with libtool. It's looking for the matching .lo files. It's not clear to me what we ought to do here. Put 'lto' inside an if ENABLE_PIC and suppress the warning? Build everything in LLVM with libtool --mode=compile? Is there a simple way to limit that to just the .o files we end up installing? Nick

...;Bill Wendling" <wendling at apple.com> Cc: "Anton Korobeynikov" <anton at korobeynikov.info>, llvmdev at cs.uiuc.edu Date: Sunday, 2 January, 2011, 2:59 PM I tried adding --enable-pics but getting the same error. I opened the make file but don't see any flag of enable_pics :-(. Is there any way to get around the problem? Akramul --- On Sun, 2/1/11, Bill Wendling <wendling at apple.com> wrote: From: Bill Wendling <wendling at apple.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "akramul azim" <bijoy123_8 at yahoo.com> Cc: &quot...

...o: In function `all_symbols_read_hoo > k': > /llvm/llvm-src/tools/gold/gold-plugin.cpp:364: undefined reference to `_lto_code > gen_create' It looks like llvm/tools/lto wasn't built in step 1 (you can check to see if this is so). From the Makefile, it will built tools/lto when ENABLE_PIC is 1. Check to see what ENABLE_PIC is set to in the Makefile.config file. If it's not set, try using the --enable-pic flag during LLVM's configure. -bw -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachm...

...rated: > #undef HAVE_<name> > This happens because in config.h.cmake (config.h.in analog) these functions just are not checked for. > We may just not use those functions anymore - do you have a list of these? > Another difference: > autofoo sets this by default: > #define ENABLE_PIC 1 > while CMake not. > This is more concerning - maybe it's a windows specific problem that came along? -eric

....lo files. My question is this, why use libtool to build the .so? I don't see what libtool helps with here, and it is a nightmare to use in general. Why not directly use the gcc driver? -Chandler > > It's not clear to me what we ought to do here. Put 'lto' inside an if > ENABLE_PIC and suppress the warning? Build everything in LLVM with > libtool --mode=compile? Is there a simple way to limit that to just the > .o files we end up installing? > > Nick > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.ed...

...' DISABLE_ASSERTIONS='' DOT='' DOTTY='' DOXYGEN='' ECHO='echo' ECHO_C='' ECHO_N='-n' ECHO_T='' EGREP='' ENABLE_CBE_PRINTF_A='' ENABLE_DOXYGEN='' ENABLE_EXPENSIVE_CHECKS='' ENABLE_OPTIMIZED='' ENABLE_PIC='' ENABLE_THREADS='' ENABLE_VISIBILITY_INLINES_HIDDEN='' ENDIAN='' EXEEXT='' EXPENSIVE_CHECKS='' EXTRA_OPTIONS='' F77='' FFLAGS='' FIND='' FLEX='' GAS='' GRAPHVIZ='' GREP='' GROFF='...

...Y='' > DOXYGEN='' > ECHO='echo' > ECHO_C='' > ECHO_N='-n' > ECHO_T='' > EGREP='' > ENABLE_CBE_PRINTF_A='' > ENABLE_DOXYGEN='' > ENABLE_EXPENSIVE_CHECKS='' > ENABLE_OPTIMIZED='' > ENABLE_PIC='' > ENABLE_THREADS='' > ENABLE_VISIBILITY_INLINES_HIDDEN='' > ENDIAN='' > EXEEXT='' > EXPENSIVE_CHECKS='' > EXTRA_OPTIONS='' > F77='' > FFLAGS='' > FIND='' > FLEX='' > GAS=...