On Sat, Mar 3, 2012 at 2:46 PM, Joshua Boyce
wrote:
> I believe that you don't have to distribute them directly, but you can
> just make them available to download somewhere. Dropbox would be a perfect
> candidate to host both the binaries as the source imo.
>
> http://www.gnu.org/licenses/gpl-faq
I believe that you don't have to distribute them directly, but you can just
make them available to download somewhere. Dropbox would be a perfect
candidate to host both the binaries as the source imo.
http://www.gnu.org/licenses/gpl-faq.html#AnonFTPAndSendSources
http://www.gnu.org/licenses/gpl-fa
2012/3/3 Earnie Boyd :
> On Fri, Mar 2, 2012 at 4:45 PM, Joshua Boyce
> wrote:
>>
>> On Sat, Mar 3, 2012 at 5:13 AM, Luis Lavena wrote:
>>>
>>> On Fri, Mar 2, 2012 at 1:09 PM, niXman wrote:
>>> >
>>> > I didn't upload sources and scripts cause nobody needs them. I didn't
>>> > want to hide them
On Fri, Mar 2, 2012 at 4:45 PM, Joshua Boyce
wrote:
>
> On Sat, Mar 3, 2012 at 5:13 AM, Luis Lavena wrote:
>>
>> On Fri, Mar 2, 2012 at 1:09 PM, niXman wrote:
>> >
>> > I didn't upload sources and scripts cause nobody needs them. I didn't
>> > want to hide them =)
>> >
>> > BTW, Why should I dup
On Sat, Mar 3, 2012 at 5:13 AM, Luis Lavena wrote:
> On Fri, Mar 2, 2012 at 1:09 PM, niXman wrote:
> >
> > I didn't upload sources and scripts cause nobody needs them. I didn't
> > want to hide them =)
> >
> > BTW, Why should I duplicate sources avalilable from official sites?
>
> That is where
On Fri, Mar 2, 2012 at 1:09 PM, niXman wrote:
>
> I didn't upload sources and scripts cause nobody needs them. I didn't
> want to hide them =)
>
> BTW, Why should I duplicate sources avalilable from official sites?
That is where GPL becomes annoying, but you should comply :-(
--
Luis Lavena
ARE
2012/3/2 Ruben Van Boxem :
> 2012/3/2 niXman
>>
>> Hello MinGW users list!
>>
>> On the 1st of March gcc-4.6.3 version was released [1]
>> I`d built MinGW based on this version with correct dynamically linking
>> of std_threads successfully [2]
>
>
Hi Ruben.
> That's great to hear. I'm having tr
2012/3/2 niXman
> Hello MinGW users list!
>
> On the 1st of March gcc-4.6.3 version was released [1]
> I`d built MinGW based on this version with correct dynamically linking
> of std_threads successfully [2]
>
That's great to hear. I'm having trouble replicating the shared std::thread
functional
2012/3/2 Alejandro Allievi
> Thank you Ruben! My ultimate intention is to be able to compile and
> execute MPI parallel C code. Would that be possible going down the route
> MinGW-w64 + GCC?? I've used GCC for serial C code for a while, but do not
> know if I'll be able to include mpi.h. Any hint
Hello MinGW users list!
On the 1st of March gcc-4.6.3 version was released [1]
I`d built MinGW based on this version with correct dynamically linking
of std_threads successfully [2]
Thanks everyone for help!
[1] http://news.softpedia.com/news/GCC-4-6-3-Brings-Lots-of-Fixes-256097.shtml
[2] http
Thank you Ruben! My ultimate intention is to be able to compile and execute
MPI parallel C code. Would that be possible going down the route MinGW-w64
+ GCC?? I've used GCC for serial C code for a while, but do not know if
I'll be able to include mpi.h. Any hints??
On Fri, Mar 2, 2012 at 11:38 AM,
2012/3/2 Alejandro Allievi
> Hi,
>
> I unzipped mingw-w64-v2.0.1. Can somebody tell me what to do next?? Is
> there a README file with the steps to follow??
>
You downloaded the MinGW-w64 headers and libraries source code, which is
what this project produces and maintains.
You probably want a c
Hi,
I unzipped mingw-w64-v2.0.1. Can somebody tell me what to do next?? Is
there a README file with the steps to follow??
Thank you and sorry for the silly question.
Alex
--
Virtualization & Cloud Management Using Capaci
13 matches
Mail list logo
