#70 The configure script deletes foreign Makefiles


I started working on building Atlas for OpenCSW (Solaris). We use a build system based on GNU make, which drives all the stages of package creation. The main build description files are Makefiles.

For example:

So, a Makefile in the current directory where an OpenCSW package maintainer is working, contains all the work on a given package. I started working on porting Atlas, and at some point I ran the configure script, like this:

$ ls
Makefile checksums files gar work
$ ./work/solaris8-sparc/build-isa-sparcv8/ATLAS/configure --help
$ ls
checksums files gar work

The configure script has deleted the Makefile which contained all my work for packaging Atlas. You can imagine I'm feeling somewhat grumpy about this. Would you please adjust the configure script so it doesn't delete people's Makefiles?


  • R. Clint Whaley

    R. Clint Whaley - 2010-03-03
    • labels: 362662 -->
    • milestone: 148060 -->
    • priority: 5 --> 1
    • assigned_to: nobody --> rwhaley
  • R. Clint Whaley

    R. Clint Whaley - 2010-03-03


    You have just submitted a documented feature of ATLAS (read the atlas install guide for how to run configure) as a bug, even though I specifically tell users not to submit anything to the bug tracker:

    You can imagine that I'm feeling somewhat grumpy about someone who wants me to change the package for them not bothering to read any of my documentation; not the install guide, and not the "how to submit a help request" . . . :)

    All that being said, I never thought of someone not reading the install guide and running configure in a non-scratch directory. I'm moving this over to the feature request tracker, and the next time I'm messing with configure, I will see if it is easy to modify the configure script to at least check for a Makefile and exit with an error message rather than overwriting . . .



Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks