Just to make everything clear, I did a build with the shared library for
OpenOCD. This is the result on the final binary using ldd:
$ ldd /usr/bin/openocd
linux-vdso.so.1 => (0x00007fffed7ff000)
libopenocd.so.0 => /usr/lib64/libopenocd.so.0 (0x00007fce2f631000)
libdl.so.2 => /lib64/libdl.so.2 (0x000000371b400000)
libftdi.so.1 => /usr/lib64/libftdi.so.1 (0x0000003161800000)
libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x000000372e200000)
libc.so.6 => /lib64/libc.so.6 (0x000000371ac00000)
/lib64/ld-linux-x86-64.so.2 (0x000000371a800000)
$
So I guess either the static library build should be used and the resulting
libopenocd.a needs to be deleted or the shared object is just shipped with
the RPM. There can be a development package later once the interface is
finalized for the library that includes the link to the unversioned so and
the needed header files. These are not part of this package so people
shouldn't be able to work with the library without some work on their part.
// Dean Glazeski
On Wed, Aug 19, 2009 at 2:00 PM, Dean Glazeski <dngl...@gmail.com> wrote:
> Well, the problem is that the default is to actually build a static
> library. If you try to disable the static library without enabling the
> shared library, it will still make the static library anyway. I think it's
> a problem with the build, but I don't know how to work with the
> autoconf/automake chain.
>
>
> // Dean Glazeski
>
> David Brownell wrote:
>
> On Tuesday 18 August 2009, Dean Glazeski wrote:
>
>
> I can't disable the building of libraries so I assumed the library was
> in use by the OpenOCD executable. Am I mistaken?
>
>
> On this system:
>
> $ ldd src/openocd
> linux-vdso.so.1 => (0x00007fff7dbfe000)
> libdl.so.2 => /lib/libdl.so.2 (0x00007fbb7561a000)
> libftdi.so.1 => /usr/local/lib/libftdi.so.1 (0x00007fbb75414000)
> libusb-0.1.so.4 => /lib/libusb-0.1.so.4 (0x00007fbb7520c000)
> libc.so.6 => /lib/libc.so.6 (0x00007fbb74eaa000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fbb7581e000)
> $
>
> With that /usr/local/... stuff working around Ubuntu 8.04 version
> issues with those libraries (configure CFLAGS=... LDFLAGS=...)
>
>
>
>
> If so, I can just
> have the spec file delete the libraries that the make process creates.
> If there is a configuration option I need to use to make the final
> server not use an external library, let me know what it is. Thanks.
>
>
> I use "configure ... --disable-shared ..." which IMO ought to be
> the default.
>
> - Dave
>
>
>
> // Dean Glazeski
>
> David Brownell wrote:
>
>
> On Thursday 06 August 2009, Chitlesh GOORAH wrote:
>
>
>
> Keep an eye on https://bugzilla.redhat.com/show_bug.cgi?id=502130 for
> further updates.
>
>
>
> You should not include a "libopenocd" ... there are are *NO* public
> supported programming interfaces in that code. Don't include any
> library at all; just "openocd" server that links against stuff like
> libftdi and libusb.
>
>
>
>
>
>
>
>
>
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
