On Tue, Mar 2, 2021 at 6:46 AM Richard W.M. Jones wrote:
> [Adding the devel list, since this change would obviously affect
> several "base" packages.]
>
> On Mon, Mar 01, 2021 at 01:31:13PM +, Daniel P. Berrangé wrote:
> > Way back when we first started the mingw project in Fedora we took th
Please do!
--Greg
On Fri, May 22, 2020 at 1:50 PM Sandro Mani wrote:
> Hi
>
> I'm thinking of adding %mingw_make_build and %mingw_make_install as
> counterparts to %make_build and %make install, see [1].
> Comments/objections?
>
> Sandro
>
> [1] https://src.fedoraproject.org/rpms/mingw-filesyst
Has anyone undertaken to create Haskell cross-compile MinGW efforts? Is
there any interest in that? I have a small project and the best library to
handle it that I can find, so far, is written in Haskell (pandoc). It
officially supports Windows, and the Haskell compiler docs include
information on
On Mon, Aug 12, 2019 at 7:22 PM Michael Cronenworth wrote:
> On 8/12/19 9:11 AM, Greg Hellings wrote:
> > In 2019, is there any reason to just not ship a 32-bit Windows binary?
> Does anyone
> > still use non-64-bit Windows?
>
> The problem isn't with us or with Mi
In 2019, is there any reason to just not ship a 32-bit Windows binary? Does
anyone still use non-64-bit Windows?
--Greg
On Mon, Aug 12, 2019 at 9:07 AM Sandro Mani wrote:
> Hi
>
> I've got a working build of mingw64-rust [1] with which I'm able to
> successfully build a current version of mingw
On Mon, Apr 16, 2018 at 11:57 PM, Michael Cronenworth
wrote:
> I finally had time to fix this script. One and only time I'll run it for
> F27. I'll run it for F28 in the next email.
>
Where does this script live? Is it something that I could poke so I can
look at it?
--Greg
__
nenworth wrote:
> On 04/26/2018 11:13 AM, Greg Hellings wrote:
>
>> What's required for the owner? What duties and responsibilities does it
>> come with?
>>
>>
> Interested? I'm going to have Fedora Infra update the owners soon.
>
> _
What's required for the owner? What duties and responsibilities does it
come with?
--Greg
On Thu, Apr 26, 2018 at 11:10 AM, Michael Cronenworth
wrote:
> Hi all,
>
> If there is anyone who would like to become the mailing list owner please
> reply either to myself or this list posting.
>
> I don
On Thu, Jun 1, 2017 at 12:32 PM, Michael Cronenworth
wrote:
> +---+---+---
> +-+
> | nspr | 4.14.0| 4.14.0|
>|
> | mingw-nspr| 4.14 | 4.14
What phase of the build are you getting this message in?
--Greg
On Mon, Jan 16, 2017 at 9:03 AM, Richard Shaw wrote:
> Never mind The ";"'s are suppressed in the output, back to the drawing
> board...
>
> Thanks,
> Richard
>
>
> ___
> mingw mailin
Thanks, Michael. Just updated my two that were behind native.
libgsf I'm a few minors ahead, and was still 3 minors behind upstream. I've
updated that - not sure why native is lagging so far behind. I'll reach out
to those maintainers about that.
--Greg
On Tue, Nov 1, 2016 at 9:29 AM, Michael Cr
Erik is correct. mplayer does not use autotools but instead has a
hand-crafted Configure script. It may or may not support cross-compiling.
If not, you'll need to figure out how mplayer is normally built for Windows
(I know it is available on the Win32 platform) and either leverage that
process or
On Sun, May 12, 2013 at 9:54 AM, Erik van Pienbroek wrote:
> Erik van Pienbroek schreef op zo 12-05-2013 om 16:35 [+0200]:
>
> > The following packages FAILED to rebuild:
>
> All build failures (except for gtk3) seem to be caused by the
> introduction of winpthreads, so we need to resolve these fi
2013/5/6 Michael Cronenworth
> --
> MinGW/native package version discrepancies
> +---+---+---+
> | libgsf| 1.14.26 | 1.14.26 |
> | mingw-libgsf | 1.14.2
I have one package that this might affect, but I won't know for sure how it
affects it until the feature is introduced. Currently in mingw-clucene I
have threading disabled on 64-bit platforms because of issues with linking
it against the existing threads library. Once a new threading library is
in
This makes me curious:
Why is Fedora maintaining a whole separate set of packages for the
MinGW spin of builds when they could be all built from the same
packages? Then all packages would be updated with a single effort, and
they would share patchsets, etc. Since building is done out of stream
any
16 matches
Mail list logo
