Bugs item #3029517, was opened at 2010-07-14 15:09
Message generated for change (Settings changed) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3029517&group_id=976
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: compile or build problem
Group: new feature request
>Status: Closed
Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: Christopher Hotchkiss (chotchki)
Assigned to: Daniel Stenberg (bagder)
Summary: The base Makefile does not have a clean target
Initial Comment:
I am currently integrating a source build of curl into a continuous integration system and I just noticed that curl does not support "make clean" until after the ./configure step. Could this be added? Otherwise to clean up the build we will have to run an extra ./configure.
OS: Solaris 10 64bit - sparc
Curl: 7.21.0
----------------------------------------------------------------------
Comment By: Daniel Stenberg (bagder)
Date: 2010-07-16 08:50
Message:
I've not been convinced we need to do anything about this. I would much
prefer a discussion on the curl-library mailing list if you still want to
push for this idea-
----------------------------------------------------------------------
Comment By: Daniel Stenberg (bagder)
Date: 2010-07-14 18:03
Message:
It still doesn't make sense to me.
make clean is supposed to clean up everything that make built. If you
never ran make, there's nothing to clean.
So, before you run make there's nothing to clean, so 'make clean' (without
an existing clean target) does then by definition do the right thing:
nothing.
Most auto-tools based softwares don't even have a default Makefile so this
is something very few packages provide and for quite apparent reasons I
think...
----------------------------------------------------------------------
Comment By: Christopher Hotchkiss (chotchki)
Date: 2010-07-14 16:10
Message:
Clean up any existing ./configure and objects. I admit it makes zero sense
for one time builds.
As a process example if we do:
- svn update
- ./configure
- make
- make clean
and the make dies for whatever reason (insert random horrible solaris
problem). We have to do an svn revert to reset everything.
However if we can do a:
- svn update
- make clean
- ./configure
- make
we always know that we have a fresh working directory every time we run.
----------------------------------------------------------------------
Comment By: Daniel Stenberg (bagder)
Date: 2010-07-14 15:58
Message:
but before configure and make have been issued, what exactly would make
clean do?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3029517&group_id=976
Received on 2010-09-20