1 |
On Sunday 20 January 2002 15:15, you wrote: |
2 |
> On Sun, 2002-01-20 at 12:59, Juergen Ilse wrote: |
3 |
> > Hello, |
4 |
> > |
5 |
> > On Sun, Jan 20, 2002 at 10:46:53AM +0200, Martin Schlemmer wrote: |
6 |
> > > On Sun, 2002-01-20 at 00:41, Juergen Ilse wrote: |
7 |
> > > > On Sat, Jan 19, 2002 at 09:44:39PM +0200, Dan Armak wrote: |
8 |
> > > > > I haven't been able to find this myself either. What does provide |
9 |
> > > > > -lpython2.2? Python doesn't install any libs according to its |
10 |
> > > > > CONTENTS, but -lpython2.2 is in the python-config output. |
11 |
> > > > |
12 |
> > > > The static library mentioned above has the name libpython2.2.a |
13 |
> > > > I didn't find a shared version of this library. |
14 |
> > |
15 |
> > ^^^^^^ |
16 |
> > |
17 |
> > > it is here: |
18 |
> > > /usr/lib/python2.2/config/libpython2.2.a |
19 |
> > |
20 |
> > I already mentioned the place where to find the static version of this |
21 |
> > library. libpython2.2.a is *not* a shared library but a static one. |
22 |
> > I don*t know, if a shared version of this library is possible, but |
23 |
> > until now, there is no shared version. |
24 |
> |
25 |
> Out of the 'ld' manpage: |
26 |
> |
27 |
> -------------------cut here---------------------------------- |
28 |
> -larchive |
29 |
> --library=archive |
30 |
> Add archive file archive to the list of files to link. This |
31 |
> option may be used any number of times. ld will search its path- |
32 |
> list for occurrences of "libarchive.a" for every archive |
33 |
> specified. |
34 |
> |
35 |
> On systems which support shared libraries, ld may also |
36 |
> search for libraries with extensions other than ".a". Specifically, on |
37 |
> ELF and SunOS systems, ld will search a directory for a |
38 |
> library with an extension of ".so" before searching for one with an |
39 |
> extension of ".a". By convention, a ".so" extension |
40 |
> indicates a shared library. |
41 |
> ------------------cut here----------------------------------- |
42 |
> |
43 |
> Meaning, that -lpython2.2 can be libpython2.2.a *or* |
44 |
> libpython2.2.so, depending on if it is linked static or |
45 |
> dynamic. |
46 |
> |
47 |
> I check the CONTENTS of 2.0 against 2.2, and the only thing |
48 |
> that differs, is that Makefile.pre.in was not installed, which |
49 |
> is fixed now. |
50 |
> |
51 |
> Bottom line: koffice's build scripts is broken, or we need |
52 |
> to create a symlink from |
53 |
> /usr/lib/python2.2/config/libpython2.2.a to |
54 |
> /usr/lib/libpython2.2.a |
55 |
> |
56 |
> Anybody else have an idea ? |
57 |
I put in a fix into the koffice ebuild a few hours ago that simply adds -L |
58 |
/usr/lib/python2.2/config. |
59 |
|
60 |
The real fix should be to add the -L ... to the output of our python-config |
61 |
script. I'm about to do that. |
62 |
|
63 |
|
64 |
|
65 |
-- |
66 |
Dan Armak |
67 |
Gentoo Linux, Desktop Team |
68 |
Matan, Israel |