Can not "make clean" etc.

[Deling Ren]

On Sat, 7 Feb 2004, Lowell Gilbert wrote:

> Don't top-post, please.
Sorry about that.
>
> Deling Ren <lg at home.homeunix.org> writes:
>
> > On Sat, 7 Feb 2004, Lowell Gilbert wrote:
> >
> > > Deling Ren <lg+freebsd at home.homeunix.org> writes:
> > >
> > > > Hi all, I am experiencing a nasty problem: I can not "make clean" or "make
> > > > update" etc under /usr/port. In most of the ports, I can not even "make
> > > > install". They all yield a common error:
> > > >
> > > > Missing }.
> > > >
> > > > This problem also exists when I tried to compile the kernel by running
> > > > "config" and "make depend". But I have no problem with "make buildkernel
> > > > KERNCONF=...".
> > > >
> > > > I even tried to cvsup to the lastest port, didn't help. I suspect a
> > > > makefile that is commonly used is corrupted. Can anyone give a a clue
> > > > where to find it? It's 5.2 RC1.
> > > >
> > > > Any suggestion will be appreciated.
> > >
> > > Just a guess:  'which make' doesn't reply with /usr/bin/make?
> > >
> > Thanks for your reply, "which make" returned "/usr/bin/make". There are
> > some ports that I can "make install", such as gettext, but others have
> > problems, e.g. mutt. I can "make", but not "make install" :(
>
> Your ports makefiles (/usr/ports/Mk) might be corrupted somehow.
> Look at bsd.port.mk in particular.

Actually I already cvsuped to the lastest port. Anyway, I swiped out the
whole /usr/ports directory and extracted from the install CD. The result
was still the same. Since it also affected building the kernel. I
suspected it was "make". I extracted "make" from the CD and overwrote the
existing one and that didn't help either.

Then I made a discovery which is that if I use "/usr/bin/make update"
instead of "make update", it would be fine. I ran "which make" again and
it did show "/usr/bin/make". I later found out it was due to some tcsh
settings. I am using the settings from tcshrc.sf.net. After removing those
rc files, it works well now. I haven't yet figured out where exactly the
problem is, but I am glad I don't have to reinstall everything, which
would be a nightmare.

Thanks a lot for your help.

> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>