On 16 March 2006 09:28, Deepa Mahajan wrote:
> When I try to execute the make command. I get the following errors
>
> $ make
> make[1]: Entering directory `/home/Deepa/
> gcc -o ../bin/m1210.exe m1210.o Deepa.a -lm -lc -lz -ltcl -ltk
> fu01.o:: undefined reference to `_libc_iname'
> fu02
When I try to execute the make command. I get the following errors
$ make
make[1]: Entering directory `/home/Deepa/
gcc -o ../bin/m1210.exe m1210.o Deepa.a -lm -lc -lz -ltcl -ltk
fu01.o:: undefined reference to `_libc_iname'
fu02.o:: undefined reference to `_libc_iname'
fu03.o:: undef
On Sun, May 08, 2005 at 08:21:26PM -0400, Christopher Faylor wrote:
>Shouldn't we be able to just mount the */bin variant which is used by
>default, though? Is that /usr/bin? That would catch the most common
>cases without using up precious mount table slots. It would not catch
>the case of some
On Sun, May 08, 2005 at 08:02:17PM -0400, Igor Pechtchanski wrote:
>On Sun, 8 May 2005, Christopher Faylor wrote:
>
>> On Sun, May 08, 2005 at 04:11:08PM -0400, Igor Pechtchanski wrote:
>> >On Sun, 8 May 2005, Joshua Daniel Franklin wrote:
>> >
>> >> > >On 5/6/05, J?rgen Havsberg Seland wrote:
>> >
On Sun, 8 May 2005, Christopher Faylor wrote:
> On Sun, May 08, 2005 at 04:11:08PM -0400, Igor Pechtchanski wrote:
> >On Sun, 8 May 2005, Joshua Daniel Franklin wrote:
> >
> >> > >On 5/6/05, J?rgen Havsberg Seland wrote:
> >> > >> This problem is (often) due to the command-line being to long for t
On Sun, May 08, 2005 at 04:11:08PM -0400, Igor Pechtchanski wrote:
>On Sun, 8 May 2005, Joshua Daniel Franklin wrote:
>
>> > >On 5/6/05, J?rgen Havsberg Seland wrote:
>> > >> This problem is (often) due to the command-line being to long for the
>> > >> windows execution model. To circumvent this, m
On Sun, May 08, 2005 at 12:48:00PM -0700, Joshua Daniel Franklin wrote:
>> >On 5/6/05, J?rgen Havsberg Seland wrote:
>> >> This problem is (often) due to the command-line being to long for the
>> >> windows execution model. To circumvent this, mount the path of the
>> >> executable using the -X swi
On Sun, 8 May 2005, Joshua Daniel Franklin wrote:
> > >On 5/6/05, Jørgen Havsberg Seland wrote:
> > >> This problem is (often) due to the command-line being to long for the
> > >> windows execution model. To circumvent this, mount the path of the
> > >> executable using the -X switch. For instance
> >On 5/6/05, Jørgen Havsberg Seland wrote:
> >> This problem is (often) due to the command-line being to long for the
> >> windows execution model. To circumvent this, mount the path of the
> >> executable using the -X switch. For instance, use
> >
> On Sat, May 07, 2005 at 05:11:39PM -0700, Joshu
On Sat, May 07, 2005 at 05:11:39PM -0700, Joshua Daniel Franklin wrote:
>On 5/6/05, J?rgen Havsberg Seland wrote:
>> This problem is (often) due to the command-line being to long for the
>> windows execution model. To circumvent this, mount the path of the
>> executable using the -X switch. For ins
On 5/6/05, Jørgen Havsberg Seland wrote:
> This problem is (often) due to the command-line being to long for the
> windows execution model. To circumvent this, mount the path of the
> executable using the -X switch. For instance, use
I don't mind adding an FAQ, it looks like it's been asked few ti
On Fri, May 06, 2005 at 11:47:42PM +0200, J?rgen Havsberg Seland wrote:
>[This posting is to provide future searchers with a direct hit.]
>
>This problem is (often) due to the command-line being to long for the
>windows execution model. To circumvent this, mount the path of the
>executable using
At 05:47 PM 5/6/2005, you wrote:
>[This posting is to provide future searchers with a direct hit.]
>
>This problem is (often) due to the command-line being to long for the windows
>execution model. To circumvent this, mount the path of the executable using
>the -X switch. For instance, use
>
>mou
[This posting is to provide future searchers with a direct hit.]
This problem is (often) due to the command-line being to long for the
windows execution model. To circumvent this, mount the path of the
executable using the -X switch. For instance, use
mount -f -X c:/cygwin/bin /bin
to enable "cy
On Tue, 8 Jun 2004, santhosh km wrote:
> Hi,
>
> I am trying porting of c files to VxWorks thru cygwin
> using the GNU-Make Version 3.80 .
> I have a problem while using makefile. The problem is
> the commond:
> "ccsimpc -o HELLO_WORLD helloWorld.c"
> works on the command line and I get the
Hi,
I am trying porting of c files to VxWorks thru cygwin
using the GNU-Make Version 3.80 .
I have a problem while using makefile. The problem is
the commond:
"ccsimpc -o HELLO_WORLD helloWorld.c"
works on the command line and I get the HELLO_WORLD
executable file.
But doesn't work thru ma
At 10:19 AM 3/29/2004, you wrote:
>Larry Hall wrote:
>>
>>>Got a SIGCHLD; 1 unreaped children.
>>>Reaping winning child 0x108b3a20 PID 1288
>>>Removing child 0x108b3a20 PID 1288 from chain.
>>> Successfully remade target file `some_path/GUI_Module.lib_ar'.
>>>Finished prerequisites of target
Larry Hall wrote:
> At 03:39 AM 3/29/2004, Ingmar Sittl wrote:
>
>>Larry Hall wrote:
>>
>>>At 12:38 PM 3/26/2004, Ingmar Sittl wrote:
>>>
>>>
Hello,
With all cygwin-versions starting with 1.5.7 (including the snapshot
20040322) I experience major problems with make, leading to a m
At 03:39 AM 3/29/2004, Ingmar Sittl wrote:
>Larry Hall wrote:
>> At 12:38 PM 3/26/2004, Ingmar Sittl wrote:
>>
>>>Hello,
>>>
>>>With all cygwin-versions starting with 1.5.7 (including the snapshot
>>>20040322) I experience major problems with make, leading to a major (>
>>>20x) increase in the tim
Larry Hall wrote:
> At 12:38 PM 3/26/2004, you wrote:
>
>>Hello,
>>
>>With all cygwin-versions starting with 1.5.7 (including the snapshot
>>20040322) I experience major problems with make, leading to a major (>
>>20x) increase in the time make needs for a specific single target in our
>>project m
At 12:38 PM 3/26/2004, you wrote:
>Hello,
>
>With all cygwin-versions starting with 1.5.7 (including the snapshot
>20040322) I experience major problems with make, leading to a major (>
>20x) increase in the time make needs for a specific single target in our
>project make system (which is quite co
Hello,
With all cygwin-versions starting with 1.5.7 (including the snapshot
20040322) I experience major problems with make, leading to a major (>
20x) increase in the time make needs for a specific single target in our
project make system (which is quite complex, includes >100 sub-makefiles
and i
, 2002 6:26 PM
To: Godson Retna
Cc: Cygwin; Pgsql-Cygwin
Subject: Re: Make-Problem Postgres on Cygwin
Godson,
On Tue, Nov 26, 2002 at 02:10:45PM +0530, Godson Retna wrote:
>
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/
include -I/usr/local/include -DBUILDING_DLL=1
Godson,
On Tue, Nov 26, 2002 at 02:10:45PM +0530, Godson Retna wrote:
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/include
>-I/usr/local/include -DBUILDING_DLL=1 -c -o ipc.o ipc.c
> cc1: warning: changing search order for system directory "/usr/local/include"
> c
cygdrive/e/postgresql-7.2.1/src
$
[end
quote]==
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Jason Tishler
Sent: Friday, November 22, 2002 7:51 PM
To: Tarabas
Cc: Cygwin
Manuel,
Sigh...
Repeat after me:
Post instead of sending private email.
Keep replies on-list.
Post instead of sending private email.
Keep replies on-list.
...
On Fri, Nov 22, 2002 at 06:48:39PM +0100, Tarabas wrote:
> Thanks a lot for your help! The "make" and "make inst
Manuel,
Please post instead of sending private email. However, your timing is
impeccable. I just got around (yesterday) to building PostgreSQL under
the latest Cygwin gcc2 and gcc packages.
On Fri, Nov 22, 2002 at 01:23:48PM +0100, Tarabas wrote:
> I read your thread abut problems installing Po
Hi!
> If the options to allow case-insensitive globbing are present, all you
> have to do is turn them on (using the MAKEFLAGS environment variable
> for make, and the appropriate .*rc file for the shell, IIRC).
I see. I'll try to find this option.
> If these options are not available, there are
Eventually, a gratefully accepted patch to the
User's Manual (or FAQ) will be submitted that
includes Igor Pechtchanski's detailed explanation,
and we'll be able to simply point questioners
to it with a URL.
> > Zoltan Graff
>
> Please keep replies on-list. Thanks.
>
> Zoltan,
>
> In the Windo
On Thu, 31 Oct 2002, Harig, Mark A. wrote:
> try:
>
> %.D: %.C
>
> or
>
> %.d: %.C
>
> > -Original Message-
> > From: Graff_Zoltan [mailto:zotyo@;z1.fszek.hu]
> > Sent: Thursday, October 31, 2002 5:24 AM
> > To: Harig, Mark A.
> > Subj
try:
%.D: %.C
or
%.d: %.C
> -Original Message-
> From: Graff_Zoltan [mailto:zotyo@;z1.fszek.hu]
> Sent: Thursday, October 31, 2002 5:24 AM
> To: Harig, Mark A.
> Subject: Re: RE: MAKE - problem with small/capital letters in
> filenames
>
>
> > $ l
> -Original Message-
> From: Graff_Zoltan [mailto:zotyo@;z1.fszek.hu]
> Sent: Tuesday, October 29, 2002 6:05 AM
> To: [EMAIL PROTECTED]
> Subject: MAKE - problem with small/capital letters in filenames
>
>
> Hi!
>
> I've got a simple makefile. It wo
Hi!
I've got a simple makefile. It works well under DOS (with DJGPP) and
under Linux (Debian Woody). But it does not work under Cygwin.
The message: no rule to make 'hello.d'
The makefile:
all:
$(CC) $(CFLAGS) hello.c -o hello.exe
include hello.d
%.d: %.c
@ $(CC) -MM $(CFLAGS) $
This is an inidcation that c++.exe is not in the list
of paths of your PATH environment variable.
"JOSE (GRI)" wrote:
>
> Hi:
>
> I have got an environment problem with make:
>
> D: \make -f mcyg32
>
> c++.exe -c /comun/src/cacheb.cpp -o /client/mcc_cyg/debg/cacheb.obj
> -DLIBRERIA -
> DDOS_S
Hi:
I have got an environment problem with make:
D: \make -f mcyg32
c++.exe -c /comun/src/cacheb.cpp -o /client/mcc_cyg/debg/cacheb.obj
-DLIBRERIA -
DDOS_SOURCE -DPRCIO -DVTREE=86 -DCOMPILADOR -DINTERPRETE -DCOM -D__386__
-D__NT_
_ -I/client/src -I/comun/src -I/cygwin/usr/include/mingw
-I/cygwi
35 matches
Mail list logo
