Guenther Sohler posted a signature three times longer than his message:
Yike! Please use a MUCH shorter signature. Preferably one without
unenforceable (and, according to Eric Blake and CGF, against ML policy)
disclaimers, and you might want to reconsider feeding the spammers as well.
See http
On Tue, Jul 11, 2006 at 05:55:32PM +0100, Dave Korn wrote:
>On 11 July 2006 16:48, Guenther Sohler wrote:
>
>> Dear Dave,
>>
>> thank you for your answer.
>>
>> I did not answer to the newsgroup before, because I just forgot the command
>> to use. but the newgroup probably did not accidently dele
On 11 July 2006 16:48, Guenther Sohler wrote:
> Dear Dave,
>
> thank you for your answer.
>
> I did not answer to the newsgroup before, because I just forgot the command
> to use. but the newgroup probably did not accidently delete the mail :)
>
>
> Please find attached the output of cygcheck.
Dear Dave,
thank you for your answer.
I did not answer to the newsgroup before, because I just forgot the command to
use. but the newgroup probably did not accidently delete the mail :)
Please find attached the output of cygcheck.
rds
> Can't think of a witty .sigline today
--
Guenther
On 11 July 2006 11:02, Guenther Sohler wrote:
> Hallo Dave,
Hi Guenther,
> I already tried so, but I was not able to see the problem from the output.
>
> it is:
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/cc1.exe -quiet -v -D__GNUC__=3
> -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=3 -D__CYGWIN32__
Hallo Dave,
thank you for your answer.
I already tried so, but I was not able to see the problem from the output.
it is:
Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/specs
Configured with: /gcc/gcc-3.3.3-3/configure --verbose --prefix=/usr --exec-prefi
x=/usr --sysconfdir=/etc --li
On 11 July 2006 08:21, Guenther Sohler wrote:
> Hallo,
>
> I have downloaded the lastest version cygwin yesterday, and wanted to use
> gcc. Unfortunately no success.
> I do a small test file a.c with just a simple main function and i type
>
> gcc -c a.c
>
> But there is no object file created.
On Thu, Jun 09, 2005 at 06:26:59PM -0400, Igor Pechtchanski wrote:
>On Thu, 9 Jun 2005, Christopher Faylor wrote:
>
>> On Thu, Jun 09, 2005 at 11:31:23PM +0200, Gerrit P. Haase wrote:
>> >>Oh, I'm sorry. I think I see. There are some gcc-mingw-* packages
>> >>after 20040822-1 that fix the problem
On Thu, 9 Jun 2005, Christopher Faylor wrote:
> On Thu, Jun 09, 2005 at 11:31:23PM +0200, Gerrit P. Haase wrote:
> >>Oh, I'm sorry. I think I see. There are some gcc-mingw-* packages
> >>after 20040822-1 that fix the problem?
> >
> >Yes. And I suggest that you get a gold star because you found
On Thu, Jun 09, 2005 at 11:31:23PM +0200, Gerrit P. Haase wrote:
>>Oh, I'm sorry. I think I see. There are some gcc-mingw-* packages
>>after 20040822-1 that fix the problem?
>
>Yes. And I suggest that you get a gold star because you found the
>first mistake I made when building and uploading thi
David Rothenberger wrote:
On 6/9/2005 12:24 PM, David Rothenberger wrote:
On 6/9/2005 12:17 PM, Gerrit P. Haase wrote:
David Rothenberger wrote:
% cygcheck -cv | grep gcc
Empty package gcc
gcc 3.4.4-1 OK
gcc-core3.4.4-1 OK
gcc-
David Rothenberger wrote:
On 6/9/2005 12:17 PM, Gerrit P. Haase wrote:
David Rothenberger wrote:
% cygcheck -cv | grep gcc
Empty package gcc
gcc 3.4.4-1 OK
gcc-core3.4.4-1 OK
gcc-g++ 3.4.4-1 OK
Empty
Gerrit P. Haase wrote:
Dave Korn wrote:
Yep, that's got to be the source of the problem.
% ls /lib/gcc/i686-pc-mingw32
3.4.1
Gcc normally lives under "/lib/gcc-lib/", rather than
"/lib/gcc/...";
someone's been playing around with all the various individual
--*-prefix=DIR
and
On 6/9/2005 12:24 PM, David Rothenberger wrote:
On 6/9/2005 12:17 PM, Gerrit P. Haase wrote:
David Rothenberger wrote:
% cygcheck -cv | grep gcc
Empty package gcc
gcc 3.4.4-1 OK
gcc-core3.4.4-1 OK
gcc-g++ 3.4.4-1
On 6/9/2005 12:17 PM, Gerrit P. Haase wrote:
David Rothenberger wrote:
% cygcheck -cv | grep gcc
Empty package gcc
gcc 3.4.4-1 OK
gcc-core3.4.4-1 OK
gcc-g++ 3.4.4-1 OK
Empty package gcc-mingw
gcc-mingw
David Rothenberger wrote:
I ran Cygwin Setup today and noticed that gcc 3.4.4-1 had moved out of
test, so I upgraded it. I then tried to build the cygwin DLL and
utilites from CVS and ran into a problem compiling cygcheck.
g++: installation problem, cannot exec 'cc1plus': No such file or dire
Dave Korn wrote:
Yep, that's got to be the source of the problem.
% ls /lib/gcc/i686-pc-mingw32
3.4.1
Gcc normally lives under "/lib/gcc-lib/", rather than "/lib/gcc/...";
someone's been playing around with all the various individual --*-prefix=DIR
and --*dir= options at configure
David Rothenberger wrote:
On 6/9/2005 11:15 AM, Dave Korn wrote:
Original Message
From: Christopher Faylor
Sent: 09 June 2005 19:08
On Thu, Jun 09, 2005 at 11:05:40AM -0700, David Rothenberger wrote:
I ran Cygwin Setup today and noticed that gcc 3.4.4-1 had moved out of
test, s
Original Message
>From: David Rothenberger
>Sent: 09 June 2005 19:50
> % gcc -print-search-dirs
> install: /usr/lib/gcc/i686-pc-cygwin/3.4.4/
> programs:
>
=/bin/../lib/gcc/i686-pc-cygwin/3.4.4/:/bin/../lib/gcc/:/usr/lib/gcc/i686-pc
-cygwin/3.4.4/:/usr/lib/gcc/i686-pc-cygwin/3.4.4/:/usr/l
On 6/9/2005 11:15 AM, Dave Korn wrote:
Original Message
From: Christopher Faylor
Sent: 09 June 2005 19:08
On Thu, Jun 09, 2005 at 11:05:40AM -0700, David Rothenberger wrote:
I ran Cygwin Setup today and noticed that gcc 3.4.4-1 had moved out of
test, so I upgraded it. I then tried
Original Message
>From: Christopher Faylor
>Sent: 09 June 2005 19:08
> On Thu, Jun 09, 2005 at 11:05:40AM -0700, David Rothenberger wrote:
>> I ran Cygwin Setup today and noticed that gcc 3.4.4-1 had moved out of
>> test, so I upgraded it. I then tried to build the cygwin DLL and
>> utilit
On Thu, Jun 09, 2005 at 11:05:40AM -0700, David Rothenberger wrote:
>I ran Cygwin Setup today and noticed that gcc 3.4.4-1 had moved out of
>test, so I upgraded it. I then tried to build the cygwin DLL and
>utilites from CVS and ran into a problem compiling cygcheck.
>
>g++: installation problem,
Christopher Faylor wrote:
Do you possibly have two versions of the mingw libgcc.a somehow? I haven't
verified this on my system, since I am knee deep in something else right
now but nm on /lib/gcc-lib/i686-pc-mingw32/3.3.1/libgcc.a tells me:
w32-shared-ptr.o:
b .bss
d .dat
On Tue, Dec 02, 2003 at 11:14:12PM -0500, Charles Wilson wrote:
>Christopher Faylor wrote:
>
>>I don't know what this particular problem is (it sounds pretty bad if
>>-mno-cygwin is this broken) but:
>>
>>==
>>File: w32-shared-ptr.c Status: Up-to-date
>>
>> Working revision:
Christopher Faylor wrote:
I don't know what this particular problem is (it sounds pretty bad if
-mno-cygwin is this broken) but:
==
File: w32-shared-ptr.c Status: Up-to-date
Working revision:1.1.6.1
Repository revision: 1.1.6.1 /cvs/gcc/gcc/gcc/config/i386/Attic/w32-
On Tue, Dec 02, 2003 at 09:55:25PM -0500, Charles Wilson wrote:
>So I'm trying to release a new version of "mingw-zlib" for cygwin(*) now
>that zlib-1.2.1 has been released. But I can't...
>
>(*) this package is a msvcrt-linked version of zlib, used by cygwin
>internal projects (like setup.exe a
Oh, one other thing -- here's the list of relevant (cygwin) packages I
have installed:
binutils20030901-1
gcc 3.3.1-3
gcc-g++ 3.3.1-3
gcc-g77 3.3.1-3
gcc-mingw 20030911-4
gcc-mingw-core 20031020-1
gcc-mingw
At 05:40 PM 1/3/2003, Macias Abraham wrote:
>I´m new in gygwin and gcc program gives me an extrange
>error when I execute it.
>
>First appear an error window which says "Error
>initialicing the program", "The file CC1.EXE is
>vinculated to one CYGWIN1.DLL:putc_unlocked of
>exportacion that not exis
28 matches
Mail list logo