Displaying 8 results from an estimated 8 matches for "dsohowto".
2006 Jan 05
1
Using gcc4 visibility features
R-devel now makes use of gcc4's visibility features: for an in-depth
account see
http://people.redhat.com/drepper/dsohowto.pdf
(and note there are older versions of that document around).
Consider for example stats.so. On a gcc4 Linux system this has just three
entry points
gannet% nm -g stats.so | grep " T "
00002720 T R_init_stats
0004a544 T _fini
00001f28 T _init
since the only entry point we need is...
2006 Sep 08
2
[LLVMdev] build broken on linux/amd64
On Fri, 8 Sep 2006, [UTF-8] Rafael Esp?ndola wrote:
> I am not sure if it is the correct solution, but the attached patch
> fixes the problem.
Your solution is correct, in that it will work and follows with the
current ifdef approach. I applied this patch though, which doesn't use
the ifdefs, hopefully it is more robust:
2006 Sep 08
0
[LLVMdev] build broken on linux/amd64
> Please lemme know if it works.
It does. Thanks.
> I don't know what that is :(
I believe that code compiled without -fpic is going into a DSO. This
creates text relocations that are not supported on linux/amd64
(http://people.redhat.com/drepper/dsohowto.pdf).
> -Chris
Rafael
2007 Apr 19
1
[LLVMdev] (possible) bytecode format change
Domagoj,
> Is that change absolutely necessary?
Unfortunately, yes. We're having at least two PRs opened for aliases
including libstdc++ compilation in shared mode for x86/linux.
> I've just spent 2 days compiling benchmarks. So, now I'd need to
> ditch all that and start from scratch...
No. Bytecode will be breaking only if it have module-wide assembler. I
don't think
2017 May 11
1
xrealloc namespace conflict
On 11 May 2017 at 12:16, Patrick Perry wrote:
| I've done a bit more investigation into this issue. Here is my current
| understanding of the situation:
|
| 1. I have a package on CRAN (corpus-0.3.1) that passes tests on all
| platforms except for Linux.
| 2. My package defines a C function, "xrealloc", for internal use.
| 3. The libreadline library that R links to defines a
2012 Oct 22
3
[PATCH 0/2 NOT WORKING] Symbol versioning
John,
This was my attempt to add symbol versioning to the library,
letting us break ABI without breaking any existing callers.
Unfortunately it doesn't work:
- the new versioned symbols are marked local in libguestfs.so
- the existing symbols should now have @GUESTFS_0.0 versions,
but don't
The documentation for this stuff is extremely thin, and I've
got a bad case of
2012 Oct 30
5
[PATCH v3 0/5] Add symbol versioning.
This is a simpler patch series to add symbol versioning.
I have pushed patches 1-3 upstream.
Rich.
2012 Oct 30
7
[PATCH v2 0/7] Add symbol versioning (now working).
This rather more complex patch series adds symbol versioning (7/7
shows it in action). This works for me, tested by running old and new
virt-inspector binaries against the new library.
Rich.