Re: [MinGW-users] _wfindnext64i32 not declared and other build errors

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [MinGW-users] _wfindnext64i32 not declared and other build errors

Earnie Boyd
>
> [*] Sure, it is *possible* to configure MinGW to work with MSVCR80.DLL
> and its later derivatives, but I am not going to encourage it.
>

But if you do be sure that all of the application, including any DLL used by
it, is using the same MSVCR library to avoid memory collisions.  Each MSVC
Runtime DLL would manage its own version of its memory pointer stack.

--
Earnie



------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe
Reply | Threaded
Open this post in threaded view
|

Re: [MinGW-users] _wfindnext64i32 not declared and other build errors

Jacob Hartmann
On Mon, Mar 16, 2015 at 2:39 PM, Gisle Vanem <[hidden email]> wrote:
 DefaultResourceProvider.cpp:216:33: error: '_wfindnext64i32' was not declared in this scope

Try to add '-D__MSVCRT_VERSION__=0x0800' to your your CFLAGS. An
link with -lmsvcr80.

--gv

Sorry for being a bit late, I fell ill and I am just recovering today. I tried that, but got the same error. I have also read what others have stated, and it appears that the actual code must be changed. I will report this back to the CEGUI team and see what we can work out.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe
Reply | Threaded
Open this post in threaded view
|

Re: [MinGW-users] _wfindnext64i32 not declared and other build errors

Jacob Hartmann
On Sat, Mar 21, 2015 at 10:36 AM, Jacob Hartmann <[hidden email]> wrote:
On Mon, Mar 16, 2015 at 2:39 PM, Gisle Vanem <[hidden email]> wrote:
 DefaultResourceProvider.cpp:216:33: error: '_wfindnext64i32' was not declared in this scope

Try to add '-D__MSVCRT_VERSION__=0x0800' to your your CFLAGS. An
link with -lmsvcr80.

--gv

Sorry for being a bit late, I fell ill and I am just recovering today. I tried that, but got the same error. I have also read what others have stated, and it appears that the actual code must be changed. I will report this back to the CEGUI team and see what we can work out.


Right, the developer of CEGUI has a few questions (as does myself). He wants to know if I am using 64 bit time, or 32 bit time. Now, I am not exactly sure how to check this, but my gut is saying something about build targets/architecture. Is this correct? He understands the situation as this: "the generic function should use 32 bit time but in your case it instead switches to use the 64 bit time version." 

What could be wrong with my setup of Mingw, if I am using _wfindnext() and getting this error?

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe
Reply | Threaded
Open this post in threaded view
|

Re: [MinGW-users] _wfindnext64i32 not declared and other build errors

Keith Marshall
On 23/03/15 10:19, Jacob Hartmann wrote:
> Right, the developer of CEGUI has a few questions (as does myself).
> He wants to know if I am using 64 bit time, or 32 bit time. Now, I am
> not exactly sure how to check this, but my gut is saying something
> about build targets/architecture. Is this correct? He understands the
> situation as this: "the generic function should use 32 bit time but
> in your case it instead switches to use the 64 bit time version."

N.B. The following applies to the 32-bit builds provided by MinGW.org.
It may not apply to 64-bit builds, nor even to 32-bit builds from any
other source; such builds are not supported by MinGW.org, nor by this
mailing list.

If you read Microsoft's documentation, on MSDN, you will assume that
_wfindnext() uses 64-bit time, unless you define _USE_32BIT_TIME_T.
However, that documentation refers primarily to MSVC, and the runtime
DLLs on which it depends; today these are descendants of MSVCR80.DLL.
Thus, in respect of its applicability to MinGW, the validity of this
MSDN documentation is decidedly questionable.

> What could be wrong with my setup of Mingw, if I am using
> _wfindnext() and getting this error?

Your original posting said you were getting an unresolved symbol
reference for _wfindnext64i32(), which uses 64-bit time and 32-bit file
size fields.  However, this symbol was introduced in MSVCR80.DLL; it
does not appear in any version of MSVCRT.DLL, AFAIK.  Unless you jump
through several awkward hoops, your MinGW setup will link with
MSVCRT.DLL; it will *not* link with MSVCR80.DLL, nor any of its
descendants, (and simply adding -lmsvcr80 is *not* the way to change
this; doing so is asking for trouble).

If you are using a standard MinGW setup[*], if you use _wfindnext() that
is exactly the symbol your application should require; it should *not*
be trying to resolve it as _wfindnext64i32().  In MSVCRT.DLL, both
_wfindfirst() and _wfindnext() use 32-bit time and 32-bit file size;
Microsoft's _USE_32BIT_TIME_T nonsense seems to be irrelevant.

[*] Unless you have the badly broken mingwrt-4.x runtime.  If this is
the case you should get rid of it, and its w32api-4.x companion, as soon
as you possibly can; install mingwrt-3.21 and w32api-3.17 in their stead.

--
Regards,
Keith.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:[hidden email]?subject=unsubscribe