Date: Tue, 22 Oct 2002 13:42:47 -0400 From: The Anarcat <anarcat@anarcat.ath.cx> To: John Baldwin <jhb@freebsd.org> Cc: Libh <freebsd-libh@freebsd.org> Subject: Re: rhtvision links against X11 Message-ID: <20021022174247.GB3492@xtanbul.espresso-com.com> In-Reply-To: <XFMail.20021022133727.jhb@FreeBSD.org> References: <20021022172422.GA3492@xtanbul.espresso-com.com> <XFMail.20021022133727.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue Oct 22, 2002 at 01:37:27PM -0400, John Baldwin wrote: > > On 22-Oct-2002 The Anarcat wrote: > > On Tue Oct 22, 2002 at 09:46:53AM -0400, John Baldwin wrote: > >> > >> On 22-Oct-2002 The Anarcat wrote: > >> > What a mess. > >> > > >> > We use rhtvision to provide a X-less installer and routines. > >> > > >> > I just discovered the unimaginable: > >> > > >> > /usr/local/lib/librhtv.so.2: > >> > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x281a3000) > >> > libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x2825f000) > >> > libncurses.so.5 => /usr/lib/libncurses.so.5 (0x28274000) > >> > libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x282b5000) > >> > libm.so.2 => /usr/lib/libm.so.2 (0x282fa000) > >> > libc.so.4 => /usr/lib/libc.so.4 (0x28069000) > >> > libXThrStub.so.6 => /usr/X11R6/lib/libXThrStub.so.6 (0x28315000) > >> > libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x28317000) > >> > libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x28361000) > >> > libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x2836a000) > >> > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x28380000) > >> > > >> > rhtvision seems to require X. Yay. That sucks. > >> > > >> > I've explored rhtvision's example programs a bit, and they have a X11 > >> > driver *by default*. That means they popup a X-window and don't > >> > display in the terminal you called them in if DISPLAY is set. > >> > > >> > These demos, by the way, work pretty well *except* in TTY mode. In a > >> > tty, they just *ignore* any input, apparently, so rhtvision is just > >> > plain borked, in FreeBSD, at least. > >> > > >> > And to make things even worse, this doesn't even fix the compilation > >> > issue. Liking against X and all those libs when linking the text build > >> > doesn't help much. > >> > > >> > I'm still trying to figure out if it's possible to build a X-less > >> > rhtvision under FreeBSD and have it work. If not, we'll have to port > >> > tvision to GCC 3.x, or scrap the tvision approach altogether and turn > >> > to another text mode backend. DlDialog, maybe? > >> > >> It shouldn't be that hard to forward port tvision to ANSI C++. > > > > Indeed. Are you volunteering? <grin> > > Well, I can do it if needed. :) Really? That'd be great. > > Seriously, you're right. I was thinking of trying to find a solution > > to the build problems against rhtv, but then I would have to fix rhtv > > to not use X anyways. > > > > I'll see what I can do about tvision. Is it actively maintained? > > Not that I'm aware of. That's bad though. rhtvision seems to be the most used tvision port, on the side of our linux friends at least, and both are not exactly API-compatible. :( Anyways, as long as we get the main build back on, I'd be pretty happy. A. PS: Good to see someone is still reading this mailing list :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021022174247.GB3492>