• AVR Freaks

Hot!XC8 v2.30 bug with MPLABX v5.45 integration

Author
dan1138
Super Member
  • Total Posts : 4162
  • Reward points : 0
  • Joined: 2007/02/21 23:04:16
  • Location: 0
  • Status: offline
2020/11/08 12:27:58 (permalink)
4.5 (2)

XC8 v2.30 bug with MPLABX v5.45 integration

There is an integration bug with XC8 v2.30 and MPLABX v5.45 that has been fixed in the XC8 v2.31 release,
 
The bug fix is not mentioned in the release notes for XC8 v2.31
 
This bug has not been described on this forum so far.
 
This is what I have found:
 
Workstation: Windows7-Pro 64-bit
MPLABX v5.45
XC8 v2.30
Target controller: PIC18F26K80
 
Bug:
The XC8 v2.30 compiler cannot be selected in the project properties.
Attachments are not available: Download requirements not met
 
 

Attachment(s)

Attachments are not available: Download requirements not met
#1

11 Replies Related Threads

    Ddhar
    New Member
    • Total Posts : 6
    • Reward points : 0
    • Joined: 2020/05/14 22:52:08
    • Location: 0
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/10 14:50:56 (permalink)
    0
    This issue is fixed in the latest compiler XC8 v2.31 
    Downloadable from https://www.microchip.com/en-us/development-tools-tools-and-software/mplab-xc-compilers
    #2
    ric
    Super Member
    • Total Posts : 29435
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: online
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/10 14:55:53 (permalink)
    0 (2)
    Ddhar
    This issue is fixed in the latest compiler XC8 v2.31 

    That is exactly what Dan's post says.
    His point is that the fix is NOT mentioned in the release notes.
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #3
    Ddhar
    New Member
    • Total Posts : 6
    • Reward points : 0
    • Joined: 2020/05/14 22:52:08
    • Location: 0
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/11 01:54:26 (permalink)
    0

    5.   Fixed Issues

    5.1.     Version 2.31
    Unexplained compiler failures (XC8-2367) When running on Windows platforms that had the system temporary directory set to a path that included a dot '.' character, the compiler may have failed to execute.
    #4
    crosland
    Super Member
    • Total Posts : 2143
    • Reward points : 0
    • Joined: 2005/05/10 10:55:05
    • Location: Warks, UK
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/11 02:02:33 (permalink)
    +2 (4)
    Ddhar

    5.   Fixed Issues

    5.1.     Version 2.31Unexplained compiler failures (XC8-2367) When running on Windows platforms that had the system temporary directory set to a path that included a dot '.' character, the compiler may have failed to execute.



    Compiler failing to execute is NOT the same as IDE failing to provide the compiler as an option.
     
    You guys really need a rocket under you a***s and get your QA and doc procedures sorted out. See also https://www.microchip.com/forums/m1157412.aspx
     
    #5
    mad_c
    Super Member
    • Total Posts : 1271
    • Reward points : 0
    • Joined: 2010/12/12 17:48:27
    • Location: Brisbane, Australia
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/15 18:53:14 (permalink)
    +3 (3)
    crosland
    Compiler failing to execute is NOT the same as IDE failing to provide the compiler as an option.

    ... except when the IDE has to run the compiler to determine if it should be included in the list. My apologies if that was not clear. The issue related to an unusual behaviour in a Windows library routine and could occur anytime that routine was called. Basically, any changed behaviour in 2.31 can be attributed to that bugfix mentioned in the release notes, as that was the only thing that was altered in this release (aside from new device support).
     
    Jeff.
    #6
    dan1138
    Super Member
    • Total Posts : 4162
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/15 20:11:46 (permalink)
    +1 (3)
    Jeff,

    Why is the bug description so cryptic?

    How would it be possible for a developer to connect this bug fix to the observed behavior?

    MPLABX v5.45 seems to show that XC8 v2.30 is available but it will not use it.

    And you say this is because an un-observable string with a dot (.) in it has a parsing issue with some buried Java craplet ?

    Also the link to the release notes on the XC8 v2.31 compiler download page still links to the v2.30 release notes.

    Crosland should fuel up that rocket.
    post edited by dan1138 - 2020/11/15 20:48:41
    #7
    mad_c
    Super Member
    • Total Posts : 1271
    • Reward points : 0
    • Joined: 2010/12/12 17:48:27
    • Location: Brisbane, Australia
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/15 23:06:53 (permalink)
    +1 (1)
    dan1138
    Why is the bug description so cryptic?

    The compiler might fail if any compiler application attempts to create a temporary file using Microsoft's library routine and your Windows/environment variable temp path has a dot in there somewhere. Temp files are created often. Failing when the IDE runs the compiler to verify versions is just one case, and even I had no idea of how the IDE would react to that situation. I can request that the developers write a more comprehensive descriptions of potential failure mechanics, but there will always be occasions where such a description might be inadequate or overwhelming, particularly when what you see is the IDE's response to a compiler failure.

    Also the link to the release notes on the XC8 v2.31 compiler download page still links to the v2.30 release notes.

    Thanks for pointing that out. Some of the webpage updates should be performed automatically once digital assets are released, but that sometimes takes a long time and then sometimes never. That rocket may need to be targeted at our server software rather than someone's a***s, as it was so eloquently stated earlier. I know this does help your cause, but many of us wish we could use our own arsenal on these systems too.
     
    Jeff.
    #8
    crosland
    Super Member
    • Total Posts : 2143
    • Reward points : 0
    • Joined: 2005/05/10 10:55:05
    • Location: Warks, UK
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/16 04:03:41 (permalink)
    +1 (3)
    mad_c
    Thanks for pointing that out. 

    Thank you for responding. It is nice to know someone cares :)
     
    #9
    dan1138
    Super Member
    • Total Posts : 4162
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/16 13:18:40 (permalink)
    0 (2)
    mad_c
    ... our server software rather than someone's a***s ...

    Is this server software managed by the same group that manages the forum server and firewall?
    #10
    dan1138
    Super Member
    • Total Posts : 4162
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/24 16:21:23 (permalink)
    +1 (1)
    mad_c
    dan1138
    Why is the bug description so cryptic?

    The compiler might fail if any compiler application attempts to create a temporary file using Microsoft's library routine and your Windows/environment variable temp path has a dot in there somewhere. Temp files are created often. Failing when the IDE runs the compiler to verify versions is just one case, and even I had no idea of how the IDE would react to that situation. I can request that the developers write a more comprehensive descriptions of potential failure mechanics, but there will always be occasions where such a description might be inadequate or overwhelming, particularly when what you see is the IDE's response to a compiler failure.

    @Jeff,
     
    I am not asking for deathless prose but something that an MPLABX user might have a chance at comprehending.
     
    At it is the text in the release notes uses jargon familiar only to the Microchip coders that maintain the MPLABX IDE.
     
    The last thing I would like to mention is that the TEMP or PATH environment variables of my Windows installation do not contain any dot ('.') characters, so the explanation for XC8-2367 is at best incomplete and at worst out right wrong.
    #11
    crosland
    Super Member
    • Total Posts : 2143
    • Reward points : 0
    • Joined: 2005/05/10 10:55:05
    • Location: Warks, UK
    • Status: offline
    Re: XC8 v2.30 bug with MPLABX v5.45 integration 2020/11/25 02:15:08 (permalink)
    0
    dan1138
    At it is the text in the release notes uses jargon familiar only to the Microchip coders that maintain the MPLABX IDE.

     
    I (an engineer) used to have endless debates with our tech authors about the way docs were written. I alwayslost, ans I knew that was right. It seems in Microchip that the engineers win the debates :)
    #12
    Jump to:
    © 2021 APG vNext Commercial Version 4.5