search for: expoert

29.06.2012, 12:17, "ryan" <stdstack at gmail.com>: > I tried some other configurations. Now with llvm 3.0 + clang 3.0, and expoert CC to be clang -flto -use-gold-plugin,and other ENV variables. > Good news is the "no archive symbol error message" is gone, but bad news is new error messages appear Why are you using outdated llvm and clang? -- Regards, Konstantin

I tried some other configurations. Now with llvm 3.0 + clang 3.0, and expoert CC to be clang -flto -use-gold-plugin, and other ENV variables. Good news is the "no archive symbol error message" is gone, but bad news is new error messages appear > /path/to/ld: error: ../mysys/libmysys.a: member at 8758 is not an ELF > object > /path/to/ld: error: ../mysys/l...

Thanks for replying! I didn't install the new binutils to system directory in case it messes thing up. For ranlib, from the error message, it seems to be the reason. But even I export RANLIB=/bin/true, clean the code and rebuild, it still fails with the same message. I created a symlink in /usr/lib/bfd-plugins as suggested in http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-March/030101.html.

...rt of limit on how many alias an endpoint can have? Therefor i'd like to use the "gwprefix" option. Do i have to patch the GnuGK to copy back the LRQ-Dest into the LCF if it's dealing with a Gateway? This seems a bit harsh, Have i got everything mixed up? I'm not a H.323 expoert so I don't know if someone is breaking protocol in the chain Cisco GW -> GnuGK -> Asterisk. Anyone with Ideas? Anyone using Asterisk with H323 support in a GW mode? Regards, Niclas Gustafsson CodeSense AB

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1320922479 0 # Node ID bc79b560aafa1e4dc42af00e6a326dc651b5636a # Parent 460b507e15f864dd6712f5040e36538d6e076ae4 libxl: use named options for tsc_mode. It seems that this knob is expoerted from the hypervisor as a raw integer (no symbolic names) documented in xen/include/asm-x86. Propagating that all the way to the end user is hardly friendly (it''s bad enough in the hypercall interface). Add an enum at the libxl level with a hopefully descriptive set of names. Deprecate t...

...so llvm 3.0 is not that outdated? Regards, Ryan On Fri, Jun 29, 2012 at 2:07 AM, Konstantin Tokarev <annulen at yandex.ru>wrote: > > 29.06.2012, 12:17, "ryan" <stdstack at gmail.com>: > > I tried some other configurations. Now with llvm 3.0 + clang 3.0, and > expoert CC to be clang -flto -use-gold-plugin,and other ENV variables. > > Good news is the "no archive symbol error message" is gone, but bad news > is new error messages appear > > Why are you using outdated llvm and clang? > -- > Regards, > Konstantin > -------------...