@SET_MAKE@, missing separator when building curl

1,486 views
Skip to first unread message

Matthew Willis

unread,
Aug 2, 2009, 2:14:34 AM8/2/09
to minix3
I'm trying to port curl to minix, and I'm getting some errors when
using make after ./configure.

It looks like ./configure is not expanding autoconf macros correctly.
In particular, it leaves @SET_MAKE@ unexpanded (I think it's supposed
to be expanded to an empty line) as well as a bunch of other @foo@
macros.

Has anyone else experienced this problem with configure scripts?

Thank you,
Matt

Erik van der Kouwe

unread,
Aug 3, 2009, 1:55:04 PM8/3/09
to minix3
Hi Matt,

Configure scripts tend to be regular shell scripts, so you should
choose the proper shell to run it. The default shell on MINIX is ASH,
which is rather minimal. You can use packman to install another shell,
such as BASH or KSH, which probably provide the features the script
requires. After this, use "bash configure" or "ksh configure" to run
it.

With kind regards,
Erik

Greg King

unread,
Aug 9, 2009, 3:49:42 AM8/9/09
to minix3
On Aug 2, 2:14 am, Matthew Willis wrote:
> I'm trying to port CURL to Minix; and, I'm getting some errors when
> using make after ./configure.
>
> It looks like ./configure is not expanding Autoconf macroes correctly.
> In particular, it leaves @SET_MAKE@ unexpanded (I think it's supposed
> to be expanded to an empty line), as well as a bunch of other @foo@
> macroes.
> Has anyone else experienced that problem with configure scripts?

Yes, I have seen it. The bugs are in "configure.in" (or,
"configure.ac"). It does not contain calls to the macroes that
substitute text for those names.

For @SET_MAKE@, there should be a line in the file that says,
AC_PROG_MAKE_SET
It should sit somewhere close under the line that calls
AM_INIT_AUTOMAKE()
(The macro tests the brand of Make that is on your system. If Make
knows how to call itself, then @SET_MAKE@ will be empty. If it
doesn't know, then @SET_MAKE@ will become something like
MAKE = pmake
.)

I had trouble with @MKDIR_P@, also. That problem was because the
person who created the package used different revisions of Autoconf
and Automake than I had on my system.

Some steps that you can try:
1. Update your Autoconf and Automake packages to the latest revisions
that you can find.
2. Add AC_PROG_MAKE_SET if it is missing.
3. Use "autoreconf" to build fresh copies of everything.

If you still have @foo@ debris, then please list some of those names
in a reply. We can figure out what is missing from "configure.in",
and why.
Reply all
Reply to author
Forward
0 new messages