Displaying 4 results from an estimated 4 matches for "bcso".
Did you mean:
bcs
2007 Dec 14
3
Puppet 0.23 client on Redhat 9
Hi,
I wanted to know whats the ideal way to install puppet client
ie the below packages on Red Hat Linux release 9 (Shrike) system --
2.4.20-8smp
I get the dependencies issue with the below(bcso they are for RHEL4
which is 2.6 kernel).
What would be an ideal way, where can I get the tar source of the
compatible version of puppet/facter/ruby for Redhat 9
facter-1.3.7-1.el4.rf.i386.rpm
puppet-0.23.2-1.el4.i386.rpm
ruby-1.8.1-7.EL4.8.i386.rpm
ruby-libs-1.8.1-7.EL4.8.i386.rpm...
2011 Dec 11
0
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
...important to my project feature: to link against bitcode
> "shared objects". The semantics is pretty simple. The module treated as
> shared object is only used as the source of symbol names which be
> excluded from the list unresolved symbols.
In summary, linking foo.bc and bar.bcso (do you use a different
extension to differentiate from a "static" bc?) would be equivalent (but
faster, easier) to
$ llc bar.bc -filetype=obj -o bar.o
$ clang -shared -o bar.so bar.o
$ clang -use-gold-plugin foo.o bar.so -o t
Is that correct? In particular, "lld t" should sho...
2011 Dec 08
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
Hi llvm team!
I'm currently working on the extended version of llvm-ld, which has an
ability to check if all the symbols present (and fail if some symbols are
not resolved), treat archives in the right way (link all the object files
in the archive if it's specified as the regular input, not as -l) and the
most important to my project feature: to link against bitcode "shared
2011 Dec 12
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
...feature: to link against bitcode
> > "shared objects". The semantics is pretty simple. The module treated as
> > shared object is only used as the source of symbol names which be
> > excluded from the list unresolved symbols.
>
> In summary, linking foo.bc and bar.bcso (do you use a different
> extension to differentiate from a "static" bc?) would be equivalent (but
> faster, easier) to
>
> $ llc bar.bc -filetype=obj -o bar.o
> $ clang -shared -o bar.so bar.o
> $ clang -use-gold-plugin foo.o bar.so -o t
>
> Is that correct? In pa...