An upcoming bsd.port.mk patch will result in AUTOCONF, AUTOMAKE, etc values that are full paths. The current code (which in mutt-devel I think I may be responsible for, oops) barfs and prevents the port from building. This needs to be fixed ASAP so we can test it in the next 4-exp run. To udo.schweigert: I'll commit for you if you're not a committer and you give the ok. Fix: ==8<====8<====8<====8<====8<====8<====8<====8<====8<====8<== How-To-Repeat: Try to build with unreleased bsd.port.mk patch. Look at the "latest 4-exp run" error logs on bento if you want to see the crash in all its fiery glory.
On Wed, Oct 23, 2002 at 10:03:01AM +0200, Udo Schweigert wrote: >On Tue, Oct 22, 2002 at 18:33:26 -0400, Alan Eldridge wrote: >> To udo.schweigert: I'll commit for you if you're not a committer and you give >> the ok. >> > >OKed. > >As far as I see: the only thing changed is the deletion of the trailing "/" >chars, isn't it? No, it's changing the '/' to '|' so it won't interfere with the '/' in a full pathname. Thanks. PS If you leave the ports/NNNNN in the subject, the messages can be indexed by the BSD bugs database to provide a better audit trail. -- Alan Eldridge Unix/C(++) IT Pro, 20 yrs, seeking new employment. (http://wwweasel.geeksrus.net/~alane/resume.txt) KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/)
State Changed From-To: open->closed Committed with maintainer's approval.