Re: [Mingw-w64-public] Autotools & git

2016-08-16 Thread Jim Michaels
; "mingw-w64-public@lists.sourceforge.net" *Sent:* Monday, June 6, 2016 2:30 PM *Subject:* Re: [Mingw-w64-public] Autotools & git I for one am grateful for the configure script. I’m sure I’m not alone. Ruben Van: Jean-Baptiste Kempf Verzonden: maandag 6 juni 2016 21:49 Aan: mi

Re: [Mingw-w64-public] Autotools & git

2016-06-06 Thread Ruben Van Boxem
I for one am grateful for the configure script. I’m sure I’m not alone. Ruben Van: Jean-Baptiste Kempf Verzonden: maandag 6 juni 2016 21:49 Aan: mingw-w64-public@lists.sourceforge.net Onderwerp: Re: [Mingw-w64-public] Autotools & git On 06 Jun, Ozkan Sezer wrote : > Not everyone would h

Re: [Mingw-w64-public] Autotools & git

2016-06-06 Thread Jean-Baptiste Kempf
On 06 Jun, Ozkan Sezer wrote : > Not everyone would have the required autofoo installed on their > systems to generate the configury. To me, it is polite to have the > generated files as they are intended to be in the repo. If you don't have autotools, then why are you compiling mingw64? If you ar

Re: [Mingw-w64-public] Autotools & git

2016-06-06 Thread lh mouse
p/gcc --- -- Best regards, lh_mouse 2016-06-07 - 发件人:Hugo Beauzée-Luyssen 发送日期:2016-06-07 00:37 收件人:mingw-w64-public@lists.sourceforge.net 抄送: 主题:[Mingw-w64-public] Autotools & git Hi, I'm wondering about the rational

Re: [Mingw-w64-public] Autotools & git

2016-06-06 Thread Ozkan Sezer
On 6/6/16, Hugo Beauzée-Luyssen wrote: > Hi, > > I'm wondering about the rational for having all autotools generated > files commited to the git repository. > Is there a specific reason for that? Or would it be OK to provide a > patch that adds a bootstrap script for all project & removes the said

[Mingw-w64-public] Autotools & git

2016-06-06 Thread Hugo Beauzée-Luyssen
Hi, I'm wondering about the rational for having all autotools generated files commited to the git repository. Is there a specific reason for that? Or would it be OK to provide a patch that adds a bootstrap script for all project & removes the said generated files? Regards, ---

Re: [Mingw-w64-public] autotools

2012-01-06 Thread Earnie Boyd
On Thu, Jan 5, 2012 at 5:09 PM, JonY wrote: > > iirc Perl 5.8 for MSYS is out, you could try to persuade the maintainers > to make it threaded. > That would be Chuck Wilson who IIRC monitors this list but discussion should happen at mingw-us...@lists.sourceforge.net. -- Earnie -- https://sites

Re: [Mingw-w64-public] autotools

2012-01-05 Thread JonY
On 1/6/2012 01:29, Alon Bar-Lev wrote: > You should try the mingw package, msys is unmaintained, while the > recent cygwin introduced proper mingw-w64 and recent auto tools which > make it a great alternative. > This really has nothing to do with MSYS, though I do encourage using Cygwin over it o

Re: [Mingw-w64-public] autotools

2012-01-05 Thread Alon Bar-Lev
You should try the mingw package, msys is unmaintained, while the recent cygwin introduced proper mingw-w64 and recent auto tools which make it a great alternative. On Thu, Jan 5, 2012 at 7:25 PM, Patrick von Reth wrote: > > Hi the autotools package contains a broken symbolic link, > autotools\s

[Mingw-w64-public] autotools

2012-01-05 Thread Patrick von Reth
Hi the autotools package contains a broken symbolic link, autotools\share\aclocal points to /usr/share/aclocal wont work if extracted with a normal tool. Also if the package gets updated can you please build it with disabled perl threads? The msys-perl doesn't support threads so some autotools oper

Re: [Mingw-w64-public] "Autotools sux" [WAS: recipes for automated 32bit mingw build?]

2011-08-09 Thread JonY
On 8/10/2011 01:12, Jon wrote: >> On 8/9/2011 22:19, Ruben Van Boxem wrote: >>> 2011/8/9 Earnie : Ruben Van Boxem wrote: >> Heh, the solution is to use autotools, all the way, never >> compromise on quality. There are a lot of packages too pretentious >> to use autotools... >>

Re: [Mingw-w64-public] "Autotools sux" [WAS: recipes for automated 32bit mingw build?]

2011-08-09 Thread Jon
> On 8/9/2011 22:19, Ruben Van Boxem wrote: > > 2011/8/9 Earnie : > >> Ruben Van Boxem wrote: > >> > Heh, the solution is to use autotools, all the way, never > compromise on quality. There are a lot of packages too pretentious > to use autotools... > >>> > >>> Bull shit. Hardly a so

Re: [Mingw-w64-public] "Autotools sux" [WAS: recipes for automated 32bit mingw build?]

2011-08-09 Thread JonY
On 8/9/2011 22:19, Ruben Van Boxem wrote: > 2011/8/9 Earnie : >> Ruben Van Boxem wrote: >> Heh, the solution is to use autotools, all the way, never compromise on quality. There are a lot of packages too pretentious to use autotools... >>> >>> Bull shit. Hardly a solution. Sorry for

Re: [Mingw-w64-public] "Autotools sux" [WAS: recipes for automated 32bit mingw build?]

2011-08-09 Thread Ruben Van Boxem
2011/8/9 Earnie : > Ruben Van Boxem wrote: > >>> Heh, the solution is to use autotools, all the way, never >>> compromise on quality. There are a lot of packages too pretentious >>> to use autotools... >> >> Bull shit. Hardly a solution. Sorry for the direct words, but you >> can't possibly force a

Re: [Mingw-w64-public] "Autotools sux" [WAS: recipes for automated 32bit mingw build?]

2011-08-09 Thread Earnie
Ruben Van Boxem wrote: >> Heh, the solution is to use autotools, all the way, never >> compromise on quality. There are a lot of packages too pretentious >> to use autotools... > > Bull shit. Hardly a solution. Sorry for the direct words, but you > can't possibly force autotools on the world. I ha