Version 2.0.2 compatibility
#11
Hi @krovit! I happened to have written most of this logic Smile I would look in
internal/c/c_compiler
, do you only have one folder called
x86_64-w64-mingw32
? Or do you also have a folder called
i686-w64-mingw32
?

Basically what's happening is that those folders are checked to determine whether you have the 32-bit compiler or the 64-bit compiler, and that then controls the architecture of that
data.o
file. There might be better ways for us to do that, but since the 32-bit and 64-bit releases will always only have one or the other of those folders it generally works fine. Unfortunately since you did clarify you avoided copying the new QB64-PE version on top of an old version you really shouldn't have both folders there. I also just went and checked the 64-bit release download (
qb64pe_win-x64-3.4.1.7z
) and it only has the
x86_64-w64-mingw32
as expected. It's not really clear to me how you could have ended up with both folders Undecided

If you don't mind, something that would be useful would be if you could go to line 77 in the
Makefile
and add this line:

Code: (Select All)
$(info wildcard search: $(wildcard $(PATH_INTERNAL_C)\c_compiler\i686-w64-mingw32))

The
wildcard search:
text should then appear in the
internal/temp/compilelog.txt
file you listed here. For the 64-bit version of QB64-PE there shouldn't be anything listed after
wildcard search:
. If it's not blank then whatever is listed is the source of the problem.
Reply


Messages In This Thread
Version 2.0.2 compatibility - by krovit - 11-25-2022, 09:22 AM
RE: Version 2.0.2 compatibility - by mnrvovrfc - 11-25-2022, 09:37 AM
RE: Version 2.0.2 compatibility - by krovit - 11-25-2022, 11:07 AM
RE: Version 2.0.2 compatibility - by mnrvovrfc - 11-25-2022, 05:15 PM
RE: Version 2.0.2 compatibility - by krovit - 11-25-2022, 06:32 PM
RE: Version 2.0.2 compatibility - by SMcNeill - 11-25-2022, 11:16 AM
RE: Version 2.0.2 compatibility - by krovit - 11-25-2022, 11:25 AM
RE: Version 2.0.2 compatibility - by doppler - 11-25-2022, 01:22 PM
RE: Version 2.0.2 compatibility - by SMcNeill - 11-25-2022, 06:11 PM
RE: Version 2.0.2 compatibility - by mnrvovrfc - 11-25-2022, 07:32 PM
RE: Version 2.0.2 compatibility - by DSMan195276 - 11-26-2022, 03:37 AM
RE: Version 2.0.2 compatibility - by krovit - 11-26-2022, 10:04 AM
RE: Version 2.0.2 compatibility - by SMcNeill - 11-26-2022, 10:31 AM
RE: Version 2.0.2 compatibility - by krovit - 11-26-2022, 10:39 AM
RE: Version 2.0.2 compatibility - by DSMan195276 - 11-26-2022, 07:24 PM
RE: Version 2.0.2 compatibility - by krovit - 11-27-2022, 08:45 AM
RE: Version 2.0.2 compatibility - by DSMan195276 - 11-27-2022, 09:28 PM
RE: Version 2.0.2 compatibility - by krovit - 11-29-2022, 11:04 AM
RE: Version 2.0.2 compatibility - by mnrvovrfc - 11-29-2022, 01:08 PM
RE: Version 2.0.2 compatibility - by SMcNeill - 11-29-2022, 03:14 PM
RE: Version 2.0.2 compatibility - by krovit - 11-30-2022, 09:04 AM
RE: Version 2.0.2 compatibility - by DSMan195276 - 11-30-2022, 02:45 PM
RE: Version 2.0.2 compatibility - by RhoSigma - 11-30-2022, 06:03 PM
RE: Version 2.0.2 compatibility - by Stuart - 11-30-2022, 11:22 PM
RE: Version 2.0.2 compatibility - by krovit - 12-01-2022, 12:32 AM
RE: Version 2.0.2 compatibility - by mnrvovrfc - 12-01-2022, 03:52 PM
RE: Version 2.0.2 compatibility - by mnrvovrfc - 12-01-2022, 01:40 AM
RE: Version 2.0.2 compatibility - by krovit - 12-02-2022, 08:01 AM
RE: Version 2.0.2 compatibility - by mnrvovrfc - 12-02-2022, 08:19 AM



Users browsing this thread: 6 Guest(s)