[xmlsec] Problem with xmlsec configure

[Roumen Petrov]

Mike Peat wrote:
> Hi Roumen
>
> [SNIP]
> //===================
> ...
> make[5]: Entering directory 
> `/projects/xmlsec1/xmlsec1-1.2.18/include/xmlsec'
> ----------------------------------------------------------------------
>
> *** WARNING ***:
>
> You seem to have old xmlsec header files installed in:
>
>   "/projects/xmlsec1/xmlsec1-1.2.18/include/xmlsec"
This is old default location : $(includedir)/xmlsec


>
> The entire directory will be removed now.
> To allow parallel installation of different xmlsec library versions,
> the header files are now installed in a version specific subdirectory:
>
>   "/projects/xmlsec1/xmlsec1-1.2.18/include/xmlsec1/xmlsec"
, i.e. new one is is $(includedir)/xmlsec1/xmlsec. Note extra 
subdirectory 'xmlsec1' in path.

>
> ----------------------------------------------------------------------
>
> rm: cannot remove directory 
> `/projects/xmlsec1/xmlsec1-1.2.18/include/xmlsec': Permission denied
I think this is windows limitation - a process still use old header 
location or race condition from antivirus or ....
May be for details you would like to review cygwin implementation of 
removal commands and hacks for microsoft OS-es.

> [SNIP]
xmlsecincdir = $(includedir)/xmlsec1/xmlsec

> ...
> remove-old-headers:
>     @if test "x$(DESTDIR)" = "x" && test -d "$(includedir)/xmlsec"; 
> then \
> [SNIP]
>         echo "  \"$(xmlsecincdir)\""; \
> [SNIP]
>         rm -rf "$(includedir)/xmlsec"; \
>     fi
> [SNIP]
>
> My workaround was just to comment-out the "rm" line, which resulted in 
> workingness.

> I suspect that this is an actual bug rather than an aspect of my 
> stupidity.
I don't know why in you environment exists 
.../xmlsec1-1.2.18/include/xmlsec.
This is not real issue (see above old vs new location).

May be one minus before remove commands just to ignore results is enough.

If I'm right for race in recursive removal then after reboot OLD 
directory  won't exists.

> Mike
[SNIP]

Roumen