On 03/09/2015 09:37, Hari Narasimhan H.N wrote:
configure:8591: checking whether the C compiler works
configure:8613: gcc -m32 -O2 -pedantic -fomit-frame-pointer conftest.c >&5
/usr/lib/gcc/i686-pc-cygwin/4.9.3/../../../../i686-pc-cygwin/bin/ld:
cannot open output file a.exe: Permission denied
-'
bindir='${exec_prefix}/bin'
build='coreiwsm-pc-cygwin'
build_alias=''
build_cpu='coreiwsm'
build_os='cygwin'
build_vendor='pc'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${data
Hi,
An error shows up while running ./confiugre while building GMP on cygwin
"configure: error: could not find a working compiler"
I have a cygwin environment with gcc4.9.3 installed and working fine.
Thanks and Regards,
Hari
--
Problem reports: http://cygwin.com/problem
Hi,
I got the following error in configuring GMP while building a bare
metal GNU cross toolchain for Xtensa on cygwin
configure: error: could not find a working compiler, see config.log for details
The build was performed using a crosstool-NG downloaded from the site
http://wiki.linux
> Add "CPPFLAGS=-I/usr/include/tirpc" to your configure flags.
now found it, thanks for the tip again.
Gery
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.h
.
checking rpc/rpc.h usability... no
checking rpc/rpc.h presence... no
checking for rpc/rpc.h... no
checking rpc/types.h usability... no
checking rpc/types.h presence... no
checking for rpc/types.h... no
configure: error: Required header not found, check include path
and intsalled devel pac
https://cygwin.com/acronyms/#PCYMTWLL !
On Mon, 2015-05-18 at 19:17 +, Gery . wrote:
> I received a SUNRPC error after running ./configure on version
> 5.4.2220 in Cygwin (CYGWIN_NT-6.3-WOW64 gery 1.7.32(0.274/5/3)
> 2014-08-13 23:03 i686 Cygwin), here it is:
>
> c
Hello,
I received a SUNRPC error after running ./configure on version 5.4.2220 in
Cygwin (CYGWIN_NT-6.3-WOW64 gery 1.7.32(0.274/5/3) 2014-08-13 23:03 i686
Cygwin), here it is:
configure: error: Required header not found, check include
path and intsalled devel packages
SUNRPC (as well as
On 12/08/2014 07:41, Philipp wrote:
When it comes to
./configure --prefix=$ROOTSYS
however, I get following error message:
configure:3985: error: C compiler cannot create executables
See `config.log' for more details
This is a complete shot in the dark, but are you perchance using Norton
An
On 12/08/2014 08:41, Philipp wrote:
I'm trying to install 'musrfit' on cygwin following these
(http://lmu.web.psi.ch/musrfit/user/MUSR/MusrFitSetup.html#A_4_MS_Windows)
instructions. When it comes to
./configure --prefix=$ROOTSYS
however, I get following error message:
configure:3985: error:
I'm trying to install 'musrfit' on cygwin following these
(http://lmu.web.psi.ch/musrfit/user/MUSR/MusrFitSetup.html#A_4_MS_Windows)
instructions. When it comes to
./configure --prefix=$ROOTSYS
however, I get following error message:
configure:3985: error: C compiler cannot create executables
gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... configure: error:
C compiler cannot create executables
See `config.log' for more details.
the config log is displayed below
g for C compiler default output file name
conf
g for gcc... gcc
checking for C compiler default output file name... configure: error:
C compiler cannot create executables
See `config.log' for more details.
the config log is displayed below
This file contains any messages produced by compilers while
running configure, to aid debugging if
On Wednesday, August 29, 2012 2:43 PM , Diego García Medina wrote:
>I can´t compile packages because of this error:
>checking for perl... /usr/bin/perl
>checking for perl >= 5.8.1... 5.14.2
>checking for XML::Parser... configure: error: XML::Parser perl module is
>required for
I can´t compile packages because of this error:
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.14.2
checking for XML::Parser... configure: error: XML::Parser perl module is
required for intltool
I tried to fix it by means of setup.exe and manually installing perl rela
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 wor
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 opensw
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
>, 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 jus
Got around to trying some of this again. I commented out some #include
, 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
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 --ena
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.
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:
>prev
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:
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/xeleran
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=
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 ../.. &qu
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/
Doc
David Rothenberger wrote:
> Although the former and current values look the same, the former
> value actually has two trailing spaces while the current value has
> only one. The attached patch solves the problem for me, but I doubt
> it is the appropriate way to fix this. Is there a better way?
T
/ -isystem
/netrel/build/cygwin/i686-pc-cygwin/newlib/targ-include -isystem
/netrel/src/cygwin/newlib/libc/include' 'LDFLAGS=' 'build_alias=i686-pc-cygwin'
'host_alias=i686-pc-cygwin' 'target_alias=i686-pc-cygwin'
--cache-file=.././config.cache --srcdir=/netrel/src/c
On 06 July 2006 21:57, Brian Dessent wrote:
> Bhagwan Anjanappa wrote:
>
>> conftest.c 1>&5 gcc: installation problem, cannot exec `as': No such
>> file or directory configure: failed program was:
>
> Binutils contains the assembler (as) which is required to use gcc. Your
> problem therefore i
Bhagwan Anjanappa wrote:
>My apologies to one and all for not being specific in my previous
> mail. Well having said that, I am using Win 2000 and when I try to
> configure httperf tool on Cygwin the command I give is as below
> however my Cygwin tool and httperf tool are installed on sape
Hard disk.
$ D:/.../http/test/httperf-0.8/configure
after this the error I get is as follows:
loading cache ./config.cache
checking for gcc... gcc
checking wether the C compiler works. no
configure: error: installation or configuration problem: C compiler
cannot create executables
when I
error
comming up whenever I try to run the configure command It says like
below
loading cache ./config.cache
checking for gcc... gcc
checking wether the C compiler works. no
configure: error: installation or configuration problem: C compiler
cannot create executables
I'm not familiar
try to run the configure command It says like
below
loading cache ./config.cache
checking for gcc... gcc
checking wether the C compiler works. no
configure: error: installation or configuration problem: C compiler
cannot create executables
I am in a fix and my work is held up as I cannot get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to CODE on 8/4/2005 7:29 AM:
> checking for C compiler default output... configure: error: C compiler
> cannot cr
> eate executables
> See `config.log' for more details.
Did you look at config.log? Since you didn
stem type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler
cannot cr
eate executables
See `config.log' for more details.
My setup details after installing cygwin is enclosed in a
All,
Discussions of various configure-related errors on the list today
reminded me of something I ran into last week when trying to rebuild
the cygwin DLL.
After syncing with CVS, the configure stage of a clean rebuild
results in the following error. Source has been checked out
into src, configu
Gerrit wrote:
> Peter wrote:
>
> >> The last time I tried to build ggi-project failed with compilation
> >> errors. That probably means that I was able to configure it
> >> or parts of
> >> it.
>
> > I have spent some time on getting libggi working. I believe
> it does work
> > now, you have
Peter wrote:
>> The last time I tried to build ggi-project failed with compilation
>> errors. That probably means that I was able to configure it
>> or parts of
>> it.
> I have spent some time on getting libggi working. I believe it does work
> now, you have to use the cvs version though as the
> The last time I tried to build ggi-project failed with compilation
> errors. That probably means that I was able to configure it
> or parts of
> it.
I have spent some time on getting libggi working. I believe it does work
now, you have to use the cvs version though as the released versions do
ome lines from the shell:
> ~/ggi-cygwin/libgii$ ../../ggi3/ggi-core/libgii/configure --prefix=/usr
> -C --with-extra-includes=/cygdrive/c/dx9csdk/include
> configure: error: invalid package name: extra-includes
> ~/ggi-cygwin/libgii$ ../../ggi3/ggi-core/libgii/configure --prefix=/u
I wrote:
> ~/ggi-cygwin/libgii$ ../../ggi3/ggi-core/libgii/configure
> --prefix=/usr
> -C --with-extra-includes=/cygdrive/c/dx9csdk/include
> configure: error: invalid package name: extra-includes
> ~/ggi-cygwin/libgii$ ../../ggi3/ggi-core/libgii/configure
> --prefix=/usr
$ ../../ggi3/ggi-core/libgii/configure --prefix=/usr
-C --with-extra-includes=/cygdrive/c/dx9csdk/include
configure: error: invalid package name: extra-includes
~/ggi-cygwin/libgii$ ../../ggi3/ggi-core/libgii/configure --prefix=/usr
-C --with-extra-includes=/cygdrive/c/dx9csdk/include
configure
Hallo linda,
Am Samstag, 6. Dezember 2003 um 23:15 schriebst du:
> I'm guessing I don't have something setup quite correctly. I'm trying
> to build the dictd package under cygwin.
There are problems with fork() in this code, I was not able to run
dictd as a daemon.
> it uses configure, but co
I'm guessing I don't have something setup quite correctly. I'm trying
to build the dictd package
under cygwin.
it uses configure, but configure starts out with an error.
checking host system type...
Invalid configuration `i686-pc-cygwin': system `cygwin' not recognized
---
Is this something
> From: Brian Ford
> Sent: Monday, October 13, 2003 8:49 PM
> On Sun, 12 Oct 2003, Hannu E K Nevalainen wrote:
>
> > Sigh - yes, or even better; the FAQ stating that there should
> be a configure
> > script in the root dir after the checkout - as it depends on it beeing
> > there - i.e. "You shoul
On Sun, 12 Oct 2003, Hannu E K Nevalainen wrote:
> Sigh - yes, or even better; the FAQ stating that there should be a configure
> script in the root dir after the checkout - as it depends on it beeing
> there - i.e. "You should now have a /src/configure script. Run it like
> this:".
>
Do you reall
On Sat, 11 Oct 2003, Micha Nelissen wrote:
> Nelissen, M. wrote:
>
> > This is exactly the same as mine! (Without the --enable-debug). So my
> > configure script itself is broken? Could it be my version of
> > autoconf/automake or outdated or broken?
>
> This was indeed the case. I ran cygwin setu
I recently downloaded Cygwin from cygwin.com, and everything
seems to be working fine.
Now when I try to compile any software using configure/make
routine, I keep getting the following error:
configure: error: installation or configuration problem:
C++ compiler cannot create executables
[snip]
> Once again, I'm not *trying* to get you into this mood.
Chris pretty much lives in that mood.
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs
> From: Christopher Faylor
> Sent: Sunday, October 12, 2003 12:04 AM
This is long and winding, not entirely on topic - you've been warned.
> On Sat, Oct 11, 2003 at 11:38:36PM +0200, Hannu E K Nevalainen wrote:
> > =-) Well, eventually it did work with the root level configure.
> >The reason I
On Sat, Oct 11, 2003 at 11:38:36PM +0200, Hannu E K Nevalainen wrote:
>> From: Igor Pechtchanski
>> Sent: Saturday, October 11, 2003 9:14 PM
>
>> > Simply "cvs co winsup; mkdir ../build; cd ../build;
>> > ../src/winsup/configure --prefix=/usr/install --enable-debugging -v;
>> > make", and you shoul
> From: Igor Pechtchanski
> Sent: Saturday, October 11, 2003 9:14 PM
> > Simply "cvs co winsup; mkdir ../build; cd ../build;
> > ../src/winsup/configure --prefix=/usr/install --enable-debugging -v;
> > make", and you should be good to go. If you need to do anything else,
> > it's a bug.
>
> Umm,
On Sat, 11 Oct 2003, Igor Pechtchanski wrote:
> On Sat, 11 Oct 2003, Hannu E K Nevalainen wrote:
>
> > > On Fri, 10 Oct 2003, Hannu E K Nevalainen wrote:
> > >
> > > > $ cvs -z3 co winsup
> > > >
> > > This gives you everything you need. I just tested it.
>
> [snip]
> Simply "cvs co winsup; mkdi
On Sat, 11 Oct 2003, Hannu E K Nevalainen wrote:
> > On Fri, 10 Oct 2003, Hannu E K Nevalainen wrote:
> >
> > > $ cvs -z3 co winsup
> > >
> > This gives you everything you need. I just tested it.
>
> It didn't at the time when I was doing it, as cgf pointed out in another
> posting. YAO
>
> > >
i686-pc-cygwin/libiberty
configure: error: invalid package name: target-subdir
make[1]: *** [configure-target-libiberty] Error 1
make[1]: Leaving directory `/obj'
Done.
... I have not looked into it yet.
Well this is *EXACTLY* my original problem. See my original post,
*sigh*. Now read my latest
roblems:
/bin/sh ../src/mkinstalldirs i686-pc-cygwin/libiberty ; \
rm -f i686-pc-cygwin/libiberty/Makefile || : ; \
cp multilib.out i686-pc-cygwin/libiberty/multilib.out
mkdir -p -- i686-pc-cygwin/libiberty
Configuring in i686-pc-cygwin/libiberty
configure: error: invalid package name: target-subdi
Nelissen, M. wrote:
This is exactly the same as mine! (Without the --enable-debug). So my
configure script itself is broken? Could it be my version of
autoconf/automake or outdated or broken?
This was indeed the case. I ran cygwin setup again and did some messing
with automake/autoconf. I turne
> From: Brian Ford
> Sent: Saturday, October 11, 2003 12:05 AM
> Sorry Hannu, I meant to send this to the list instead of you personally.
As long as the intention is good ;-) - no problem.
I post this reply to show on the amount of problems there seems to be to
follow the instructions that are
Hannu E K Nevalainen wrote:
$ grep -n w32api make.log | grep -i configure
1673:running /bin/sh
./../../../winsup/w32api/configure --host=i686-pc-cygwin --build=i686-pc-cy
gwin --with-newlib --enable-multilib --prefix=/install --enable-debug -v --p
rogram-transform-name=s,y,y, --with-target-subdi
On Fri, Oct 10, 2003 at 05:04:59PM -0500, Brian Ford wrote:
>Sorry Hannu, I meant to send this to the list instead of you personally.
>
>On Fri, 10 Oct 2003, Hannu E K Nevalainen wrote:
>
>> $ cvs -z3 co winsup
>>
>This gives you everything you need. I just tested it.
That's because I just fixed
Sorry Hannu, I meant to send this to the list instead of you personally.
On Fri, 10 Oct 2003, Hannu E K Nevalainen wrote:
> $ cvs -z3 co winsup
>
This gives you everything you need. I just tested it.
> To get the cvs /src level stuff (configure among other things) I did
> $ cvs -z3 co .
>
> and
> From: Micha Nelissen
> Sent: Friday, October 10, 2003 10:42 PM
> Here it still breaks on configure, but this time in winsup/w32api. It
> tries to feed the configure script:
> '--with-target-subdir=i686-pc-cygwin' but it doesn't recognize option
> target-subdir: 'invalid package name: target-subd
Hannu E K Nevalainen wrote:
Building the cvs version of the cygwin dll "OOTB" seems to be a no-no
currently.
$ export CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs/src
$ cvs login
passwd: anoncvs
$ cvs -z3 co winsup
To get the cvs /src level stuff (configure among other things) I did
$ cvs -z3 co .
and
> From: Christopher Faylor
> Sent: Friday, October 10, 2003 9:27 PM
> On Fri, Oct 10, 2003 at 09:10:03PM +0200, Hannu E K Nevalainen wrote:
> >> From: Micha Nelissen
> >> Sent: Friday, October 10, 2003 2:58 PM
> >
> >> Hi,
> >>
> >> Can somebody help me with this problem while making cygwin:
> >>
Building the cvs version of the cygwin dll "OOTB" seems to be a no-no
currently.
$ export CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs/src
$ cvs login
passwd: anoncvs
$ cvs -z3 co winsup
To get the cvs /src level stuff (configure among other things) I did
$ cvs -z3 co .
and then hit CTRL-C when it
Hannu E K Nevalainen wrote:
From: Micha Nelissen
Sent: Friday, October 10, 2003 2:58 PM
May I guess that you did the same as I did, i.e. follow the instructions on
cvs page... Then you need THIS information too:
I used the "How do I rebuild the tools on my NT box?" instructions. I
have installe
On Fri, Oct 10, 2003 at 09:10:03PM +0200, Hannu E K Nevalainen wrote:
>> From: Micha Nelissen
>> Sent: Friday, October 10, 2003 2:58 PM
>
>> Hi,
>>
>> Can somebody help me with this problem while making cygwin:
>>
>
>>
>> Any hints appreciated!
>>
>> Micha.
>>
>
>May I guess that you did the same a
> From: Micha Nelissen
> Sent: Friday, October 10, 2003 2:58 PM
> Hi,
>
> Can somebody help me with this problem while making cygwin:
>
>
> Any hints appreciated!
>
> Micha.
>
May I guess that you did the same as I did, i.e. follow the instructions on
cvs page... Then you need THIS information t
creating Makefile
Configuring in i686-pc-cygwin/libiberty
configure: error: invalid package name: target-subdir
make: *** [configure-target-libiberty] Error 1
Any hints appreciated!
Micha.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
On Thu, 17 Jul 2003, Rafael Jimenez wrote:
> Dear list,
>
> I am encountering some problems when building xpdf-0.92 under cygwin.
> I built the t1lib libraries, and installed in /usr/local/lib/ and
> /usr/local/include/. However, it seems that the ./configure script
> doesn't find them, even thoug
Dear list,
I am encountering some problems when building xpdf-0.92 under cygwin.
I built the t1lib libraries, and installed in /usr/local/lib/ and
/usr/local/include/. However, it seems that the ./configure script
doesn't find them, even though I include the specific path to them:
The libraries e
72 matches
Mail list logo