Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Unable to build CDT from latest source

I did upgrade, and I did issue a git clean -f.  Perhaps the lack of '-d' was the problem, I'll try again when I'm near that machine.

On Mon, Aug 29, 2016 at 2:33 AM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Hi Avi,

Thanks for the extra information. Have you recently updated from an
older CDT to current?

The problem here is that the configuration for the Eclipse application
used to run ANT is corrupt. The configuration is generated by the
build and is located here:
/home/avi/eclipse-cdt/doc/org.eclipse.cdt.doc.user/target/eclipserun-work/configuration

If you have not already done a complete clean build (e.g do "git clean
-df --force" in root of cdt)  I would recommend that as it will reset
the configuration and tycho/maven should rebuild it correctly.

If you have already done such a complete clean, I am less sure how to
help. You have hit a problem that others have hit in that a bad OSGi
configuration gives you a meaningless NPE instead of a full error
message. See http://eclip.se/443761 and http://eclip.se/461781 for
example of other people that have hit that bug.

Of course none of this resolves how Tycho created a bad version in the
first place.

HTH,
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 27 August 2016 at 09:06, Avi Kivity <avi@xxxxxxxxxxxx> wrote:
> My repo is in https://github.com/avikivity/cdt (two patches on top of
> master); master itself also fails in the same way, so my patches are not
> responsible.
>
> Running the command line with -debug got me this output:
>
> $ /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.101-1.b14.fc24.x86_64/jre/bin/java
> -jar
> /home/avi/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.100.v20150511-1540/org.eclipse.equinox.launcher-1.3.100.v20150511-1540.jar
> -debug  -install
> /home/avi/eclipse-cdt/doc/org.eclipse.cdt.doc.user/target/eclipserun-work
> -configuration
> /home/avi/eclipse-cdt/doc/org.eclipse.cdt.doc.user/target/eclipserun-work/configuration
> -application org.eclipse.ant.core.antRunner -buildfile,
> customBuildCallbacks.xml build.index
> Configuration location:
>
> file:/home/avi/eclipse-cdt/doc/org.eclipse.cdt.doc.user/target/eclipserun-work/configuration/
> Configuration file:
>
> file:/home/avi/eclipse-cdt/doc/org.eclipse.cdt.doc.user/target/eclipserun-work/configuration/config.ini
> loaded
> Install location:
>
> file:/home/avi/eclipse-cdt/doc/org.eclipse.cdt.doc.user/target/eclipserun-work/
> Framework located:
>
> file:/home/avi/.m2/repository/p2/osgi/bundle/org.eclipse.osgi/3.10.102.v20160118-1700/org.eclipse.osgi-3.10.102.v20160118-1700.jar
> Framework classpath:
>
> file:/home/avi/.m2/repository/p2/osgi/bundle/org.eclipse.osgi/3.10.102.v20160118-1700/org.eclipse.osgi-3.10.102.v20160118-1700.jar
> Debug options:
>     file:/home/avi/eclipse-cdt/.options not found
> Time to load bundles: 11
> Starting application: 571
> An error has occurred. See the log file
> /home/avi/eclipse-cdt/doc/org.eclipse.cdt.doc.user/target/eclipserun-work/configuration/1472285043336.log.
>
>
> The log file says:
>
> !SESSION 2016-08-27 11:04:03.211
> -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_101
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -application org.eclipse.ant.core.antRunner
> -buildfile, customBuildCallbacks.xml build.index
> Command-line arguments:  -debug -application org.eclipse.ant.core.antRunner
> -buildfile, customBuildCallbacks.xml build.index
>
> !ENTRY org.eclipse.osgi 4 0 2016-08-27 11:04:03.798
> !MESSAGE Application error
> !STACK 1
> java.lang.NullPointerException: null values not allowed
> at
> org.eclipse.core.internal.registry.ReferenceMap.put(ReferenceMap.java:351)
> at
> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.getBundle(RegistryStrategyOSGI.java:151)
> at
> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:166)
> at
> org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at
> org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at
> org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
>
>
>
> On Mon, Aug 22, 2016 at 4:49 PM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
> wrote:
>>
>> Have you removed any plug-ins from the source tree? The build is
>> failing on the legacy call from Maven back to Ant to build
>> documentation. If you want to debug the problem, it may help to try
>> and run the problematic ant parts manually with the -debug flag.
>>
>> My offer is still open if it helps.
>>
>> Jonah
>> ~~~
>> Jonah Graham
>> Kichwa Coders Ltd.
>> www.kichwacoders.com
>>
>>
>> On 22 August 2016 at 14:19, Avi Kivity <avi@xxxxxxxxxxxx> wrote:
>> > After commenting out all the doc packages, the build passed (it was
>> > before I
>> > read about -skipDoc).
>> >
>> >
>> > Nevertheless it would be good to understand why the doc build failed and
>> > fix
>> > it.  I'm happy to help to debug this, though I know nothing about maven
>> > and
>> > eclipse-cdt (other than being a happy user).
>> >
>> >
>> > On 08/22/2016 04:06 PM, Marc-André Laperle wrote:
>> >
>> > I think it's -DskipDoc
>> >
>> > Marc-Andre
>> > ________________________________
>> > From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on
>> > behalf of
>> > Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
>> > Sent: Saturday, 20 August 2016 1:20 PM
>> > To: CDT General developers list.
>> > Subject: Re: [cdt-dev] Unable to build CDT from latest source
>> >
>> > There is a CDT build flag to skip building the docs.  Add the following
>> > to
>> > your maven command:
>> >
>> > -skipDoc
>> >
>> > or
>> >
>> > -skipDoc=true
>> >
>> > I'm not sure which at this time
>> >
>> > Marc
>> >
>> > ________________________________
>> > From: Avi Kivity <avi@xxxxxxxxxxxx>
>> > Sent: Aug 20, 2016 10:24
>> > To: CDT General developers list.
>> > Subject: Re: [cdt-dev] Unable to build CDT from latest source
>> >
>> >
>> >
>> > On Sat, Aug 20, 2016 at 3:22 PM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
>> > wrote:
>> >>
>> >> Hi Avi,
>> >>
>> >> I don't know the answer to your question, but in case you didn't know
>> >> you may find the last build output log from CDT's master here:
>> >> https://hudson.eclipse.org/cdt/job/cdt-master/. The most recent code
>> >> did build ok there, perhaps you could identify the difference between
>> >> your setup and CDT's build machine?
>> >
>> >
>> > I don't know how to do that.
>> >
>> >>
>> >>
>> >> Alternatively, if you don't need the user docs to be built, you could
>> >> use a workaround to exclude the problematic build portion by removing
>> >> org.eclipse.cdt.doc.user from the root pom.xml
>> >> (https://git.eclipse.org/c/cdt/org.eclipse.cdt.git/tree/pom.xml#n77).
>> >>
>> >
>> >
>> > It proceeded a little further, then hit
>> >
>> > [ERROR] Failed to execute goal
>> > org.eclipse.tycho.extras:tycho-eclipserun-plugin:0.25.0:eclipse-run
>> > (default) on project org.eclipse.cdt.debug.application.doc: Error while
>> > executing platform: Error while executing platform (return code: 13) ->
>> > [Help 1]
>> >
>> > again a .doc package.  I can try to remove it as well.
>> >
>> >
>> >
>> >>
>> >> Hopefully someone else on the list will have a more complete answer.
>> >>
>> >> HTH
>> >> Jonah
>> >> ~~~
>> >> Jonah Graham
>> >> Kichwa Coders Ltd.
>> >> www.kichwacoders.com
>> >>
>> >>
>> >> On 20 August 2016 at 12:44, Avi Kivity <avi@xxxxxxxxxxxx> wrote:
>> >> > Hello, heroic CDT developers,
>> >> >
>> >> > I regularly build CDT from source (since I need a patch, not good
>> >> > enough
>> >> > for
>> >> > upstream, for C++14 lambdas).  I just hit an error with git master:
>> >> >
>> >> > [ERROR] Failed to execute goal
>> >> > org.eclipse.tycho.extras:tycho-eclipserun-plugin:0.25.0:eclipse-run
>> >> > (default) on project org.eclipse.cdt.doc.user: Error while executing
>> >> > platform: Error while executing platform (return code: 13) -> [Help
>> >> > 1]
>> >> >
>> >> > Here is the log:
>> >> >
>> >> > !SESSION 2016-08-20 14:22:26.415
>> >> > -----------------------------------------------
>> >> > eclipse.buildId=unknown
>> >> > java.version=1.8.0_101
>> >> > java.vendor=Oracle Corporation
>> >> > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
>> >> > Framework arguments:  -application org.eclipse.ant.core.antRunner
>> >> > -buildfile
>> >> > customBuildCallbacks.xml build.index
>> >> > Command-line arguments:  -application org.eclipse.ant.core.antRunner
>> >> > -buildfile customBuildCallbacks.xml build.index
>> >> >
>> >> > !ENTRY org.eclipse.osgi 4 0 2016-08-20 14:22:27.129
>> >> > !MESSAGE Application error
>> >> > !STACK 1
>> >> > java.lang.NullPointerException: null values not allowed
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.internal.registry.ReferenceMap.put(ReferenceMap.java:351)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.getBundle(RegistryStrategyOSGI.java:151)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:166)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
>> >> > at
>> >> >
>> >> >
>> >> > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
>> >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> > at
>> >> >
>> >> >
>> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> >> > at
>> >> >
>> >> >
>> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >> > at java.lang.reflect.Method.invoke(Method.java:498)
>> >> > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
>> >> > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
>> >> > at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
>> >> > at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
>> >> >
>> >> >
>> >> > Help is appreciated.
>> >> >
>> >> > _______________________________________________
>> >> > cdt-dev mailing list
>> >> > cdt-dev@xxxxxxxxxxx
>> >> > To change your delivery options, retrieve your password, or
>> >> > unsubscribe
>> >> > from
>> >> > this list, visit
>> >> > https://dev.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://dev.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://dev.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://dev.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://dev.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://dev.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://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top