Hello, and thank you for your reply.

Quoting Stanislav Sedov <[EMAIL PROTECTED]>:

On Tue, 02 Sep 2008 12:25:51 -0700
[EMAIL PROTECTED] mentioned:


Good. Perhaps you (or anyone) can suggest how I might debug /when/where/
these eval are called. I could use /usr/bin/script, but not sure how to
(e)grep the culprit(s).


Try to find the exact script which causes this (it'd be pretty easy if you
could find a port with this error reproducible). Then you will be able
to track the problem down by inserting a couple of echos/exits in the
offending script and observing the result.

Well, I ultimately found the problem by recognizing a pattern.
Since the error messages hadn't proved fatal as far as I could see.
I just continued to build as required - always keeping a watchful eye.
I began to notice what seemed to be ports checking against Apache were
emitting errors, where others were not. Then it occurred to me that my
problem was self-inflicted. I had made some changes to the Apache source
before making && installing. Because the changes were so unique, I bumped
the version by a tenth of a point (1.4x). I then remembered all the Apache
make conditionals being against 1.3 || 2 - the light went off in my pointy
head; the version /I/ installed was != 1.3 || 2, but > 1.3 < 2. D'OH! Well,
no harm has /yet/ come of it. The scripts simply emit the error and
continue on their merry way. So unless something bombs farther down the road,
I'll just accept/expect the errors knowing what they are trying to tell
me. :)

Thanks again for responding.

--Chris



--
Stanislav Sedov
ST4096-RIPE




_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to