libtcl8.4.so missing (in tcl8.4-dev for some reason?)

Bug #59896 reported by sean finney
4
Affects Status Importance Assigned to Milestone
tcl8.4 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: tcl8.4

subject says it all. why is the shared library in the -dev package?

Revision history for this message
Michael Bienia (geser) wrote :

Thanks for your report but this is not a bug.
The shared library is /usr/lib/libtcl8.4.so.0 (included in tcl8.4). libtcl8.4.so is only needed for linking at compilation time therefore it is included in tcl8.4-dev.

I'm rejecting this bug report for now. Please reopen if your problem still exists.

Changed in tcl8.4:
status: Unconfirmed → Rejected
Revision history for this message
sean finney (sean-stickybit) wrote :

well *i* seem to need it for runtime programs anyway. perhaps something funny happened during compilation:

sean@jenka:~$ ldd /usr/local/Modules/3.1.6/bin/modulecmd | grep tcl
        libtcl8.4.so => /usr/lib/libtcl8.4.so (0xb7e59000)

which does not resolve to .so.0 when the .so is not present. re-reading my own problem i agree that libtcl8.4.so actually belongs in the -dev package, but now i'm confused why my program is dynamically linked against the library without the soname...

Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 59896] Re: libtcl8.4.so missing (in tcl8.4-dev for some reason?)

That's something in /usr/local -- Ubuntu never puts software there.

Revision history for this message
sean finney (sean-stickybit) wrote : Re: [Bug 59896] Re: [Bug 59896] Re: libtcl8.4.so missing (in tcl8.4-dev for some reason?)

On Thu, 2006-09-14 at 13:20 +0000, Dennis Kaarsemaker wrote:
> That's something in /usr/local -- Ubuntu never puts software there.

erm, you might say i'm aware of such details ;p

in my last message i thought it was pretty clear (i.e "my program") that
i wasn't assuming this, but was curious as to how such a program could
have been linked against the .so and not the .so.soname library. i'm
guessing that it's breakage in the upstream author's build process.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.