configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Ryan McLeod]

I get the above error when I am trying to cross-compile openswan for
cygwin as laid out here:
http://www.cygwin.com/ml/cygwin/2005-08/msg00175.html

The only thing i do differently is:

../../winsup/configure --prefix=/myprefix/cross
--target=i686-pc-cygwin --without-headers \

--with-newlib --disable-shared --enable-languages=c,c++

changes to:

../winsup/configure --prefix=/myprefix/xelerance/cross/win2k
--target=i686-pc-cygwin --without-headers \

--with-newlib --disable-shared --enable-languages=c,c++

The prefix change is mentioned as that in the openswan documents, but
considering i only go up one directory from winsup

and into a build directory from there, not sure why he specified
../../winsup. I did have to copy install-sh, config.guess and
config.sub into the winsup directory, as i was getting configure
errors then with the install-sh. But now its asking for it

in a directory that seems to be irrelevant to the install. configure
error: cannot find install-sh or install.sh
in ../.. "../../winsup/cygwin"/../..

Thanks for any assistance.


Ryan

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Matthias Andree]

Am 19.07.2010 17:29, schrieb Ryan McLeod:
> I get the above error when I am trying to cross-compile openswan for
> cygwin as laid out here:
> http://www.cygwin.com/ml/cygwin/2005-08/msg00175.html
> 
> The only thing i do differently is:
> 
> ../../winsup/configure --prefix=/myprefix/cross
> --target=i686-pc-cygwin --without-headers \
> 
> --with-newlib --disable-shared --enable-languages=c,c++
> 
> changes to:
> 
> ../winsup/configure --prefix=/myprefix/xelerance/cross/win2k
> --target=i686-pc-cygwin --without-headers \
> 
> --with-newlib --disable-shared --enable-languages=c,c++
> 
> The prefix change is mentioned as that in the openswan documents, but
> considering i only go up one directory from winsup
> 
> and into a build directory from there, not sure why he specified
> ../../winsup. I did have to copy install-sh, config.guess and
> config.sub into the winsup directory, as i was getting configure
> errors then with the install-sh. But now its asking for it
> 
> in a directory that seems to be irrelevant to the install. configure
> error: cannot find install-sh or install.sh
> in ../.. "../../winsup/cygwin"/../..
> 
> Thanks for any assistance.

Without looking at the actual issue (no time), and just as a pointer to a solution:

If autoconf/automake are involved, there are pre-defined variables such as
$(srcdir), $(top_srcdir) and similar that could replace hard-coded prefixes such
as "../..".

Details: Please see the "Preset Output Variables" section in the autoconf manual.

-- 
Matthias Andree

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Dave Korn]

On 19/07/2010 16:29, Ryan McLeod wrote:
> I get the above error when I am trying to cross-compile openswan for
> cygwin as laid out here:
> http://www.cygwin.com/ml/cygwin/2005-08/msg00175.html
> 
> The only thing i do differently is:
> 
> ../../winsup/configure --prefix=/myprefix/cross
> --target=i686-pc-cygwin --without-headers \
> 
> --with-newlib --disable-shared --enable-languages=c,c++
> 
> changes to:
> 
> ../winsup/configure --prefix=/myprefix/xelerance/cross/win2k
> --target=i686-pc-cygwin --without-headers \
> 
> --with-newlib --disable-shared --enable-languages=c,c++
> 
> The prefix change is mentioned as that in the openswan documents, but
> considering i only go up one directory from winsup
> and into a build directory from there, not sure why he specified
> ../../winsup. I did have to copy install-sh, config.guess and

  It's bad advice.  Use an absolute path to configure, and be sure to build in
a directory that is parallel to (rather than a subdir of) the source tree.

> ../../winsup. I did have to copy install-sh, config.guess and
> config.sub into the winsup directory, as i was getting configure
> errors then with the install-sh. 

  That shouldn't be necessary either.  The top-level copies should be the only
ones.

    cheers,
      DaveK

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Ryan McLeod]

Thanks Dave,

In case anyone else has the issue, here's what i did:

Paths were /home/rmcleod/cygwin/winsup and /home/rmcleod/cygwin/build.
Copy an install-sh, config.guess and config.sub into
/home/rmcleod/cygwin. cd to build. Run:
/home/rmcleod/cygwin/winsup/configure \
--prefix=/myprefix/xelerance/cross/win2k --target=i686-pc-cygwin
--without-headers  --with-newlib \
--disable-shared  --enable-languages=c,c++

On Mon, Jul 19, 2010 at 12:53 PM, Dave Korn <dave.korn.cygwin@gmail.com> wrote:
> On 19/07/2010 16:29, Ryan McLeod wrote:
>> I get the above error when I am trying to cross-compile openswan for
>> cygwin as laid out here:
>> http://www.cygwin.com/ml/cygwin/2005-08/msg00175.html
>>
>> The only thing i do differently is:
>>
>> ../../winsup/configure --prefix=/myprefix/cross
>> --target=i686-pc-cygwin --without-headers \
>>
>> --with-newlib --disable-shared --enable-languages=c,c++
>>
>> changes to:
>>
>> ../winsup/configure --prefix=/myprefix/xelerance/cross/win2k
>> --target=i686-pc-cygwin --without-headers \
>>
>> --with-newlib --disable-shared --enable-languages=c,c++
>>
>> The prefix change is mentioned as that in the openswan documents, but
>> considering i only go up one directory from winsup
>> and into a build directory from there, not sure why he specified
>> ../../winsup. I did have to copy install-sh, config.guess and
>
>  It's bad advice.  Use an absolute path to configure, and be sure to build in
> a directory that is parallel to (rather than a subdir of) the source tree.
>
>> ../../winsup. I did have to copy install-sh, config.guess and
>> config.sub into the winsup directory, as i was getting configure
>> errors then with the install-sh.
>
>  That shouldn't be necessary either.  The top-level copies should be the only
> ones.
>
>    cheers,
>      DaveK
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Ryan McLeod]

Problems love me,

getting some make issues now when i run make in the build directory.

/usr/include/sys/select.h:78: error: conflicting types for 'fd_set'
/home/rmcleod/cygwin/winsup/w32api/lib/../include/winsock2.h:64 note:
previous declaration of 'fd_set' was here
/usr/include/sys/select.h:109: error: conflicting types for 'select'
/home/rmcleod/cygwin/winsup/w32api/lib/../include/winsock2.h632: note:
previous declaration of 'select' was here

I am doing this process on Ubuntu, as i believe thats how im supposed
to cross compile something for cygwin; do it from linux.

Thanks,

Ryan

On Mon, Jul 19, 2010 at 12:50 PM, Ryan McLeod <r.mcleod20@gmail.com> wrote:
> Thanks Dave,
>
> In case anyone else has the issue, here's what i did:
>
> Paths were /home/rmcleod/cygwin/winsup and /home/rmcleod/cygwin/build.
> Copy an install-sh, config.guess and config.sub into
> /home/rmcleod/cygwin. cd to build. Run:
> /home/rmcleod/cygwin/winsup/configure \
> --prefix=/myprefix/xelerance/cross/win2k --target=i686-pc-cygwin
> --without-headers  --with-newlib \
> --disable-shared  --enable-languages=c,c++
>
> On Mon, Jul 19, 2010 at 12:53 PM, Dave Korn <dave.korn.cygwin@gmail.com> wrote:
>> On 19/07/2010 16:29, Ryan McLeod wrote:
>>> I get the above error when I am trying to cross-compile openswan for
>>> cygwin as laid out here:
>>> http://www.cygwin.com/ml/cygwin/2005-08/msg00175.html
>>>
>>> The only thing i do differently is:
>>>
>>> ../../winsup/configure --prefix=/myprefix/cross
>>> --target=i686-pc-cygwin --without-headers \
>>>
>>> --with-newlib --disable-shared --enable-languages=c,c++
>>>
>>> changes to:
>>>
>>> ../winsup/configure --prefix=/myprefix/xelerance/cross/win2k
>>> --target=i686-pc-cygwin --without-headers \
>>>
>>> --with-newlib --disable-shared --enable-languages=c,c++
>>>
>>> The prefix change is mentioned as that in the openswan documents, but
>>> considering i only go up one directory from winsup
>>> and into a build directory from there, not sure why he specified
>>> ../../winsup. I did have to copy install-sh, config.guess and
>>
>>  It's bad advice.  Use an absolute path to configure, and be sure to build in
>> a directory that is parallel to (rather than a subdir of) the source tree.
>>
>>> ../../winsup. I did have to copy install-sh, config.guess and
>>> config.sub into the winsup directory, as i was getting configure
>>> errors then with the install-sh.
>>
>>  That shouldn't be necessary either.  The top-level copies should be the only
>> ones.
>>
>>    cheers,
>>      DaveK
>>
>> --
>> Problem reports:       http://cygwin.com/problems.html
>> FAQ:                   http://cygwin.com/faq/
>> Documentation:         http://cygwin.com/docs.html
>> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>>
>>
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Christopher Faylor]

On Mon, Jul 19, 2010 at 01:04:53PM -0400, Ryan McLeod wrote:
>Problems love me,
>
>getting some make issues now when i run make in the build directory.
>
>/usr/include/sys/select.h:78: error: conflicting types for 'fd_set'
>/home/rmcleod/cygwin/winsup/w32api/lib/../include/winsock2.h:64 note:
>previous declaration of 'fd_set' was here
>/usr/include/sys/select.h:109: error: conflicting types for 'select'
>/home/rmcleod/cygwin/winsup/w32api/lib/../include/winsock2.h632: note:
>previous declaration of 'select' was here
>
>I am doing this process on Ubuntu, as i believe thats how im supposed
>to cross compile something for cygwin; do it from linux.

Something is mixing windows header files with cygwin header files.  You
shouldn't be using winsock2.h in a cygwin program.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Ryan McLeod]

Can't say im trying to... I ran configure on winsup with some options:
/home/rmcleod/cygwin/winsu/configure \
--prefix=/myprefix/xelerance/cross/win2k --target=i686-pc-cygwin
--without-headers  --with-newlib \
--disable-shared  --enable-languages=c,c++

 then did make and those c errors came back.

I'm not a programmer, so not to sure what to do from here.

Thanks, Ryan

On Mon, Jul 19, 2010 at 1:07 PM, Christopher Faylor
<cgf-use-the-mailinglist-please@cygwin.com> wrote:
> On Mon, Jul 19, 2010 at 01:04:53PM -0400, Ryan McLeod wrote:
>>Problems love me,
>>
>>getting some make issues now when i run make in the build directory.
>>
>>/usr/include/sys/select.h:78: error: conflicting types for 'fd_set'
>>/home/rmcleod/cygwin/winsup/w32api/lib/../include/winsock2.h:64 note:
>>previous declaration of 'fd_set' was here
>>/usr/include/sys/select.h:109: error: conflicting types for 'select'
>>/home/rmcleod/cygwin/winsup/w32api/lib/../include/winsock2.h632: note:
>>previous declaration of 'select' was here
>>
>>I am doing this process on Ubuntu, as i believe thats how im supposed
>>to cross compile something for cygwin; do it from linux.
>
> Something is mixing windows header files with cygwin header files.  You
> shouldn't be using winsock2.h in a cygwin program.
>
> cgf
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Christopher Faylor]

On Mon, Jul 19, 2010 at 01:12:04PM -0400, Ryan McLeod wrote:
>Can't say im trying to... I ran configure on winsup with some options:
>/home/rmcleod/cygwin/winsu/configure \
>--prefix=/myprefix/xelerance/cross/win2k --target=i686-pc-cygwin
>--without-headers  --with-newlib \
>--disable-shared  --enable-languages=c,c++
>
> then did make and those c errors came back.
>
>I'm not a programmer,...

Then you may be in trouble.  You'll probably need to make some source
code changes to fix this.  Someone has made a bad decision about cygwin,
apparently thinking that it was like Windows rather than like UNIX.

As a very simple change you could just delete any calls to winsock2.h
to see if that fixes things but I suspect that it won't.  You could also
check to see if WIN32 or _WIN32 is being defined anywhere.  It shouldn't
be for Cygwin.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Ryan McLeod]

Got around to trying some of this again. I commented out some #include
<winsock2.h>, but eventually one file didnt like it and had a bunch of
unknown variables. I was reading through the emails and I did want to
specify that at this point I'm just trying to compile and install
winsup from the CVS cygwin server. I havent gotten to openswan yet.
Not sure if that helps to look for the root of the issue.

Ryan

On Mon, Jul 19, 2010 at 1:25 PM, Christopher Faylor
<cgf-use-the-mailinglist-please@cygwin.com> wrote:
> On Mon, Jul 19, 2010 at 01:12:04PM -0400, Ryan McLeod wrote:
>>Can't say im trying to... I ran configure on winsup with some options:
>>/home/rmcleod/cygwin/winsu/configure \
>>--prefix=/myprefix/xelerance/cross/win2k --target=i686-pc-cygwin
>>--without-headers  --with-newlib \
>>--disable-shared  --enable-languages=c,c++
>>
>> then did make and those c errors came back.
>>
>>I'm not a programmer,...
>
> Then you may be in trouble.  You'll probably need to make some source
> code changes to fix this.  Someone has made a bad decision about cygwin,
> apparently thinking that it was like Windows rather than like UNIX.
>
> As a very simple change you could just delete any calls to winsock2.h
> to see if that fixes things but I suspect that it won't.  You could also
> check to see if WIN32 or _WIN32 is being defined anywhere.  It shouldn't
> be for Cygwin.
>
> cgf
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Christopher Faylor]

On Tue, Jul 27, 2010 at 11:22:13AM -0400, Ryan McLeod wrote:
>Got around to trying some of this again. I commented out some #include
><winsock2.h>, but eventually one file didnt like it and had a bunch of
>unknown variables. I was reading through the emails and I did want to
>specify that at this point I'm just trying to compile and install
>winsup from the CVS cygwin server.

At the risk of annoying the open source zealots among us, I have to ask:
Why?  There is no need to build "winsup" when you're trying to build
some other package.  That is definitely not a prerequiste.  All of the
files that you need to build packages are already part of the cygwin
release.  You can't avoid downloading them if you have a working cygwin
installation.

>I havent gotten to openswan yet.  Not sure if that helps to look for
>the root of the issue.

Actually, no, it just confuses things.  The problems that you're seeing
are likely do to some bad decisions that are being made in the openswan
code.  You don't need cygwin source code to deal with that.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Ryan McLeod]

The reason for it, was I initially had issues trying to install
openswan into cygwin. Openswan is supposed to support installation on
cygwin. I was then instructed to cross compile openswan for cygwin on
linux to try and get it to work. And i was told to look at the
cross-compiler doc in the openswan package on how to do that. Which
told me to get winsup and build it so I would have a compiler on Linux
to build openswan for cygwin. But thats when i ran into the issues
above.

You mention packages that come with a cygwin installation to compile a
program to be used on cygwin. Mind giving me a rough idea on how to do
that?

Thanks,

Ryan

On Tue, Jul 27, 2010 at 3:04 PM, Christopher Faylor
<cgf-use-the-mailinglist-please@cygwin.com> wrote:
> On Tue, Jul 27, 2010 at 11:22:13AM -0400, Ryan McLeod wrote:
>>Got around to trying some of this again. I commented out some #include
>><winsock2.h>, but eventually one file didnt like it and had a bunch of
>>unknown variables. I was reading through the emails and I did want to
>>specify that at this point I'm just trying to compile and install
>>winsup from the CVS cygwin server.
>
> At the risk of annoying the open source zealots among us, I have to ask:
> Why?  There is no need to build "winsup" when you're trying to build
> some other package.  That is definitely not a prerequiste.  All of the
> files that you need to build packages are already part of the cygwin
> release.  You can't avoid downloading them if you have a working cygwin
> installation.
>
>>I havent gotten to openswan yet.  Not sure if that helps to look for
>>the root of the issue.
>
> Actually, no, it just confuses things.  The problems that you're seeing
> are likely do to some bad decisions that are being made in the openswan
> code.  You don't need cygwin source code to deal with that.
>
> cgf
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: configure error: cannot find install-sh or install.sh in ../.. "../../winsup/cygwin"/../..

[Christopher Faylor]

On Tue, Jul 27, 2010 at 03:53:32PM -0400, Ryan McLeod wrote:
>The reason for it, was I initially had issues trying to install
>openswan into cygwin. Openswan is supposed to support installation on
>cygwin. I was then instructed to cross compile openswan for cygwin on
>linux to try and get it to work. And i was told to look at the
>cross-compiler doc in the openswan package on how to do that. Which
>told me to get winsup and build it so I would have a compiler on Linux
>to build openswan for cygwin. But thats when i ran into the issues
>above.

Ok.  Sorry that I haven't been paying attention.  It seems like very bad
advice to suggest that someone cross-build a cygwin application from
linux.  It doesn't make a lot of sense.

>You mention packages that come with a cygwin installation to compile a
>program to be used on cygwin. Mind giving me a rough idea on how to do
>that?

If you want to build on/for cygwin then you need to download things like
gcc, make, binutils and probably other things that I haven't thought of.

There was a recent discussion about this:

http://cygwin.com/ml/cygwin/2010-07/msg00358.html

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple