On Thu, Mar 1, 2012 at 11:22 PM, Kanu <[email protected]> wrote:
> >
> Started by user anonymous
> Building in workspace C:\Program Files\Jenkins\workspace\Helloworld
> [Helloworld] $ C:\cygwin\bin\bash -xe C:\WINDOWS\TEMP
> \hudson8960933788009414142.sh
> cygwin warning:
> MS-DOS style path detected: C:\WINDOWS\TEMP
> \hudson8960933788009414142.sh
> Preferred POSIX equivalent is: /cygdrive/c/WINDOWS/TEMP/
> hudson8960933788009414142.sh
> CYGWIN environment variable option "nodosfilewarning" turns off this
> warning.
> Consult the user's guide for more details about POSIX paths:
> http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
> + c:/cygwin/bin/bash -xe c:/test/build.sh
> + c:/cygwin/bin/gcc -c helloworld.c
> /usr/lib/gcc/i686-pc-cygwin/4.5.3/cc1.exe: error while loading shared
> libraries: ?: cannot open shared object file: No such file or
> directory
> Build step 'Execute shell' marked build as failure
> Finished: FAILURE
When you start cygwin from the usual console batch file it runs bash
with the --login -i options which, among other things will make it
source /etc/profile to set many environment variables (PATH, etc.)
that you won't have otherwise.
--
Les Mikesell
[email protected]
