Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=479874
Jason Tibbitts <tibbs(a)math.uh.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag| |needinfo?(itamar@ispbrasil.
| |com.br)
--- Comment #14 from Jason Tibbitts <tibbs(a)math.uh.edu> 2009-07-17 18:56:37 EDT ---
It's been six weeks since that ping. I guess this should be closed soon.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=509940
--- Comment #2 from dulsi(a)identicalsoftware.com 2009-07-17 09:30:49 EDT ---
mingw32-sdl is installed. Here is part of rpm -qi mingw32-SDL.
Name : mingw32-SDL Relocations: (not relocatable)
Version : 1.2.13 Vendor: Fedora Project
If you look at FindSDL.cmake, you will see the FIND_PATH for SDL.h. It is
search a bunch of paths but nothing that can be found from the root path
/usr/i686-pc-mingw32. The cmake mailing list suggested adding
/usr/i686-pc-mingw32/sys-root/mingw to the root path but the FIND_PATH in
FindSDL.cmake isn't looking in /include/SDL so it still doesn't find it. It
was mentioned that the FindSDL.cmake is using an old way to look for the
appropriate include files. Not sure what the current suggested practice is.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502692
--- Comment #7 from Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> 2009-07-17 06:32:39 EDT ---
For the record, mingw32-gcc has been submitted as #512323
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502692
Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |WONTFIX
--- Comment #6 from Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> 2009-07-17 06:21:10 EDT ---
I've made a working (building, no runtime test yet). mingw32-gc package.
The problem is that's the 9.2 alpha release.
I don't remember which mingw32 package I haven't yet submitted will requires
mingw32-libatomic_ops, so that can wait a little for gc 9.2 to move to stable
from upstream.
So yes, the plan is to have it merged with gc.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=509940
Erik van Pienbroek <erik-fedora(a)vanpienbroek.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL|fedora-mingw(a)lists.fedorapr |
|oject.org |
CC| |fedora-mingw(a)lists.fedorapr
| |oject.org
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502692
--- Comment #5 from Erik van Pienbroek <erik-fedora(a)vanpienbroek.nl> 2009-07-17 06:11:21 EDT ---
Do you still want me to review this package (as the native one has been
orphaned) ?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
would be nice to rewrite %_mingw32_cflags to %__global_cflags
-------- Original Message --------
Subject: Re: %{_global_cflags}
Date: Mon, 13 Jul 2009 17:17:00 +0200
From: Michael Schwendt <mschwendt(a)gmail.com>
Reply-To: Development discussions related to Fedora
<fedora-devel-list(a)redhat.com>
To: Development discussions related to Fedora <fedora-devel-list(a)redhat.com>
References: <fac47fca0907130731p7a930455t99d71a4bd2c080a0(a)mail.gmail.com>
On Mon, 13 Jul 2009 16:31:34 +0200, Marcus wrote:
> Hi all.
>
> In http://fedoraproject.org/wiki/Packaging:RPMMacros#Build_flags_macros
> %{_global_cflags} is set and %{_optflags} references
> %{__global_cflags} (double underscores). Is this correct or should it
> say %{_global_cflags}?
%{optflags} and %{__global_cflags}
$ rpm --eval %optflags
-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i586
-mtune=generic -fasynchronous-unwind-tables
$ rpm --eval %__global_cflags
-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
Levente "Si vis pacem para bellum!"
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502691
Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution| |NOTABUG
--- Comment #2 from Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> 2009-07-09 07:17:19 EDT ---
Sorry, this package was added with #467391
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.