Date: Sat, 7 Nov 1998 00:28:21 -0400 (AST) From: The Hermit Hacker <scrappy@hub.org> To: Satoshi Asami <asami@FreeBSD.ORG> Cc: scrappy@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/devel/mico Makefile ports/devel/mico/patches patch-af patch-aj patches-af Message-ID: <Pine.BSF.4.05.9811062242320.126-100000@thelab.hub.org> In-Reply-To: <199811062203.OAA09801@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Nov 1998, Satoshi Asami wrote:
> * scrappy 1998/11/04 19:13:26 PST
> *
> * Modified files:
> * devel/mico Makefile
> * Added files:
> * devel/mico/patches patch-af patch-aj
> * Removed files:
> * devel/mico/patches patches-af
> * Log:
> * Added a patch from the MICO developers that allow it to compile with a
> * current bug in the egcs port (its not a bug in the port, its a bug in egcs
> * itself)...
>
> Your commit message sounds like you've added a workaround for egcs
> bugs, but you also changed this port to always use egcs, was that
> necessary? I mean, the rule of thumb is that depend on a compiler
> port only if the port can't be compiled with a system compiler.
> That's not the problem you're trying to fix here, is it?
first off, the 'patch' fixes a bug, period. Unless I screwed something up
along the way, if you try to compile mico-2.2.1 using gcc 2.7.2.1 without
the patch, and with --disable-mini-stl "enabled", the compile fails at the
same point...
As for depending on the compiler, I'm trying the build with the patch and
gcc 2.7.2.1 right now...that dependency may have been a mistake :(
gcc 2.7.2.1 also fails, but at a different point then what you
reported...the reason that I've been using egcs is that its what the MICO
developers recommend on their web page. The list, in order of preference:
egcs 1.1
gcc 2.8.x
gcc 2.7.2.x
Of course, the egcs port right now is an 'experimental' version, which has
its own inherient bugs, but according to obrien, its got less bugs then
egcs 1.1...1.1.1 is coming out soon, and I've been reporting bugs to both
MICO and EGCS development teams as a result of my attempts to get a
*stable* compile of MICO built. Its slow work when our egcs port isn't a
release, but a development copy, and a moving target :( I reported one
bug to the EGCS ppl, stating what version of EGCS i was using...first
response back was to upgrade to a newer version since our port was ancient
compared to the pre-releaes they are working on now :(
> By the way, your previous commit did not fix the problem here either.
> The qt dependency was already specified with USE_QT so it's redundant
> to have it in LIB_DEPENDS. Also, are you sure just using --with-tcl
> etc. without specifying any paths is going to make it find them in the
> right place?
I didn't realize abotu the USE_QT...I knew it was there, just
didn't really *understand* why.
> I have a feeling that you have something in /usr/local or /usr/X11R6
> that is not standard. Can you try emptying them up? I get this error
> by starting with empty /usr/local and /usr/X11R6. (Also, make sure
> you have /usr/bin in front of /usr/local/bin in your path, although it
> shouldn't make a difference here because you're calling "eg++"
> explicitly.)
Anything that I have in /usr/local and /usr/X11R6 is installed out
of ports, actually...except the egcs I'm using, which is a newer version
of of it. Empty out /usr/local and /usr/X11R6? I *just* did a complete
re-install of FreeBSD-3.0-RELEASE two weeks back, when my new drive
arrived...and i haven't instlaled anything into it except for from
/usr/ports/* ...
Try what is there now...it uses gcc 2.7.2.1, and MICO's internal
'stl' instead of what comes with 2.7.2.1, and appears to get built and
installed properly. Its useless for using with KDE/Koffice, but at least
it builds. I'm actively working on getting it to build properly/stablely
with --disable-mini-stl, to the point that I've just created two 'ports'
on my machine here, one using egcs and one using 2.7.2.1, so that I can
report any bugs generated by each...its gotta work with at least oen of
them...
BTW...gcc 2.8.x? the port? is anyone working on that? I'd be
curious to see whether it fixes the problems that are showing up with
2.7.2.1, but its been marked BROKEN forever now :(
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9811062242320.126-100000>