Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Debian 2 and j-pine
- To: tlug@example.com
- Subject: Re: tlug: Debian 2 and j-pine
- From: Totoro <riley@example.com>
- Date: 05 Nov 1998 11:16:20 +0900
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: "Stephen J. Turnbull"'s message of "Mon, 2 Nov 1998 18:14:06 +0900 (JST)"
- References: <XFMail.981102175056.riley@example.com> <13885.30686.795439.637152@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
- User-Agent: Gnus/5.07004 (Pterodactyl Gnus v0.40) XEmacs/20.4 (Emerald)
>>>>> "Stephen" == Stephen J Turnbull <turnbull@example.com> writes: >>>>> "Totoro" == Totoro <riley@example.com> writes: Totoro> I'm puttering around with Debian lately, and can't get Totoro> j-pine to compile. Pine and Pico both want to link Totoro> termcap, however, Debian is supposed to be using Totoro> terminfo. With the old termcap-compat in, the errors Totoro> continue. I've already tried changing the makefiles on Totoro> Pine and Pico to not use termcap, but it won't run. Stephen> As far as I know, although terminfo is preferred to Stephen> termcap for new applications, legacy applications should Stephen> compile with termcap support. The Pine and Pico makefiles are calling for -ltermcap in the libs section. From what Scott mentioned about termcap/libtermcap, what is it actually looking for here? Stephen> Unfortunately, Debian-JP does not measure up to the Stephen> quality of Debian in general IMO. And in any case, you Stephen> probably need to be extremely careful about compiling Stephen> Debian sources on the release they were configured for. Stephen> You often won't be able to compile 1.3 .dscs (you are Stephen> building from .dscs, aren't you?) on a 2.0 system, or Stephen> vice versa, and "slink" (current experimental branch) Stephen> sources are likely to be worse. I used the basic source tarball on this, plus the japanese patch. Stephen> However, it's probably better to start from a Debian-JP Stephen> .dsc for the wrong system release (or an old version of Stephen> Pine) than from UW sources + Japanization patches. At Stephen> least that will give you some idea of how to work around Stephen> the weirdness. Unfortunately, I cannot find anything like this. The Debian-JP web site has no reference to a Pine application. Guess I'll try playing with the binaries Chris is munching together. Meantime, I'll do without Pine and just hang with XEmacs/Gnus! Stephen> What are those two straight lines for? "Free software Stephen> rules." Until I spent some time reading the Gnus documentation last week, I didn't have any idea what you meant by this. Never would've thought that an RFC specifies the proper styles of signatures... -- David Riley Hachinohe Institute of Technology 88-1, Myo, Ohbiraki Hachinohe-shi, Aomori-ken 031-8501 JAPAN http://w3.clat.hi-tech.ac.jp ---------------------------------------------------------------- Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Technical Meeting: 12 December, 12:30 HSBC Securities Office ---------------------------------------------------------------- more info: http://tlug.linux.or.jp Sponsors: PHT, HSBC Securities
- Follow-Ups:
- Re: tlug: Debian 2 and j-pine
- From: Scott Stone <sstone@example.com>
- References:
- tlug: Debian 2 and j-pine
- From: Totoro <riley@example.com>
- tlug: Debian 2 and j-pine
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: NE2000 PCI
- Next by Date: Re: tlug: Debian 2 and j-pine
- Prev by thread: tlug: Debian 2 and j-pine
- Next by thread: Re: tlug: Debian 2 and j-pine
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links