Bug 22621
| Summary: | tcl.h and tk.h not in the right places. | ||
|---|---|---|---|
| Product: | Base System | Reporter: | opentrax <opentrax> |
| Component: | misc | Assignee: | freebsd-ports (Nobody) <ports> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->analyzed I really don't think this qualifies as a PR, since the behavior is actually by design. However, Justin may be able to add some pointers somewhere, or close this with a more authoritative voice. Responsible Changed From-To: freebsd-bugs->jseger Justin maintains several tcl ports State Changed From-To: analyzed->closed The reasons for using nonstandard installations of tcl libraries is, as you mentioned, to avoid namespace collision. Discussions regarding this appear in the ports mailing list archive. Perhaps you could submit a port that installs the expected headers with small headers that just "#error ..." with a detailed message and the tcl/tk ports could depend on that port to at least help our users out. Responsible Changed From-To: jseger->freebsd-ports common ports issue On Thu, 09 Nov 2000 20:07:22 PST, opentrax@email.com wrote: > True the real problem is simple to solve, but it seems > that a trival problem, because is has no glory or fame, > is being cast aside without good cause - only to reflect > on the entire community. FreeBSD is user-supported software. Without user contribution, it wouldn't exist, and I mean that in the most literal sense possible. Why not create the child port suggested by Bill Fumerola and submit it as a PR? Ciao, Sheldon. On 13 Nov, Sheldon Hearn wrote:
>
>
> On Thu, 09 Nov 2000 20:07:22 PST, opentrax@email.com wrote:
>
>> True the real problem is simple to solve, but it seems
>> that a trival problem, because is has no glory or fame,
>> is being cast aside without good cause - only to reflect
>> on the entire community.
>
> FreeBSD is user-supported software. Without user contribution, it
> wouldn't exist, and I mean that in the most literal sense possible.
>
> Why not create the child port suggested by Bill Fumerola and submit it
> as a PR?
>
Can you reprase your question? I'm not getting it.
Jessem.
On Mon, Nov 13, 2000 at 06:50:03AM -0800, opentrax@email.com wrote: > > Why not create the child port suggested by Bill Fumerola and submit it > > as a PR? > > > Can you reprase your question? I'm not getting it. Um, it's simple. Use send-pr(1) to send a problem report with the child port Bill suggested. -- wca |
Many applications that depend on tcl.h and tk.h break because the headers are not where they are expected to be. The headers should in /usr/local/include. Instead headers are placed in /usr/local/include/tcl${VERSION} and /usr/local/include/tk${VERSION} These files may be there to prevent name-space collision when several application (each) require a different version of TCL or TK. While the short turn problem has been solved no clear information is available as to what to do. Hence, if a 'make' breaks or 'configure' breaks, the end user has no clear direction. Even investigating the binaries offers very little help. How-To-Repeat: Install an application that is not in the packages or ports collections. Example, TkRATrc7. Currently, this Application is not in the packages. TkRATrc3 is.