-static not working with gcc 4.3.4

-static not working with gcc 4.3.4

[Samuel Thibault]

Hello,

gcc -static doesn't seem to be working any more using gcc 4.3.4:

$ cat test.c
int main(void) {}
$ gcc test.c -o test -static
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld: cannot find -lgcc_s
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld: cannot find -lgcc_s

There indeed is libgcc_s.dll.a in /usr/lib/gcc/i686-pc-cygwin/, but for
some reason gcc doesn't seem to be happy with it. This is using gcc4 and
gcc4-core 4.3.4-3.  gcc-3 works fine.

Samuel

--
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

R: -static not working with gcc 4.3.4

[Marco Atzeri]

--- Dom 17/10/10, Samuel Thibault  ha scritto:

> Data: Domenica 17 ottobre 2010, 02:58
> Hello,
> 
> gcc -static doesn't seem to be working any more using gcc
> 4.3.4:
> 
> $ cat test.c
> int main(void) {}
> $ gcc test.c -o test -static
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> cannot find -lgcc_s
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> cannot find -lgcc_s
> 
> There indeed is libgcc_s.dll.a in
> /usr/lib/gcc/i686-pc-cygwin/, but for
> some reason gcc doesn't seem to be happy with it. This is
> using gcc4 and
> gcc4-core 4.3.4-3.  gcc-3 works fine.
> 
> Samuel

$ gcc test.c -o test -static-libgcc

$ cygcheck ./test.exe
C:\cygwin\tmp\test.exe
  C:\cygwin\bin\cygwin1.dll
    C:\WINDOWS\system32\ADVAPI32.DLL
      C:\WINDOWS\system32\KERNEL32.dll
        C:\WINDOWS\system32\ntdll.dll
      C:\WINDOWS\system32\RPCRT4.dll
        C:\WINDOWS\system32\Secur32.dll

see gcc documetation

Regards





--
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: R: -static not working with gcc 4.3.4

[Samuel Thibault]

Marco Atzeri, le Sun 17 Oct 2010 06:33:39 +0100, a écrit :
> > Data: Domenica 17 ottobre 2010, 02:58
> > gcc -static doesn't seem to be working any more using gcc
> > 4.3.4:
> > 
> > $ cat test.c
> > int main(void) {}
> > $ gcc test.c -o test -static
> > /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> > cannot find -lgcc_s
> > /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> > cannot find -lgcc_s
> > 
> > There indeed is libgcc_s.dll.a in
> > /usr/lib/gcc/i686-pc-cygwin/, but for
> > some reason gcc doesn't seem to be happy with it. This is
> > using gcc4 and
> > gcc4-core 4.3.4-3.  gcc-3 works fine.
> 
> $ gcc test.c -o test -static-libgcc

Errr, right, that's a workaround, but I don't see why I should be
forced to do it that way, not taking advantage of sharing libgcc, while
apparently libgcc_s.dll.a and cygcc_s-1.dll are really there, and it's
just something that doesn't exactly work appropriately any more, i.e. a
regression.

> $ cygcheck ./test.exe
> C:\cygwin\tmp\test.exe
>   C:\cygwin\bin\cygwin1.dll
>     C:\WINDOWS\system32\ADVAPI32.DLL
>       C:\WINDOWS\system32\KERNEL32.dll
>         C:\WINDOWS\system32\ntdll.dll
>       C:\WINDOWS\system32\RPCRT4.dll
>         C:\WINDOWS\system32\Secur32.dll
> 
> see gcc documetation

Yes, it doesn't use the shared version of libgcc, but that's not what I
want.

Samuel

--
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: -static not working with gcc 4.3.4

[Nellis, Kenneth]

> From: Samuel Thibault
> 
> Hello,
> 
> gcc -static doesn't seem to be working any more using gcc 4.3.4:
> 
> $ cat test.c
> int main(void) {}
> $ gcc test.c -o test -static
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> cannot find -lgcc_s
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> cannot find -lgcc_s
> 
> There indeed is libgcc_s.dll.a in /usr/lib/gcc/i686-pc-cygwin/, but for
> some reason gcc doesn't seem to be happy with it. This is using gcc4
> and
> gcc4-core 4.3.4-3.  gcc-3 works fine.
> 
> Samuel

Please, why such a large test case when the following would
have been perfectly adequate to demonstrate the problem?:

$ cat test.c
main() {}
$

--Ken Nellis

Re: -static not working with gcc 4.3.4

[Samuel Thibault]

Nellis, Kenneth, le Mon 18 Oct 2010 07:45:15 -0500, a écrit :
> > From: Samuel Thibault
> > $ cat test.c
> > int main(void) {}
> > $ gcc test.c -o test -static
> > /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> > cannot find -lgcc_s
> > /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> > cannot find -lgcc_s
> > 
> > There indeed is libgcc_s.dll.a in /usr/lib/gcc/i686-pc-cygwin/, but for
> > some reason gcc doesn't seem to be happy with it. This is using gcc4
> > and
> > gcc4-core 4.3.4-3.  gcc-3 works fine.
> 
> Please, why such a large test case when the following would
> have been perfectly adequate to demonstrate the problem?:
> 
> $ cat test.c
> main() {}
> $

Because providing precise information is always better when reporting a
bug, whatever the circumstances.

That being said, I'd still like to see this bug fixed: the -static is
suppoed to be able to work alone.

Samuel

--
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: -static not working with gcc 4.3.4

[Marco Atzeri]

--- Lun 18/10/10, Samuel Thibault  scritto:

> > > From: Samuel Thibault
> > > $ cat test.c
> > > int main(void) {}
> > > $ gcc test.c -o test -static
> > >
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> > > cannot find -lgcc_s
> > >
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld:
> > > cannot find -lgcc_s
> > > 
> > > There indeed is libgcc_s.dll.a in
> /usr/lib/gcc/i686-pc-cygwin/, but for
> > > some reason gcc doesn't seem to be happy with it.
> This is using gcc4
> > > and
> > > gcc4-core 4.3.4-3.  gcc-3 works fine.
> > 
> > Please, why such a large test case when the following
> would
> > have been perfectly adequate to demonstrate the
> problem?:
> > 
> > $ cat test.c
> > main() {}
> > $
> 
> Because providing precise information is always better when
> reporting a
> bug, whatever the circumstances.
> 
> That being said, I'd still like to see this bug fixed: the
> -static is
> suppoed to be able to work alone.
> 
> Samuel
> 

have you checked if 4.5 has the same problem ?

http://cygwin.com/ml/cygwin-announce/2010-08/msg00016.html






--
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: -static not working with gcc 4.3.4

[Samuel Thibault]

Marco Atzeri, le Mon 18 Oct 2010 14:22:02 +0100, a écrit :
> have you checked if 4.5 has the same problem ?
> 
> http://cygwin.com/ml/cygwin-announce/2010-08/msg00016.html

It doesn't have the problem any more.

Samuel

--
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: -static not working with gcc 4.3.4

[gvidaver]

It still requires the cygwin1.dll:

$ g++ -v
...
gcc version 4.5.0 (GCC)

$ g++ test.c -o test -static

$ ldd test.exe
        ...
        cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
        ...

And apparently the only alternative is mingw, see:

http://cygwin.com/faq/faq-nochunks.html#faq.programming.static-linking
"it is not possible to statically link with a Cygwin library to obtain an
independent, self-contained executable. "

$ i686-w64-mingw32-g++ -v
...
gcc version 4.5.1 (GCC)

$ i686-w64-mingw32-g++ test.c -o test -static

$ ldd test.exe
        ntdll.dll => ... path to Windows dlls
        kernel32.dll => ... 
        KERNELBASE.dll => ...
        msvcrt.dll => ...

(I.e. no dependencies on anything besides system dlls.)


Samuel Thibault wrote:
> 
> Marco Atzeri, le Mon 18 Oct 2010 14:22:02 +0100, a écrit :
>> have you checked if 4.5 has the same problem ?
>> 
>> http://cygwin.com/ml/cygwin-announce/2010-08/msg00016.html
> 
> It doesn't have the problem any more.
> 
> Samuel
> 
> --
> 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
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/-static-not-working-with-gcc-4.3.4-tp29981383p30838541.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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: -static not working with gcc 4.3.4

[marco atzeri]

On Thu, Feb 3, 2011 at 8:34 PM, gvidaver  wrote:

what is a new game to continue a thread after 3-4 months ?

>
> It still requires the cygwin1.dll:

of course it is a cygwin program built by the gcc for cygwin .

>
> $ g++ -v
> ...
> gcc version 4.5.0 (GCC)
>
> $ g++ test.c -o test -static
>
> $ ldd test.exe
>        ...
>        cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
>        ...
>
> And apparently the only alternative is mingw, see:
>
> http://cygwin.com/faq/faq-nochunks.html#faq.programming.static-linking
> "it is not possible to statically link with a Cygwin library to obtain an
> independent, self-contained executable. "
>
> $ i686-w64-mingw32-g++ -v
> ...
> gcc version 4.5.1 (GCC)
>
> $ i686-w64-mingw32-g++ test.c -o test -static
>
> $ ldd test.exe
>        ntdll.dll => ... path to Windows dlls
>        kernel32.dll => ...
>        KERNELBASE.dll => ...
>        msvcrt.dll => ...
>
> (I.e. no dependencies on anything besides system dlls.)
>
>
> Samuel Thibault wrote:
>>
>> Marco Atzeri, le Mon 18 Oct 2010 14:22:02 +0100, a écrit :
>>> have you checked if 4.5 has the same problem ?
>>>
>>> http://cygwin.com/ml/cygwin-announce/2010-08/msg00016.html
>>
>> It doesn't have the problem any more.
>>
>> Samuel
>>
>> --
>> 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
>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/-static-not-working-with-gcc-4.3.4-tp29981383p30838541.html
> Sent from the Cygwin list mailing list archive at Nabble.com.
>
>
> --
> 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: -static not working with gcc 4.3.4

[Charles Wilson]

On 2/3/2011 2:34 PM, gvidaver wrote:
> It still requires the cygwin1.dll:
> 
> $ g++ -v
> ...
> gcc version 4.5.0 (GCC)
> 
> $ g++ test.c -o test -static
> 
> $ ldd test.exe
>         ...
>         cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
>         ...

Uhm, yes.  The cygwin-provided gcc is a cygwin compiler, intended for
generating cygwin DLLs and executables.  Thus, all dlls and exes it
generates will require the cygwin1.dll (since there is not now, and will
not be, any "static version" of cygwin1.dll).

Older cygwin gcc's had a controversial mode "-mno-cygwin" that,
basically, turned the cygwin gcc into a buggy version of the mingw gcc.
 It often had "cygwin pollution" problems, and many people misunderstood
the purpose of the flag.  So, it has been deprecated for about five
years now, and was finally removed with the release of cygwin's gcc-4.3.4.

> And apparently the only alternative is mingw, see:
> 
> http://cygwin.com/faq/faq-nochunks.html#faq.programming.static-linking
> "it is not possible to statically link with a Cygwin library to obtain an
> independent, self-contained executable. "
> 
> $ i686-w64-mingw32-g++ -v
> ...
> gcc version 4.5.1 (GCC)
> 
> $ i686-w64-mingw32-g++ test.c -o test -static
> 
> $ ldd test.exe
>         ntdll.dll => ... path to Windows dlls
>         kernel32.dll => ... 
>         KERNELBASE.dll => ...
>         msvcrt.dll => ...
> 
> (I.e. no dependencies on anything besides system dlls.)

Right, but on the "cygwin system", the cygwin1.dll IS a system dll (as
are cyggcc_s-1.dll, cygstdc++-6.dll, and the other "language" runtime
libraries). All -static does is force the compiler to attempt to link
statically to OTHER user libs that you'd pass on the link command, like
-lintl -lz -ljpeg etc.

You can, in SOME cases, avoid a shared dependency on the *language*
runtimes (for C and C++ alone) by using the -static-libgcc and/or
-static-libstdc++, but...there are complexities with that.

However, using the cygwin compiler, you cannot (*) avoid a dependency on
the cygwin runtime cygwin1.dll.  This is not a bug; it is part of the
design.

Now, the OP in this thread posted a problem with -static related to the
language runtime library for C (gcc_s aka cyggcc_s-1.dll) but that's a
whole different issue that your attempt to avoid cygwin1.dll.


(*) OK, sure, you can use -nostdlib but...I guarantee you won't like the
results.  It just won't work, and you'd be better off simply using the
mingw compiler instead (or one of cygwin's mingw-target cross compilers).

--
Chuck

--
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: -static not working with gcc 4.3.4

[gvidaver]

To clarify : you can't make an executable that copies the dll or library code
into the executable itself.  When the exe launches it will look for
cygwin1.dll in /usr/bin.  So it will fail to launch on a system that doesn't
have cygwin installed.  

If I understand the cygwin license, this is intended as a way to help RedHat
make money from cygwin (this intent is fine by me) by forcing you to pay
them for a solution to this problem.


marco atzeri-4 wrote:
> 
> On Thu, Feb 3, 2011 at 8:34 PM, gvidaver  wrote:
> 
> what is a new game to continue a thread after 3-4 months ?
> 
>>
>> It still requires the cygwin1.dll:
> 
> of course it is a cygwin program built by the gcc for cygwin .
> 
>>
>> $ g++ -v
>> ...
>> gcc version 4.5.0 (GCC)
>>
>> $ g++ test.c -o test -static
>>
>> $ ldd test.exe
>>        ...
>>        cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
>>        ...
>>
>> And apparently the only alternative is mingw, see:
>>
>> http://cygwin.com/faq/faq-nochunks.html#faq.programming.static-linking
>> "it is not possible to statically link with a Cygwin library to obtain an
>> independent, self-contained executable. "
>>
>> $ i686-w64-mingw32-g++ -v
>> ...
>> gcc version 4.5.1 (GCC)
>>
>> $ i686-w64-mingw32-g++ test.c -o test -static
>>
>> $ ldd test.exe
>>        ntdll.dll => ... path to Windows dlls
>>        kernel32.dll => ...
>>        KERNELBASE.dll => ...
>>        msvcrt.dll => ...
>>
>> (I.e. no dependencies on anything besides system dlls.)
>>
>>
>> Samuel Thibault wrote:
>>>
>>> Marco Atzeri, le Mon 18 Oct 2010 14:22:02 +0100, a écrit :
>>>> have you checked if 4.5 has the same problem ?
>>>>
>>>> http://cygwin.com/ml/cygwin-announce/2010-08/msg00016.html
>>>
>>> It doesn't have the problem any more.
>>>
>>> Samuel
>>>
>>> --
>>> 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
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/-static-not-working-with-gcc-4.3.4-tp29981383p30838541.html
>> Sent from the Cygwin list mailing list archive at Nabble.com.
>>
>>
>> --
>> 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
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/-static-not-working-with-gcc-4.3.4-tp29981383p30839509.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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: -static not working with gcc 4.3.4

[Christopher Faylor]

On Thu, Feb 03, 2011 at 01:21:39PM -0800, gvidaver wrote:
>To clarify : you can't make an executable that copies the dll or
>library code into the executable itself.  When the exe launches it will
>look for cygwin1.dll in /usr/bin.  So it will fail to launch on a
>system that doesn't have cygwin installed.

Nope.  Cygwin doesn't look in /usr/bin.  If you could get something like
that to work you'd just have to adhere to the GPL.  That's all.

>If I understand the cygwin license, this is intended as a way to help
>RedHat make money from cygwin (this intent is fine by me) by forcing
>you to pay them for a solution to this problem.

You don't understand the license.  Please stop attempting to give advice.
The thread is five months old.  We don't need further discussion.

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