bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MacOS X 10.3.7 Build Problem After CVS CheckOut


From: Derek Price
Subject: Re: MacOS X 10.3.7 Build Problem After CVS CheckOut
Date: Tue, 03 May 2005 23:11:20 -0400
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Conrad T. Pino wrote:


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Derek,

From: Derek Price [mailto:address@hidden

I never thought it was worth coming up with a more automated solution, but you're welcome to try. I would argue against changing the name of the executable though, and I'm not sure what else is workable.

The "configure" script could test for the existence of a directory named
"src/cvs" and if true then execute a "mkdir build" command if "build" is
not already created.

That being said, how many shell variations need to be tested before we
commit such a fix assuming there are no objections?

What good would it be to make the build directory if the user didn't know to cd there before building? Also, once the src dir is configured, the build dir will refuse to be configured. The user would have to `make distclean; cd build; ../configure' afterwards anyhow. There might be a way to bootstrap that, but why not try something simpler, like just printing a nice, easy-to-spot-and-read warning message?

The test would be something like

"$srcdir" = "$builddir" && $fs_case_insensitive && test -z "$exe_ext"

I'm sure those var names are not correct, but you would have to make sure the latter test ran after all the tests that set the correct flags.

Cheers,

Derek




reply via email to

[Prev in Thread] Current Thread [Next in Thread]