configure errors

Project Infrastructure LLVM Dev List Archives
1

I see two minor configure errors on FreeBSD. The first is:

checking for mmap of files... yes
checking if /dev/zero is needed for mmap... test: FreeBSD: unexpected operator
no

The second:

checking for python... true python
test: : bad number
configure: WARNING: QMTest requires Python 2.2 or later

I guess it shouldn't get the "bad number" error if python is missing (and it is in this case). But we don't use QMTest anymore, correct? So isn't the python test obsolete?

2

checking for mmap of files... yes
checking if /dev/zero is needed for mmap... test: FreeBSD: unexpected
operator
no

It could be due to the '==' in the test, it also trips up /bin/sh on
Sparc, so I use ksh for configuring.

checking for python... true python
test: : bad number
configure: WARNING: QMTest requires Python 2.2 or later

I guess it shouldn't get the "bad number" error if python is missing
(and it is in this case). But we don't use QMTest anymore, correct?
So isn't the python test obsolete?

I think it's obsolete and must be just an artifact left behind.

3

I see two minor configure errors on FreeBSD. The first is:

checking for mmap of files... yes
checking if /dev/zero is needed for mmap... test: FreeBSD: unexpected
operator
no

That was a bug and I just fixed it. Thanks for pointing it out.

The second:

checking for python... true python
test: : bad number
configure: WARNING: QMTest requires Python 2.2 or later

I guess it shouldn't get the "bad number" error if python is missing
(and it is in this case). But we don't use QMTest anymore, correct? So
isn't the python test obsolete?

ERM, we removed those tests before the /dev/zero test went in so I'm a
little confused on how those messages are generated. If you look at
autoconf/* you'll find that neither python nor qmtest occur in any file.
What were you configuring when this message was generated?

Reid.

4

llvm-test, I think.

Reid Spencer wrote:

5

Jeff,

I don't have the correct autoconf tools for regenerating llvm-test's
configure script which it needs. So, I'll check in the changes to
configure.ac but leave the rest to someone else (Misha?) to fix. The
llvm-test autoconf stuff is woefully out of date, unfortunately.

Reid.

6

It seems you _did_ regenerate it, Reid, and when I re-ran AutoRegen.sh,
the configure script was unmodified, so I have nothing to check in.

7

Yeah, I decided to fix the one problem but there are many many more in
llvm-test's configure script. Try turning on the --warnings=all flag and
you'll see what I mean.

Reid.