mingw defines __MSVCRT_VERSION__
by Farkas Levente
hi,
while we try to compile gstreamer we got and error
error: storage size of 'stat_results' isn't known
and the reason is that because __stat64 is defined in
/usr/i686-pc-mingw32/sys-root/mingw/include/sys/stat.h
but only as :
----------------------------------------
#if __MSVCRT_VERSION__ >= 0x0601
struct __stat64
{
_dev_t st_dev;
_ino_t st_ino;
_mode_t st_mode;
short st_nlink;
short st_uid;
short st_gid;
_dev_t st_rdev;
__int64 st_size;
__time64_t st_atime;
__time64_t st_mtime;
__time64_t st_ctime;
};
#endif /* __MSVCRT_VERSION__ */
----------------------------------------
and at the same time in
/usr/i686-pc-mingw32/sys-root/mingw/include/_mingw.h :
----------------------------------------
#ifndef __MSVCRT_VERSION__
/* High byte is the major version, low byte is the minor. */
# define __MSVCRT_VERSION__ 0x0600
#endif
----------------------------------------
may be it's not the right place to ask and would be better to move to
mingw mailing list, but it's the right version?
ie. the current runtime really not support __MSVCRT_VERSION__ >= 0x0601?
thanks.
yours.
--
Levente "Si vis pacem para bellum!"
15 years, 2 months
[Bug 490704] Review Request: mingw32-liboil - MinGW Windows liboil library
by Red Hat Bugzilla
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=490704
--- Comment #9 from Richard W.M. Jones <rjones(a)redhat.com> 2009-03-19 05:03:08 EDT ---
(In reply to comment #8)
> for #5 where does this Auto-buildrequires comes from?
>From Fedora of course:
https://admin.fedoraproject.org/pkgdb/packages/name/auto-buildrequires
> anyway it's strange that it can be build in mock without these BRs. also the
Not strange. Autoconf can decide to compile the package differently
depending on the presence or absence of dependencies.
> native packages has no such BRs (eg gettext). on the other hand all these req
> are comes from gtk2 BR. do you really think i should add them?
HOWEVER in this case I suspect that the dependencies come from
glib2, so you can ignore them, as I said above.
> i add
> BuildRequires: pkgconfig
> Requires: pkgconfig
> the changelog contains the name of the real packages i'm just submit it for rr.
Can you post the new URLs please.
--
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.
15 years, 2 months
[Bug 490704] Review Request: mingw32-liboil - MinGW Windows liboil library
by Red Hat Bugzilla
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=490704
Levente Farkas <lfarkas(a)lfarkas.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag|needinfo?(lfarkas(a)lfarkas.o |
|rg) |
--- Comment #8 from Levente Farkas <lfarkas(a)lfarkas.org> 2009-03-18 18:13:11 EDT ---
for #5 where does this Auto-buildrequires comes from?
anyway it's strange that it can be build in mock without these BRs. also the
native packages has no such BRs (eg gettext). on the other hand all these req
are comes from gtk2 BR. do you really think i should add them?
i add
BuildRequires: pkgconfig
Requires: pkgconfig
the changelog contains the name of the real packages i'm just submit it for rr.
--
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.
15 years, 2 months
[Bug 490704] Review Request: mingw32-liboil - MinGW Windows liboil library
by Red Hat Bugzilla
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=490704
--- Comment #7 from Richard W.M. Jones <rjones(a)redhat.com> 2009-03-18 06:57:48 EDT ---
+ rpmlint output
+ package name satisfies the packaging naming guidelines
+ specfile name matches the package base name
+ package should satisfy packaging guidelines
+ license meets guidelines and is acceptable to Fedora
+ license matches the actual package license
+ %doc includes license file
+ spec file written in American English
- spec file is legible
(see below)
+ upstream sources match sources in the srpm
11dd39b1ca13ce2e0618d4df8303f137 822195
+ package successfully builds on at least one architecture
n/a ExcludeArch bugs filed
+ BuildRequires list all build dependencies
n/a %find_lang instead of %{_datadir}/locale/*
n/a binary RPM with shared library files must call ldconfig in %post and
%postun
n/a does not use Prefix: /usr
n/a package owns all directories it creates
+ no duplicate files in %files
+ %defattr line
+ %clean contains rm -rf $RPM_BUILD_ROOT
+ consistent use of macros
+ package must contain code or permissible content
n/a large documentation files should go in -doc subpackage
+ files marked %doc should not affect package
n/a header files should be in -devel
n/a static libraries should be in -static
- packages containing pkgconfig (.pc) files need 'Requires: pkgconfig'
n/a libfoo.so must go in -devel
n/a -devel must require the fully versioned base
n/a packages should not contain libtool .la files
n/a packages containing GUI apps must include %{name}.desktop file
+ packages must not own files or directories owned by other packages
+ %install must start with rm -rf %{buildroot} etc.
+ filenames must be valid UTF-8
Optional:
n/a if there is no license file, packager should query upstream
n/a translations of description and summary for non-English languages, if
available
+ reviewer should build the package in mock
+ the package should build into binary RPMs on all supported architectures
- review should test the package functions as described
n/a scriptlets should be sane
n/a pkgconfig files should go in -devel
n/a shouldn't have file dependencies outside /etc /bin /sbin /usr/bin or
/usr/sbin
-------------
Couple of things:
(1) Please add your real name and email address in the first
%changelog description.
(2) The package must have:
Requires: pkgconfig
When you create a new package, bump the release number and
add a new changelog entry.
You can probably ignore comment 5, since the BuildRequires
look OK.
--
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.
15 years, 2 months