Date: Mon, 2 Feb 1998 09:45:04 +0100 (CET) From: Didier Derny <didier@omnix.net> To: Alex <garbanzo@hooked.net> Cc: Ruslan Shevchenko <Ruslan@Shevchenko.kiev.ua>, hackers@FreeBSD.ORG Subject: Re: egcs and Qt? Message-ID: <Pine.BSF.3.96.980202093608.12325C-100000@omnix.net> In-Reply-To: <Pine.BSF.3.96.980201235612.1476A-100000@zippy.dyn.ml.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 1 Feb 1998, Alex wrote: I've been able to port qt-1.32 (directly take from the www.troll.no web site) without any problem. the only things was: install the qt distribution in /usr/local/qt set the variables according to the INSTALL file I'm not sure but it seems that it needs the following environment variable to be defined QTDIR=/usr/local/qt CPLUS_INCLUDE_PATH=/usr/local/qt/include LD_LIBARY_PATH=/usr/local/qt/lib LIBRARY_PATH=/usr/local/qt/lib export QTDIR CPLUS_INCLUDE_PATH LD_LIBRARY_PATH LIBRARY_PATH cd /usr/local/qt make freebsd-shared in /etc/rc add a line to load the shared library at boot time for example, copy the /usr/local/lib line and replace qt were it's needed. (reboot or execut ldconfig with the right paths) use gmake instead of make You should be able to build qt without any problems. [after I rebuilt kde without any real problems] I've never tried with egcs > > On Sun, 1 Feb 1998, Ruslan Shevchenko wrote: > > > Alex wrote: > > > > > Has anyone had luck making the Qt port? I've tried the latest libg++ > > > (2.8.0 snapshots) in both static and shared form, to no avail. I was able > > > to get the Qt port to compile, but linking against the generated library > > > produced many many errors. However creating programs with egcs (or any > > > gcc) linked against the libraries created FreeBSD's gcc (2.7) seem to work > > > fine. Has anyone had better results with an a.out system? Any > > > suggestions? > > > > Linux fun's probabily solve this problem ;)(look at attachment) > > Hmm. Nice to see the warnings gone, but I'm still getting as warnings > (relocation burb for some symbol), and then getting undefined errors for > the same symbol when running programs linked against that library. > Compiling without -fno-implicit-templates will crap out with many many > multiply defined symbols. Too bad, cause I kinda liked the smaller > executables (-fno-exceptions -fno-rtti) too. > > Linux: The Microsoft Windows(tm) of the Unix(tm) world. > > - alex > > -- Didier Derny didier@omnix.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980202093608.12325C-100000>