CJ Keist wrote: >> >I did try running in both sh and bash but still got same error. >But I did get mailman to install. The problem was with the Makefile in >the misc folder. > >EMAILPKG= >JACODECSPKG= >KOCODECSPKG= > >PACKAGES= $(EMAILPKG) $(JACODECSPKG) $(KOCODECSPKG) > >There were no packages defined. Does this mean I didn't run configure >correctly?
No, it means that configure found suitable email and Korean and Japanese codecs packages in the installed Python and thus didn't need to install the ones that ship with Mailman. >I simply commented out the for p loop: > > #for p in $(PACKAGES); \ > #do \ > #gunzip -c $(srcdir)/$$p.tar.gz | (cd $(PKGDIR) ; tar xf -); \ > #(cd $(PKGDIR)/$$p ; umask 02 ; PYTHONPATH=$(PYTHONLIBDIR) >$(PYTHON) > $(SETUPCMD)); \ > #done > >This got mailman installed and looks to be working okay. That is a perfectly acceptable workaround, but the question is why doesn't your make properly handle for p in ; do ... ; done and treat it effectively as a no-op when the for list is empty? -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
