| I guess as per this bug report, it only
      affects GCC 9.1.0: 
 
      That seems to be what's causing my
        problem, shame I only found it after creating my own fix
        separately... 
 I guess you're using an earlier version
      of GCC? Thanks for looking into this, I do appreciate it. 
 Davin
 
 On 23/6/19 11:18 pm, Mark B wrote:
 
      
      yes, I opened the file with SIGHUP symbol 
 
        
        
          
            _______________________________________________Hmm. 
 The
              errors only become visible when you open a file in the
              editor - i.e. src/load-service.cc displays errors on lines
              28-33 (under each of the SIGxxx definitions). Did you open
              any files?
 
 
 On
              23/6/19 8:47 pm, marco wrote:
 I'm not able to reproduce this
              problem. I cloned your repository and imported it as
              makefile project. I can't see any kind of error. The
              project has been correctly indexed. 
 Il 23/06/19 11:17, Davin McCall ha scritto:
 
 The latest commit that I know
                works is 2734b7ae8295dd4dde0d4383b2bcf7dc708a072a. _______________________________________________
 However, I'm now unable to re-build even at that commit,
                due to the error I posted earlier (or at least a similar
                one):
 
 [ERROR] Failed to resolve target definition
 /home/davmac/eclipse-cdt/ws/cdt-git/releng/org.eclipse.cdt.target/cdt.target:
 Failed to load p2 metadata repository from location
 http://download.eclipse.org/eclipse/updates/4.12-I-builds/I20190510-1800/:
 Artifact not found:
 http://download.eclipse.org/eclipse/updates/4.12-I-builds/I20190510-1800/content.xml.xz.
 -> [Help 1]
 
 Being unable to build an archive, I'm not able to test
                changes from that point on, unless there is another way
                to use the plugin without building via maven?
 
 
 On 23/6/19 3:52 pm, Mark B wrote:
 
 can you provide the latest
                  working commit for you? 
 Il dom 23 giu 2019, 06:46 Davin McCall <davmac@xxxxxxxxxx
                  <mailto:davmac@xxxxxxxxxx>>
                  ha scritto:
 
 I should add: this is a makefile-based project,
                  and if anyone
 wants to try it for themselves it can be found at
 https://github.com/davmac314/dinit.
                  Building is quite
 straightforward and it shouldn't require any
                  special configuration
 in Eclipse.
 
 Davin
 
 On 23/6/19 2:39 pm, Davin McCall wrote:
 
  Hi all,
 
 I'm a user and occasional contributor to Eclipse
                    CDT. I want to
 ask for help in tracking down the cause of a
                    problem that is
 biting me after updating.
 
 I've just updated to Eclipse 2019-06 and with it
                    CDT 9.8.0 (after
 using 2019-03 with 9.7.2). With that update, one
                    of my projects
 is suddenly showing a lot of "Symbol 'name'
                    could not be
 resolved" for no clear reason and with no
                    apparent solution; I've
 tried the usual tricks such as re-building the
                    index.
 
 From a little investigation, it appears that the
                    errors are shown
 if the symbol is defined in a header file that
                    is included only
 indirectly. If the symbol is defined in a header
                    that is included
 directly from the source file where the symbol
                    is referenced,
 everything's ok.
 
 For example I have a line of code:
 
 if (signame == "HUP") return SIGHUP;
 
 The "SIGHUP" is underlined and reported as
                    symbol-not-resolved.
 However, the appropriate header file (csignal)
                    is *indirectly*
 included. If I add "#include <csignal>" to
                    the top of the source
 file containing the line of code above, the
                    problem does go away.
 Note that even when the "Symbol could not be
                    resolved" error is
 displayed, going to the declaration works just
                    fine.
 
 Going back to a pre-CDT 9.8.0 build (which I had
                    built myself
 previously) in Eclipse 2019-06, the problem goes
                    away.
 
 I wanted to bi-sect this issue to see if I can
                    identify when it
 began. However, it seems I'm unable to build the
                    tagged CDT 9.8.0
 (using maven):
 
 [INFO] Fetching p2.index from
 http://download.eclipse.org/cbi/updates/license/2.0.1.v20180423-1114/
 [INFO] Adding repository
 http://download.eclipse.org/eclipse/updates/4.12milestones/S-4.12RC1a-201905310245
 [ERROR] Failed to resolve target definition
 /home/davmac/eclipse-cdt/ws/cdt-git/releng/org.eclipse.cdt.target/cdt.target:
 Failed to load p2 metadata repository from
                    location
 http://download.eclipse.org/eclipse/updates/4.12milestones/S-4.12RC1a-201905310245/:
 No repository found at
 http://download.eclipse.org/eclipse/updates/4.12milestones/S-4.12RC1a-201905310245.
 -> [Help 1]
 
 So, does anyone have any clues about the problem
                    itself, and
 secondly can anyone help with building non-HEAD
                    using maven?
 
 Thanks,
 
 Davin
 
 
 
 _______________________________________________
 cdt-dev mailing list
 cdt-dev@xxxxxxxxxxx 
                    <mailto:cdt-dev@xxxxxxxxxxx>
 To change your delivery options, retrieve your
                    password, or unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/cdt-dev
 
 
 _______________________________________________
 cdt-dev mailing list
 cdt-dev@xxxxxxxxxxx
                  <mailto:cdt-dev@xxxxxxxxxxx>
 To change your delivery options, retrieve your
                  password, or
 unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/cdt-dev
 
 
 _______________________________________________
 cdt-dev mailing list
 cdt-dev@xxxxxxxxxxx
 To change your delivery options, retrieve your
                  password, or unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/cdt-dev
 
 
 
 _______________________________________________
 cdt-dev mailing list
 cdt-dev@xxxxxxxxxxx
 To change your delivery options, retrieve your password,
                or unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/cdt-dev
 
 
 cdt-dev mailing list
 cdt-dev@xxxxxxxxxxx
 To change your delivery options, retrieve your password,
              or unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/cdt-dev
 
 
 cdt-dev mailing list
 cdt-dev@xxxxxxxxxxx
 To change your delivery options, retrieve your password, or
          unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/cdt-dev
 
 _______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev 
 |