2012/3/4 niXman <[email protected]>
> 2012/3/4 Ruben Van Boxem <[email protected]>:
> > Op 4 mrt. 2012 07:40 schreef "niXman" <[email protected]> het volgende:
> >
> >
> >>
> >> 2012/3/3 Joshua Boyce <[email protected]>:
> >> > 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-faq.html#SourceAndBinaryOnDifferentSites
> >>
> >> Did I understand correctly, that it to me is sufficient to provide the
> >> information for getting the sources for each archive with binaries?
> >>
> >> Since now each archive would contain the information on the project
> >> licenses used for builds, as like as Ruben and sezero do.
> >
> > Note that we both also provide source archives for our builds (under
> > "Toolchain sources"). Just to be clear: I'm not going to call the cops on
> > you, but the GPL is pretty clear on this point.
> >
>
> You haven't answered... According to:
> http://www.gnu.org/licenses/gpl-faq.html#AnonFTPAndSendSources
> http://www.gnu.org/licenses/gpl-faq.html#SourceAndBinaryOnDifferentSites
>
> - am I obliged to upload the sources? Or it is sufficient to provide
> information about where to get the sources?
> I understand it ambiguously...
>
The way I understand it is that you must provide sources (links are ok) and
*build scripts* or at least build instructions for the binaries. This so
that anyone can reproduce your binaries from freely available sources. Arch
Linux for example, only stores build scripts, which can be used with their
pkgbuild tool to download and build the binary packages.
I'm sure that if web hosting space is a problem, you can persuade Kai to
give you limited access to the "Personal Builds" section of the MinGW-w64
sourceforge site like for me and sezero.
Ruben
> >> The builds 4.6.2-release and 4.6.3-release will be updated.
> >>
> >> Ruben, under which license is your patch
> >> "gcc-4.6-posixthreadingandlibstdc++.patch" ?
> >
> > It's a clean backport from GCC 4.7 (current trunk), so I guess the same
> > license as GCC.
> >
> > Ruben
> >
> > PS: I'm attempting to figure out why some of your builds have a
> functioning
> > shared std::thread while all my builds don't. I can see your GCC
> configure
> > flags, but not your winpthreads configure call. Would you care to post
> that
> > please? Thanks.
>
> winpthreads configure flags:
> --host=$HOST
> --target=$TARGET
> --prefix=$MINGW_PREFIX/$TARGET
> --enable-static
> --enable-shared
>
> I can guess why your std::thread does not work ...
> When I reported that this bug may be fixed by replacing:
> > #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
> on:
> > #if SUPPORTS_WEAK && GTHREAD_USE_WEAK && !defined(__MINGW32__)
>
> and Kai fixed it: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52300 I
> checked it with the confidence that I have disabled the patch at my
> built.
> Now, I discovered that it was still enabled. (I sprinkle ashes upon my
> head!)
>
I'll be sure to also try this. I'm not having luck comparing the configure
arguments at all.
Thanks,
Ruben
>
> This means that if you still have a bug with std::threads, then Kai's
> patch does not work.
>
>
> >
> >>
> >>
> >> >
> >> > On Sat, Mar 3, 2012 at 9:47 AM, niXman <[email protected]> wrote:
> >> >>
> >> >> 2012/3/3 Earnie Boyd <[email protected]>:
> >> >> > On Fri, Mar 2, 2012 at 4:45 PM, Joshua Boyce
> >> >> > <[email protected]> wrote:
> >> >> >>
> >> >> >> On Sat, Mar 3, 2012 at 5:13 AM, Luis Lavena <[email protected]
> >
> >> >> >> wrote:
> >> >> >>>
> >> >> >>> On Fri, Mar 2, 2012 at 1:09 PM, niXman <[email protected]>
> 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 :-(
> >> >> >>>
> >> >> >>
> >> >> >> Yep, it can be quite frustrating sometimes. :(
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> http://www.gnu.org/licenses/gpl-faq.html#DistributingSourceIsInconvenient
> >> >>
> >> >> It is very inconvenient, because for each archive with size of 30-60
> >> >> MB, I have to add an archive of sources with size of 150-180 MB.
> >> >> Besides, I doubt that the gcc/binutils/mingw-w64 projects will ever
> >> >> disappear completely, and there wouldn't be any possibility to
> >> >> download the necessary source code revision.
> >> >>
> >> >> Again, I have not uploaded the build scripts and sources for two
> >> >> reasons:
> >> >> 1. Until now nobody asked.
> >> >> 2. On google.code.com the space for the project is limited.
> >> >>
> >> >> but not for that to hide something from someone, or even with any
> >> >> malicious intent.
> >> >>
> >> >> But I agree with the fact that in every build the license files used
> >> >> for each project to be inserted. I will do so.
> >> >>
> >> >> >
> >> >> > So in a nut shell, it is *your* responsibility to provide the exact
> >> >> > source for the binary distribution, including libraries, if someone
> >> >> > asks for it. Not all licenses require source distribution when
> >> >> > distributing the binary but it is a common practice to do so
> anyway.
> >> >> > If you offer a binary on the internet you must provide the source
> on
> >> >> > the internet from a location or locations you control.
> >> >> >
> >> >> > --
> >> >> > Earnie
> >> >> > -- https://sites.google.com/site/earnieboyd
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> ------------------------------------------------------------------------------
> >> >> > Virtualization & Cloud Management Using Capacity Planning
> >> >> > Cloud computing makes use of virtualization - but cloud computing
> >> >> > also focuses on allowing computing to be delivered as a service.
> >> >> > http://www.accelacomm.com/jaw/sfnl/114/51521223/
> >> >> > _______________________________________________
> >> >> > Mingw-w64-public mailing list
> >> >> > [email protected]
> >> >> > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Regards,
> >> >> niXman
> >> >>
> >> >>
> >> >>
> >> >>
> ------------------------------------------------------------------------------
> >> >> Virtualization & Cloud Management Using Capacity Planning
> >> >> Cloud computing makes use of virtualization - but cloud computing
> >> >> also focuses on allowing computing to be delivered as a service.
> >> >> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> >> >> _______________________________________________
> >> >> Mingw-w64-public mailing list
> >> >> [email protected]
> >> >> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> >> >
> >> >
> >> >
> >> >
> >> >
> ------------------------------------------------------------------------------
> >> > Virtualization & Cloud Management Using Capacity Planning
> >> > Cloud computing makes use of virtualization - but cloud computing
> >> > also focuses on allowing computing to be delivered as a service.
> >> > http://www.accelacomm.com/jaw/sfnl/114/51521223/
> >> > _______________________________________________
> >> > Mingw-w64-public mailing list
> >> > [email protected]
> >> > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> >> >
> >>
> >>
> >>
> >> --
> >> Regards,
> >> niXman
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Virtualization & Cloud Management Using Capacity Planning
> >> Cloud computing makes use of virtualization - but cloud computing
> >> also focuses on allowing computing to be delivered as a service.
> >> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> >> _______________________________________________
> >> Mingw-w64-public mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> >
> >
> >
> ------------------------------------------------------------------------------
> > Virtualization & Cloud Management Using Capacity Planning
> > Cloud computing makes use of virtualization - but cloud computing
> > also focuses on allowing computing to be delivered as a service.
> > http://www.accelacomm.com/jaw/sfnl/114/51521223/
> > _______________________________________________
> > Mingw-w64-public mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> >
>
>
>
> --
> Regards,
> niXman
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
