search for: libipa

...VMTransformUtils.a libLLVMipa.a > > LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the list > should depend on LLVMIPA. If you knew what was pulling in IPA that would > probably be an easy tie to sever. To diagnose and fix this, I need to know the specific symbol in libipa that is getting referenced. Reid, since you have the magical ability to run the script, can you look into it? -Chris -- http://nondot.org/sabre/ http://llvm.org/

...is not listed as a dependency, you need libsasl2-modules-gssapi-mit, otherwise authentication against LDAP/AD won't work apt-get install libsasl2-modules-gssapi-mit # Install sssd. We don't really need all built packages. This is what the metapackage "sssd" would install dpkg -i libipa-hbac0*.deb libsss-idmap0*.deb libsss-nss-idmap0*.deb python-sss*.deb sssd*.deb sssd-ad*.deb sssd-ad-common*.deb sssd-common*.deb sssd-ipa*.deb sssd-krb5*.deb sssd-krb5-common*.deb sssd-ldap*.deb sssd-proxy*.deb # You probably also want libnss-sss, libpam-sss, libsss-sudo, sssd-tools and some addit...

On Tue, 21 Mar 2006, Reid Spencer wrote: > About the only thing I can suggest are: > > 1. Combine LLVMSparc*.o into one LLVMSparc.a. That work is already > happening with the new Sparc backend that is being developed. Should be > out in 1.7 (Chris?) I wouldn't worry about the SparcV9 backend for your project. > 2. Combine the JIT/Interpreter/ExecutionEngine into one .a

On Thu, 26 Feb 2004, Reid Spencer wrote: > One of the things that I don't understand well about LLVM is what code > is in what object files or library archives. It would be very useful if > there was a map of the dependencies between the files (e.g. if you link > X.o you need Y.a and Z.o). Trying to figure out the link lines by trial > and error is a bit frustrating. No

...to the LLVM docs directory so I can > > submit patches against it? BTW, here's some hints for it: libtransforms.a -> contains only the level raise pass libtarget.a -> contains code generator support for describing target architectures libanalysis.a -> intraprocedural analyses libipa.a -> interprocedural analyses libinstrument.a -> instrumentation (e.g. profiling) transformations libtransformutils.a -> common code shared by various xforms libregalloc.a -> sparc register allocator sched.o -> sparc instruction scheduler select.o -> sparc instruction sel...

One of the things that I don't understand well about LLVM is what code is in what object files or library archives. It would be very useful if there was a map of the dependencies between the files (e.g. if you link X.o you need Y.a and Z.o). Trying to figure out the link lines by trial and error is a bit frustrating. To assist myself with understanding this, I've started to write a