1 |
On 6/13/19 5:47 AM, John Covici wrote: |
2 |
> Hi. I use inn to fetch/post usenet news. I know its no longer in the |
3 |
> tree, but I would like to keep it going. The last version in the tree |
4 |
> 2.5.5-r1 no longer configures, so I wrote an ebuild similar to the |
5 |
> ones that used to be there which I copied to my local ebuilds for |
6 |
> 2.6.3. This configures and compiles fine, but gets linking errors |
7 |
> where it cannot find symbol HISTLOOKUP. |
8 |
|
9 |
You need to track down where HISTLOOKUP should be coming from, and then |
10 |
why in isn't finding it, but didn't miss it at configure/compile. Do |
11 |
"ldd /path/to/inn" to see if there is a library it can't find. If it |
12 |
finds everything, then perhaps it needs a newer version of whichever |
13 |
dependency includes (or is supposed to include) that symbol. |
14 |
|
15 |
You can also compare that ldd output to "ldd |
16 |
/path/to/inn/from/tarball". If there is any difference, then perhaps |
17 |
your ebuild is missing something in the ./configure command. |
18 |
|
19 |
> Now what is strange is if I just get the tarball and configure with |
20 |
> the same parameters and compile out of tree, it works fine -- at least |
21 |
> up to the point of make install. I would like to do things in such a |
22 |
> way that portage knows its there in case there is a preserved lib or |
23 |
> something that I need to take care of. I could not figure what the |
24 |
> difference is as to why the ebuild does not work and my out of tree |
25 |
> compile works, so it looks like I have two choices: |
26 |
> |
27 |
> 1. unmerge and just maintain the out of tree build or |
28 |
> 2. Leave it there and just do a make update which copies the binaries |
29 |
> over the old ones. If I do number 2, it might be impossible to go to |
30 |
> the 17.1 profile, so I am of two minds about this. |
31 |
> |
32 |
> If anyone has any insight into this I would appreciate it very much. |
33 |
> |
34 |
> Thanks. |