GNU C++ Compiler error

[Pete]

Well of course that's better. Don't forget, I was channeling Clippy.

Pete

[bplus]

RE: Steve's even better... reply

Yes all QB files in separate folder but that's not all I need to do.

Here is my checklist, to which I add some other item every new version it seems:

Code: (Select All)

Downloaded
Extract to Desktop to avoid notifications
add files to QB64.exe folder from QB Files - might just need Direntry.h for old files, Falcon.h for sure

test new download IDE
    set Multi Highlite off Options > IDE Colors DIALOG
    set comments color to 0,180,120 in default IDE display theme
    set Run > * Output .Exe to Source folder
    set Dialog Load File BULLET off so can start in Short cuts directory OPTIONS > LAST ITEM
    use Camoflage for 2nd screen
    large print options > display [x] use monospace lucon.ttf 18 pixels width 116, height 39
    
Windows stuff:
Shortcut to new exe
Shortcut properties > startup = QB Files (full path)
REMOVE OLD VERSION SHORTCUTS
Pin to startup and taskbar

get bas assoc to new exe
    rename old VERSION with old to disable last assoc
    pick a bas and Open With...
    check box always open with
    browse other apps to new the new QB64.exe and use!
    remove old from old version name once new assoc works

color schemes qb64/internal/config.ini

[IDE COLOR SCHEMES]
Instructions1="Create custom color schemes in the IDE (Options->IDE Colors)."
Instructions2="Custom color schemes will be stored in this section."
Scheme1$=StarryNight|216216216069118226049186226000177226245128128000216128000000039078000128000088108170170170
Scheme2$=Forest|000186000180108000000157069000167088255128064000167098040020010070070000000088000078167000
Scheme3$=Red Light District|196157088255118000255226226255167167255108108255167000186039000059020000255070000255049000
Scheme4$=GreyBound|245118118078206075110163043092231124252145031255049078036061040089001020094002042178174157
Scheme5$=Dk camo mod|226226167098098227255118138255118186137137245020147157043045037010000020088088088170170170
Scheme6$=camo-mod|196196196000137177000255000128128000137177147000180255000020020100100100000147177170170170

Plus a good time to run a backup of QB File and clear the Pictures folder and review and refile Downloads of bas stuff (do that first actually).

[Kernelpanic]

Sometimes one can really to make a serious mistake. 

[Cobalt]

*sigh* *sigh*

[eoredson]

How about the following:

Download QB64pe-4.0.0.zip
Extract to C:\ preserving pathnames.
Drop to Cmd then
C>Cd\
C>Ren QB64pe QB64pe.old
C>Ren QB64pe-4.0.0 QB64pe
C>Cd\QB64pe
C>@echo Run install command
C>setup_win.cmd
C>Exit

[Kernelpanic]

How about the following:

Download QB64pe-4.0.0.zip
Extract to C:\ preserving pathnames.
Drop to Cmd then
C>Cd\
C>Ren QB64pe QB64pe.old
C>Ren QB64pe-4.0.0 QB64pe
C>Cd\QB64pe
C>@echo Run install command
C>setup_win.cmd
C>Exit

Without offending you - what are you doing there? 

[eoredson]

Without offending you - what are you doing there? 

Trying to build the QB64pe source into the original \QB64pe directory.

[JRace]

Extract to C:\ preserving pathnames.

This implies that you are running on Windows?

If so, there is no need to build from source unless you are making changes to the compiler.  The Windows version of QB64PE is ready to use out of the box.  Just unpack and go.

BEFORE UNPACKING THE WINDOWS .7z ARCHIVE: delete your old "qb64pe" folder or rename it  Name it to "qb64pe_OLD", or "Q", or "Fred", or whatever.  The new name does not matter as long as you free up the name "qb64pe" for reuse.

If you run an antivirus then you may have to go through the rigmarole of whitelisting the new PE with your A/V.

If the new installation has the same directory name as your old installation, then any old file associations, Open With options, etc should work just fine on the new version, with no changes needed.

The entire Windows compiler suite is contained in a folder called "qb64pe", so just extract the archive wherever you want and you are good to go.

---

((If you insist on building from source, just do it in the "QB64pe-4.0.0" folder.  If successful you can then move the shiny new PE files into a good (and EMPTY!!!) home of their very own.))

[eoredson]

Extract to C:\ preserving pathnames.

This implies that you are running on Windows?

If so, there is no need to build from source unless you are making changes to the compiler.  The Windows version of QB64PE is ready to use out of the box.  Just unpack and go.

BEFORE UNPACKING THE WINDOWS .7z ARCHIVE: delete your old "qb64pe" folder or rename it  Name it to "qb64pe_OLD", or "Q", or "Fred", or whatever.  The point of this is to free up the name "qb64pe" for reuse.

If you run an antivirus then you may have to go through the rigmarole of whitelisting the new PE with your A/V.

If the new installation has the same directory name as your old installation, then any old file associations, Open With options, etc should work just fine on the new version, with no changes needed.

The entire Windows compiler suite is contained in a folder called "qb64pe", so just extract the archive wherever you want and you are good to go.

---

((If you insist on building from source, just do it in the "QB64pe-4.0.0" folder.  If successful you can then move the shiny new PE files into a good home of their very own.))

I have downloaded the file:

qb64pe_win-x86-4.0.0.7z

and had compilation issues and was told to build the source from:

QB64pe-4.0.0.zip

which extracts into \QB64pe-4.0.0 but I want it in \QB64pe

[JRace]

You beat my last edit:

Do the build in the "QB64pe-4.0.0" folder.  If successful you can then move the shiny new PE files into a good (and EMPTY!!!) home of their very own.


Reading your compilelog.txt, it looks like some essential files got clobbered, like you may have installed 4.0.0 onto an older version of PE.

QB64PE on Windows is -->2<-- compilers with many thousands of files built to work with other files of the same version.  Even if the names don't change, the contents of many of those files change from one PE version to the next, so lose that idea about merging directories.  That's, NEVER a good idea when updating software suite like PE.  Most software updates remove or isolate the old before cleanly installing the new, and that's the way we should do it.  Unless the author explicitly says a new-over-old update is safe, assume it's not.

I recommend trying a COMPLETELY FRESH extraction of the .7z archive.