[ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]

gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.

This version has been built with
--with-default-libstdcxx-abi=gcc4-compatible so it should remain
compatible to GCC 4 C++ ABI.

Changes since -1:

* Rebuilt with binutils-2.28-1, seems to have fixed the testcase from
https://cygwin.com/ml/cygwin/2017-02/msg00093.html


              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com <at> cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Marco Atzeri]

On 29/06/2017 13:16, JonY wrote:
> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
>
> This version has been built with
> --with-default-libstdcxx-abi=gcc4-compatible so it should remain
> compatible to GCC 4 C++ ABI.
>
> Changes since -1:
>
> * Rebuilt with binutils-2.28-1, seems to have fixed the testcase from
> https://cygwin.com/ml/cygwin/2017-02/msg00093.html
>

Jon,
you missed to update the override.hint from

test: 6.3.0-1
curr: 5.4.0-1
prev: 5.3.0-5

to

test: 6.3.0-2
curr: 5.4.0-1
prev: 5.3.0-5

I did for you and also removed the 6.3.0-1
files, to avoid future problems when removing the override.hint

Regards
Marco



--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 823 bytes --]

On 07/01/2017 04:56 AM, Marco Atzeri wrote:
> On 29/06/2017 13:16, JonY wrote:
>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
>>
>> This version has been built with
>> --with-default-libstdcxx-abi=gcc4-compatible so it should remain
>> compatible to GCC 4 C++ ABI.
>>
>> Changes since -1:
>>
>> * Rebuilt with binutils-2.28-1, seems to have fixed the testcase from
>> https://cygwin.com/ml/cygwin/2017-02/msg00093.html
>>
> 
> Jon,
> you missed to update the override.hint from
> 
> test: 6.3.0-1
> curr: 5.4.0-1
> prev: 5.3.0-5
> 
> to
> 
> test: 6.3.0-2
> curr: 5.4.0-1
> prev: 5.3.0-5
> 
> I did for you and also removed the 6.3.0-1
> files, to avoid future problems when removing the override.hint
> 

Thanks, I was trying to find out how to remove -1.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Marco Atzeri]

On 01/07/2017 10:37, JonY wrote:
> On 07/01/2017 04:56 AM, Marco Atzeri wrote:
>> On 29/06/2017 13:16, JonY wrote:
>>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
>>>

>>
>> I did for you and also removed the 6.3.0-1
>> files, to avoid future problems when removing the override.hint
>>
>
> Thanks, I was trying to find out how to remove -1.
>


to remove any <nomefile> upload an empty <-nomefile>

see instructions at the end of
https://cygwin.com/package-upload.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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Achim Gratz]

Marco Atzeri writes:
> I did for you and also removed the 6.3.0-1
> files, to avoid future problems when removing the override.hint

Someone might still need to trigger calm to run to pick up these
changes and produce a matching setup.ini, it seems.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Marco Atzeri]

On 01/07/2017 15:56, Achim Gratz wrote:
> Marco Atzeri writes:
>> I did for you and also removed the 6.3.0-1
>> files, to avoid future problems when removing the override.hint
>
> Someone might still need to trigger calm to run to pick up these
> changes and produce a matching setup.ini, it seems.
>
>
> Regards,
> Achim.
>


that is the problem that I found after making the changes

Marco




--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 720 bytes --]

On 07/01/2017 10:46 AM, Marco Atzeri wrote:
> On 01/07/2017 10:37, JonY wrote:
>> On 07/01/2017 04:56 AM, Marco Atzeri wrote:
>>> On 29/06/2017 13:16, JonY wrote:
>>>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test
>>>> version.
>>>>
> 
>>>
>>> I did for you and also removed the 6.3.0-1
>>> files, to avoid future problems when removing the override.hint
>>>
>>
>> Thanks, I was trying to find out how to remove -1.
>>
> 
> 
> to remove any <nomefile> upload an empty <-nomefile>
> 
> see instructions at the end of
> https://cygwin.com/package-upload.html

Does it need to be in the same directory layout of the actual file to be
removed? Does it also support globbing?




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Marco Atzeri]

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

On 02/07/2017 05:47, JonY wrote:
> On 07/01/2017 10:46 AM, Marco Atzeri wrote:
>> On 01/07/2017 10:37, JonY wrote:
>>> On 07/01/2017 04:56 AM, Marco Atzeri wrote:
>>>> On 29/06/2017 13:16, JonY wrote:
>>>>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test
>>>>> version.
>>>>>
>>
>>>>
>>>> I did for you and also removed the 6.3.0-1
>>>> files, to avoid future problems when removing the override.hint
>>>>
>>>
>>> Thanks, I was trying to find out how to remove -1.
>>>
>>
>>
>> to remove any <nomefile> upload an empty <-nomefile>
>>
>> see instructions at the end of
>> https://cygwin.com/package-upload.html
>
> Does it need to be in the same directory layout of the actual file to be
> removed? Does it also support globbing?
>

same exact layout, no globbing.

I prefer to use lftp for upload, and I use the attached script in
the upload tree to duplicate for every new file a removal of the old one

upload-removal.sh 6.3.0-2 6.3.0-1

Of course if the structure changes you need to do manually,
usually for API bumps..

Regards
Marco








[-- Attachment #2: upload-removal.sh --]
[-- Type: text/plain, Size: 335 bytes --]

#!/bin/bash
if [ $# -ne 2 ]
then
    echo "Usage : " $0 "new_version old_version"
    exit 1
fi

for i in $(find -type f -name "*.xz" -not -name "-*.xz" ) $(find -type f -name "*.hint" -not -name "-*.hint" )
do
	OF=$(basename $i)
	DF=${OF/$1/$2}
	if [ x${OF} != x${DF} ]
	then
		DD=${i%${OF}}
		cp -- /dev/null ${DD}"-"${DF}
	fi
done


[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ken Brown]

On 6/29/2017 7:16 AM, JonY wrote:
> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.

JonY,

I assume you want some feedback on this.

I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and 
x86_64, by rebuilding several of my packages.  So far I've built 
texlive, emacs, and icu.  There have been no problems, and all builds 
have passed their test suites.

Ken



--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ross Smith]

On 2017-07-28 02:49, Ken Brown wrote:
> On 6/29/2017 7:16 AM, JonY wrote:
>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
> 
> JonY,
> 
> I assume you want some feedback on this.
> 
> I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and 
> x86_64, by rebuilding several of my packages.  So far I've built 
> texlive, emacs, and icu.  There have been no problems, and all builds 
> have passed their test suites.
> 
> Ken

gcc 6.3 works fine for me unless I use threads. Any C++ program that 
uses std::thread (and worked with the previous gcc) will fail. Simple 
example:

     #include <iostream>
     #include <thread>
     void payload() {
         std::cout << "Thread\n";
     }
     int main() {
         std::cout << "Start\n";
         std::thread t(payload);
         t.join();
         std::cout << "Done\n";
     }

Build and run with:

     g++ thread.cpp -o thread && ./thread || echo Fail

This will print Fail, indicating that the executable errored out. 
There's no other output. Sorry, I'm not familiar enough with gcc 
debugging to narrow down the error further.

Code that uses raw pthreads instead of the C++ API works fine.

(I'm running 64-bit Cygwin on Windows 8.1.)

Ross Smith

--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ross Smith]

On 2017-07-28 02:49, Ken Brown wrote:
> On 6/29/2017 7:16 AM, JonY wrote:
>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test version.
> 
> JonY,
> 
> I assume you want some feedback on this.
> 
> I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and 
> x86_64, by rebuilding several of my packages.  So far I've built 
> texlive, emacs, and icu.  There have been no problems, and all builds 
> have passed their test suites.
> 
> Ken

gcc 6.3 works fine for me unless I use threads. Any C++ program that 
uses std::thread (and worked with the previous gcc) will fail. Simple 
example:

     #include <iostream>
     #include <thread>
     void payload() {
         std::cout << "Thread\n";
     }
     int main() {
         std::cout << "Start\n";
         std::thread t(payload);
         t.join();
         std::cout << "Done\n";
     }

Build and run with:

     g++ thread.cpp -o thread && ./thread || echo Fail

This will print Fail, indicating that the executable errored out. 
There's no other output. Sorry, I'm not familiar enough with gcc 
debugging to narrow down the error further.

Code that uses raw pthreads instead of the C++ API works fine.

(I'm running 64-bit Cygwin on Windows 8.1.)

Ross Smith


--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Marco Atzeri]

On 27/07/2017 23:04, Ross Smith wrote:
> On 2017-07-28 02:49, Ken Brown wrote:
>> On 6/29/2017 7:16 AM, JonY wrote:
>>> gcc-6.3.0-2 has been uploaded for Cygwin. It is marked as a test
>>> version.
>>
>> JonY,
>>
>> I assume you want some feedback on this.
>>
>> I've been testing gcc-6.3.0-2 with binutils-2.28-3, on both x86 and
>> x86_64, by rebuilding several of my packages.  So far I've built
>> texlive, emacs, and icu.  There have been no problems, and all builds
>> have passed their test suites.
>>
>> Ken
>
> gcc 6.3 works fine for me unless I use threads. Any C++ program that
> uses std::thread (and worked with the previous gcc) will fail. Simple
> example:
>
>     #include <iostream>
>     #include <thread>
>     void payload() {
>         std::cout << "Thread\n";
>     }
>     int main() {
>         std::cout << "Start\n";
>         std::thread t(payload);
>         t.join();
>         std::cout << "Done\n";
>     }
>
> Build and run with:
>
>     g++ thread.cpp -o thread && ./thread || echo Fail
>
> This will print Fail, indicating that the executable errored out.
> There's no other output. Sorry, I'm not familiar enough with gcc
> debugging to narrow down the error further.
>
> Code that uses raw pthreads instead of the C++ API works fine.
>
> (I'm running 64-bit Cygwin on Windows 8.1.)
>
> Ross Smith
>

it works for me on W7-64

./thread || echo "fail"
Start
Thread
Done

$ g++ --version
g++ (GCC) 6.3.0


--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ross Smith]

On 2017-07-28 09:19, Marco Atzeri wrote:
> On 27/07/2017 23:04, Ross Smith wrote:
>>
>> gcc 6.3 works fine for me unless I use threads. Any C++ program that
>> uses std::thread (and worked with the previous gcc) will fail. Simple
>> example:
>>
>>     #include <iostream>
>>     #include <thread>
>>     void payload() {
>>         std::cout << "Thread\n";
>>     }
>>     int main() {
>>         std::cout << "Start\n";
>>         std::thread t(payload);
>>         t.join();
>>         std::cout << "Done\n";
>>     }
>>
>> Build and run with:
>>
>>     g++ thread.cpp -o thread && ./thread || echo Fail
>>
>> This will print Fail, indicating that the executable errored out.
>> There's no other output. Sorry, I'm not familiar enough with gcc
>> debugging to narrow down the error further.
>>
>> Code that uses raw pthreads instead of the C++ API works fine.
>>
>> (I'm running 64-bit Cygwin on Windows 8.1.)
>>
>> Ross Smith
>>
> 
> it works for me on W7-64
> 
> ./thread || echo "fail"
> Start
> Thread
> Done
> 
> $ g++ --version
> g++ (GCC) 6.3.0

That's interesting. Maybe I have something wrong with my installation? I 
updated the gcc-core, gcc-g++, and libgcc1 packages to the 6.3 test 
version; was there something else I needed? (I found those by searching 
the installed package list in the Cygwin installer for gcc or g++, and 
seeing which ones offered the option of updating to 6.3; there doesn't 
seem to be any way of checking what you actually need in a case like this.)

Ross Smith

--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ross Smith]

On 2017-07-28 09:19, Marco Atzeri wrote:
> On 27/07/2017 23:04, Ross Smith wrote:
>>
>> gcc 6.3 works fine for me unless I use threads. Any C++ program that
>> uses std::thread (and worked with the previous gcc) will fail. Simple
>> example:
>>
>>     #include <iostream>
>>     #include <thread>
>>     void payload() {
>>         std::cout << "Thread\n";
>>     }
>>     int main() {
>>         std::cout << "Start\n";
>>         std::thread t(payload);
>>         t.join();
>>         std::cout << "Done\n";
>>     }
>>
>> Build and run with:
>>
>>     g++ thread.cpp -o thread && ./thread || echo Fail
>>
>> This will print Fail, indicating that the executable errored out.
>> There's no other output. Sorry, I'm not familiar enough with gcc
>> debugging to narrow down the error further.
>>
>> Code that uses raw pthreads instead of the C++ API works fine.
>>
>> (I'm running 64-bit Cygwin on Windows 8.1.)
>>
>> Ross Smith
>>
> 
> it works for me on W7-64
> 
> ./thread || echo "fail"
> Start
> Thread
> Done
> 
> $ g++ --version
> g++ (GCC) 6.3.0

That's interesting. Maybe I have something wrong with my installation? I 
updated the gcc-core, gcc-g++, and libgcc1 packages to the 6.3 test 
version; was there something else I needed? (I found those by searching 
the installed package list in the Cygwin installer for gcc or g++, and 
seeing which ones offered the option of updating to 6.3; there doesn't 
seem to be any way of checking what you actually need in a case like this.)

Ross Smith


--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ken Brown]

On 7/27/2017 5:39 PM, Ross Smith wrote:
> On 2017-07-28 09:19, Marco Atzeri wrote:
>> On 27/07/2017 23:04, Ross Smith wrote:
>>>
>>> gcc 6.3 works fine for me unless I use threads. Any C++ program that
>>> uses std::thread (and worked with the previous gcc) will fail. Simple
>>> example:
>>>
>>>     #include <iostream>
>>>     #include <thread>
>>>     void payload() {
>>>         std::cout << "Thread\n";
>>>     }
>>>     int main() {
>>>         std::cout << "Start\n";
>>>         std::thread t(payload);
>>>         t.join();
>>>         std::cout << "Done\n";
>>>     }
>>>
>>> Build and run with:
>>>
>>>     g++ thread.cpp -o thread && ./thread || echo Fail
>>>
>>> This will print Fail, indicating that the executable errored out.
>>> There's no other output. Sorry, I'm not familiar enough with gcc
>>> debugging to narrow down the error further.
>>>
>>> Code that uses raw pthreads instead of the C++ API works fine.
>>>
>>> (I'm running 64-bit Cygwin on Windows 8.1.)
>>>
>>> Ross Smith
>>>
>>
>> it works for me on W7-64
>>
>> ./thread || echo "fail"
>> Start
>> Thread
>> Done
>>
>> $ g++ --version
>> g++ (GCC) 6.3.0
> 
> That's interesting. Maybe I have something wrong with my installation? I 
> updated the gcc-core, gcc-g++, and libgcc1 packages to the 6.3 test 
> version; was there something else I needed? (I found those by searching 
> the installed package list in the Cygwin installer for gcc or g++, and 
> seeing which ones offered the option of updating to 6.3; there doesn't 
> seem to be any way of checking what you actually need in a case like this.)

Click the test button when running setup.  You'll see several other 
packages with versions 6.3.0-2, including libstdc++6.

Ken

--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ross Smith]

On 2017-07-28 09:45, Ken Brown wrote:
> On 7/27/2017 5:39 PM, Ross Smith wrote:
>> On 2017-07-28 09:19, Marco Atzeri wrote:
>>> On 27/07/2017 23:04, Ross Smith wrote:
>>>>
>>>> gcc 6.3 works fine for me unless I use threads. Any C++ program that
>>>> uses std::thread (and worked with the previous gcc) will fail. Simple
>>>> example:
>>>>
>>>>     #include <iostream>
>>>>     #include <thread>
>>>>     void payload() {
>>>>         std::cout << "Thread\n";
>>>>     }
>>>>     int main() {
>>>>         std::cout << "Start\n";
>>>>         std::thread t(payload);
>>>>         t.join();
>>>>         std::cout << "Done\n";
>>>>     }
>>>>
>>>> Build and run with:
>>>>
>>>>     g++ thread.cpp -o thread && ./thread || echo Fail
>>>>
>>>> This will print Fail, indicating that the executable errored out.
>>>> There's no other output. Sorry, I'm not familiar enough with gcc
>>>> debugging to narrow down the error further.
>>>>
>>>> Code that uses raw pthreads instead of the C++ API works fine.
>>>>
>>>> (I'm running 64-bit Cygwin on Windows 8.1.)
>>>>
>>>> Ross Smith
>>>>
>>>
>>> it works for me on W7-64
>>>
>>> ./thread || echo "fail"
>>> Start
>>> Thread
>>> Done
>>>
>>> $ g++ --version
>>> g++ (GCC) 6.3.0
>>
>> That's interesting. Maybe I have something wrong with my installation? 
>> I updated the gcc-core, gcc-g++, and libgcc1 packages to the 6.3 test 
>> version; was there something else I needed? (I found those by 
>> searching the installed package list in the Cygwin installer for gcc 
>> or g++, and seeing which ones offered the option of updating to 6.3; 
>> there doesn't seem to be any way of checking what you actually need in 
>> a case like this.)
> 
> Click the test button when running setup.  You'll see several other 
> packages with versions 6.3.0-2, including libstdc++6.

Thanks! Yes, turns out I was missing some packages. Everything works 
now. Sorry for the false alarm!

Ross Smith

--
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: [ANNOUNCEMENT] Updated: gcc-6.3.0-2 (x86/x86_64)(Test)

[Ross Smith]

On 2017-07-28 09:45, Ken Brown wrote:
> On 7/27/2017 5:39 PM, Ross Smith wrote:
>> On 2017-07-28 09:19, Marco Atzeri wrote:
>>> On 27/07/2017 23:04, Ross Smith wrote:
>>>>
>>>> gcc 6.3 works fine for me unless I use threads. Any C++ program that
>>>> uses std::thread (and worked with the previous gcc) will fail. Simple
>>>> example:
>>>>
>>>>     #include <iostream>
>>>>     #include <thread>
>>>>     void payload() {
>>>>         std::cout << "Thread\n";
>>>>     }
>>>>     int main() {
>>>>         std::cout << "Start\n";
>>>>         std::thread t(payload);
>>>>         t.join();
>>>>         std::cout << "Done\n";
>>>>     }
>>>>
>>>> Build and run with:
>>>>
>>>>     g++ thread.cpp -o thread && ./thread || echo Fail
>>>>
>>>> This will print Fail, indicating that the executable errored out.
>>>> There's no other output. Sorry, I'm not familiar enough with gcc
>>>> debugging to narrow down the error further.
>>>>
>>>> Code that uses raw pthreads instead of the C++ API works fine.
>>>>
>>>> (I'm running 64-bit Cygwin on Windows 8.1.)
>>>>
>>>> Ross Smith
>>>>
>>>
>>> it works for me on W7-64
>>>
>>> ./thread || echo "fail"
>>> Start
>>> Thread
>>> Done
>>>
>>> $ g++ --version
>>> g++ (GCC) 6.3.0
>>
>> That's interesting. Maybe I have something wrong with my installation? 
>> I updated the gcc-core, gcc-g++, and libgcc1 packages to the 6.3 test 
>> version; was there something else I needed? (I found those by 
>> searching the installed package list in the Cygwin installer for gcc 
>> or g++, and seeing which ones offered the option of updating to 6.3; 
>> there doesn't seem to be any way of checking what you actually need in 
>> a case like this.)
> 
> Click the test button when running setup.  You'll see several other 
> packages with versions 6.3.0-2, including libstdc++6.

Thanks! Yes, turns out I was missing some packages. Everything works 
now. Sorry for the false alarm!

Ross Smith


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