Re: [platform-dev] Build from source problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] Build from source problem
From: Andrey Loskutov <loskutov@xxxxxx>
Date: Sun, 18 Apr 2021 17:32:20 +0200
Delivered-to: platform-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/platform-dev/>
List-help: <mailto:platform-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/platform-dev>, <mailto:platform-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/platform-dev>, <mailto:platform-dev-request@eclipse.org?subject=unsubscribe>
Could be, that incremental build isn't working because of some build artifacts from previous build, I've never managed to resume build from a failure in the middle. Try git clean -fdx and full rebuild, also beware of some jar files in jdt project that are checked in and modified by the build - they must be reverted too.

Am 18. April 2021 17:12:46 MESZ schrieb Kirill Kotovich <kirillkotovich1@xxxxxxxxx>:
>Using this command (mvn -U clean verify -DskipTests=true) helped up to a point.
>Build restarts didn't help at this stage:
>
>.............................................
>[INFO] org.eclipse.rcp.configuration 1.1.1300-SNAPSHOT .... SUCCESS [  0.180 s]
>[INFO] org.eclipse.rt.osgistarterkit.product 4.20.0-SNAPSHOT SUCCESS [ 16.049 s]
>[INFO] equinox-sdk 4.20.0-SNAPSHOT ........................ SUCCESS [ 56.965 s]
>[INFO] eclipse-junit-tests 4.20.0-SNAPSHOT ................ FAILURE [01:25 min]
>[INFO] eclipse.platform.repository 4.20.0-SNAPSHOT ........ SKIPPED
>[INFO] platform-aggregator 4.20.0-SNAPSHOT ................ SKIPPED
>[INFO] ------------------------------------------------------------------------
>[INFO] BUILD FAILURE
>[INFO] ------------------------------------------------------------------------
>[INFO] Total time:  52:33 min
>[INFO] Finished at: 2021-04-18T17:21:28+03:00
>[INFO] ------------------------------------------------------------------------
>[ERROR] Failed to execute goal
>org.apache.maven.plugins:maven-assembly-plugin:3.3.0:single
>(make-assembly) on project eclipse-junit-tests: Failed to create
>assembly: Error adding file to archive:
>/home/main/eclipse.platform.releng.aggregator/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/../../eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/target/doc.bin.log
>-> [Help 1]
>[ERROR]
>[ERROR] To see the full stack trace of the errors, re-run Maven with
>the -e switch.
>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>[ERROR]
>[ERROR] For more information about the errors and possible solutions,
>please read the following articles:
>[ERROR] [Help 1]
>http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>[ERROR]
>[ERROR] After correcting the problems, you can resume the build with the command
>[ERROR]   mvn <args> -rf :eclipse-junit-tests
>main@ubuntu-pc:~/eclipse.platform.releng.aggregator$
>
>Thank you for not losing interest in my problems!
>Kirill
>
>сб, 17 апр. 2021 г. в 08:12, Sravan K Lakkimsetti <sravankumarl@xxxxxxxxxx>:
>>
>> As Jonah suggested you had network problem. Only way to fix is to rebuild. In this kind of environment please use -U option with maven. This way the artifacts will be stored in local .m2 repository for subsequent builds.
>>
>>
>>
>> Use mvn -U clean verify -DskipTests=true
>>
>>
>>
>> Xmx6G would be sufficient. If you are using a machine more ram you don’t need to set MAVAN_OPTS environment variable.
>>
>> Regarding the warning you’ll see a lot. There are different warnings. We ignote Information type warning. These are the ones you are seeing.
>>
>> Here is a sample log https://download.eclipse.org/eclipse/downloads/drops4/I20210416-1800/buildlogs/mb220_buildSdkPatch.sh.log. You should get a similar log
>>
>>
>>
>> Thanks
>>
>> Sravan
>>
>>
>>
>> From: Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
>> Sent: 17 April 2021 00:38
>> To: Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>
>> Subject: [EXTERNAL] Re: [platform-dev] Build from source problem
>>
>>
>>
>> It looks like you were a little unlucky with your network connection. The issue is
>>
>>
>>
>> : Could not transfer
>> artifact org.apache.maven.doxia:doxia-core:jar:1.0 from/to central
>> (https://repo.maven.apache.org/mn2): Transfer failed for
>> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar:
>> Connection timed out (Read failed) -> [Help 1]
>>
>>
>> [ERROR]
>> [
>>
>>
>>
>> On Fri., Apr. 16, 2021, 14:40 Kirill Kotovich, <kirillkotovich1@xxxxxxxxx> wrote:
>>
>> Built on Ubuntu 20.04 x86_64. Now a result like this:
>>
>> $ export MAVEN_OPTS="-Xmx10G"
>> $ mvn clean verify -DskipTests=true
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by
>> com.google.inject.internal.cglib.core.$ReflectUtils$1
>> (file:/usr/share/maven/lib/guice.jar) to method
>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
>> WARNING: Please consider reporting this to the maintainers of
>> com.google.inject.internal.cglib.core.$ReflectUtils$1
>> WARNING: Use --illegal-access=warn to enable warnings of further
>> illegal reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> [INFO] Scanning for projects...
>> [WARNING] No explicit target runtime environment configuration. Build
>> is platform dependent.
>> [WARNING] No explicit target runtime environment configuration. Build
>> is platform dependent.
>> [INFO] Computing target platform for MavenProject:
>> org.eclipse.jdt:org.eclipse.jdt:3.18.800-SNAPSHOT @
>> /home/main/eclipse.platform.releng.aggregator/eclipse.jdt/org.eclipse.jdt/pom.xml
>> [INFO] Fetching p2.index from
>> https://download.eclipse.org/eclipse/updates/4.20-I-builds/ (128B)
>> [INFO] Adding repository
>> https://download.eclipse.org/eclipse/updates/4.20-I-builds
>> ...................................................................
>> [INFO] org.eclipse.jdt.ui.tests.refactoring 3.13.1400-SNAPSHOT SUCCESS
>> [ 19.246 s]
>> [INFO] org.eclipse.jdt.ui.junit.sampleproject 1.0.0-SNAPSHOT SUCCESS [08:28 min]
>> [INFO] org.eclipse.jdt.ui.examples.projects 3.1.300-SNAPSHOT FAILURE [20:45 min]
>> [INFO] org.eclipse.unittest.ui 1.0.0-SNAPSHOT ............. SKIPPED
>> [INFO] org.eclipse.jdt.ui.unittest.junit 1.0.100-SNAPSHOT . SKIPPED
>> [INFO] org.eclipse.jdt.ui.unittest.junit.feature 1.0.100-SNAPSHOT SKIPPED
>> ...................................................................
>> [INFO] eclipse.platform.repository 4.20.0-SNAPSHOT ........ SKIPPED
>> [INFO] platform-aggregator 4.20.0-SNAPSHOT ................ SKIPPED
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time:  01:08 h
>> [INFO] Finished at: 2021-04-16T19:12:38+03:00
>> [INFO] ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-dependency-plugin:2.8:copy (copy) on
>> project org.eclipse.jdt.ui.exles.projects: Execution copy of goal
>> org.apache.maven.plugins:maven-dependency-plugin:2.8:copy failed:
>> Plugin org.apache.maven.pins:maven-dependency-plugin:2.8 or one of its
>> dependencies could not be resolved: The following artifacts could not
>> be resolved:g.apache.maven.doxia:doxia-core:jar:1.0,
>> org.apache.maven.shared:maven-doxia-tools:jar:1.0.2,
>> commons-validator:commons-validatoar:1.2.0: Could not transfer
>> artifact org.apache.maven.doxia:doxia-core:jar:1.0 from/to central
>> (https://repo.maven.apache.org/mn2): Transfer failed for
>> https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar:
>> Connection timed out (Read failed) -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the command
>> [ERROR]   mvn <args> -rf :org.eclipse.jdt.ui.examples.projects
>>
>> There are also a large number of warnings in the logs, for example:
>> ...................................................................
>> [INFO] --- tycho-compiler-plugin:2.3.0:compile (default-compile) @
>> org.eclipse.ui.workbench ---
>> [INFO] Compiling 1199 source files to
>> /home/main/eclipse.platform.releng.aggregator/eclipse.platform.ui/bundles/org.eclipse.ui.workbench/target/classes
>> [WARNING] /home/main/eclipse.platform.releng.aggregator/eclipse.platform.ui/bundles/org.eclipse.ui.workbench/Eclipse
>> UI/org/eclipse/ui/internal/WorkbenchPage.java:[885]
>>         if (!(minimizedStack.getObject() instanceof
>> org.eclipse.e4.ui.workbench.addons.minmax.TrimStack))
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Discouraged access: The type 'TrimStack' is not API (restriction on
>> classpath entry
>> '/home/main/eclipse.platform.releng.aggregator/eclipse.platform.ui/bundles/org.eclipse.e4.ui.workbench.addons.swt/target/classes')
>> ...................................................................
>>
>> Kirill
>>
>> пт, 16 апр. 2021 г. в 18:08, Wim Jongman <wim.jongman@xxxxxxxxx>:
>> >
>> > Also, don't compile with sudo, that will cause the build artifacts to be created for root and you might not be able to access them later on.
>> >
>> > On Fri, Apr 16, 2021 at 7:47 AM Sravan K Lakkimsetti <sravankumarl@xxxxxxxxxx> wrote:
>> >>
>> >> Here you are seeing compilation failure in SWT.
>> >> In SWT we have org.eclipse.swt as plugin and org.eclipse.swt.<platform> as fragment. In this case I am suspecting fragment is not getting loaded during the compilation of org.eclipse.swt.tests. if you have a x86_64 machine, can you please try building on that machine? This is most likely problem with e2k architecture. SWT does not have a plugin fragment supporting e2k architecture. This might be the problem
>> >>
>> >> -Sravan
>> >>
>> >> -----Original Message-----
>> >> From: Kirill Kotovich <kirillkotovich1@xxxxxxxxx>
>> >> Sent: 16 April 2021 02:15
>> >> To: Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>
>> >> Subject: [EXTERNAL] Re: [platform-dev] Build from source problem
>> >>
>> >> export MAVEN_OPTS=-Xmx6G Didn't help (unless, of course, the lack of quotes doesn't affect the build)
>> >>
>> >> Part of the output:
>> >>
>> >> $ export MAVEN_OPTS=-Xmx6G
>> >> $ mvn clean verify -DskipTests=true
>> >>
>> >> ..........................................
>> >> [INFO] ------------------------------------------------------------------------
>> >> [INFO] Reactor Summary:
>> >> [INFO]
>> >> [INFO] eclipse-platform-parent 4.20.0-SNAPSHOT ............ SUCCESS [ 2.530 s] [INFO] eclipse-sdk-prereqs 4.20.0-SNAPSHOT ................ SUCCESS [ 2.188 s] ..........................................
>> >> ..........................................
>> >> [INFO] org.eclipse.swt.examples.ole.win32 3.107.400-SNAPSHOT SUCCESS [ 3.635 s] [INFO] org.eclipse.swt.examples.views 3.107.0-SNAPSHOT .... SUCCESS [ 3.021 s] [INFO] org.eclipse.swt.tests.fragments.feature 3.106.0-SNAPSHOT SUCCESS [ 0.499 s] [INFO] org.eclipse.swt.tests 3.106.1300-SNAPSHOT .......... FAILURE [ 12.265 s] [INFO] org.eclipse.swt.tools.feature 3.108.100-SNAPSHOT ... SKIPPED [INFO] org.eclipse.swt.tests.gtk 3.107.200-SNAPSHOT ....... SKIPPED [INFO] eclipse.platform.swt.binaries 4.20.0-SNAPSHOT ...... SKIPPED ..........................................
>> >> ..........................................
>> >> [INFO] eclipse.platform.repository 4.20.0-SNAPSHOT ........ SKIPPED [INFO] platform-aggregator 4.20.0-SNAPSHOT ................ SKIPPED [INFO] ------------------------------------------------------------------------
>> >> [INFO] BUILD FAILURE
>> >> [INFO] ------------------------------------------------------------------------
>> >> [INFO] Total time: 03:05 h
>> >> [INFO] Finished at: 2021-04-15T23:51:11+03:00 [INFO] ------------------------------------------------------------------------
>> >> [ERROR] Failed to execute goal
>> >> org.eclipse.tycho:tycho-compiler-plugin:2.3.0:compile
>> >> (default-compile) on project org.eclipse.swt.tests: Compilation
>> >> failure: Compilation failure:
>> >> [ERROR] /home/main/eclipse.platform.releng.aggregator/eclipse.platform.swt/tests/org.eclipse.swt.tests/JUnit
>> >> Tests/org/eclipse/swt/tests/junit/Test_org_eclipse_swt_custom_BidiSegmentListener.java:[22]
>> >> [ERROR] import org.eclipse.swt.SWT;
>> >> [ERROR] ^^^^^^^^^^^^^^^^^^^
>> >> [ERROR] The import org.eclipse.swt.SWT cannot be resolved [ERROR] /home/main/eclipse.platform.releng.aggregator/eclipse.platform.swt/tests/org.eclipse.swt.tests/JUnit
>> >> Tests/org/eclipse/swt/tests/junit/Test_org_eclipse_swt_custom_BidiSegmentListener.java:[23]
>> >> [ERROR] import org.eclipse.swt.custom.BidiSegmentListener;
>> >> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
>> >> [ERROR] The import org.eclipse.swt.custom cannot be resolved [ERROR] /home/main/eclipse.platform.releng.aggregator/eclipse.platform.swt/tests/org.eclipse.swt.tests/JUnit
>> >> Tests/org/eclipse/swt/tests/junit/Test_org_eclipse_swt_custom_BidiSegmentListener.java:[24]
>> >> [ERROR] import org.eclipse.swt.custom.StyleRange;
>> >> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
>> >> [ERROR] The import org.eclipse.swt.custom cannot be resolved ..........................................
>> >>
>> >> Kirill
>> >>
>> >> чт, 15 апр. 2021 г. в 15:50, Sravan K Lakkimsetti <sravankumarl@xxxxxxxxxx>:
>> >> >
>> >> > I see one definite problem. MAVEN_OPTS=-Xmx2048m Is definitely not sufficient. To build eclipse you’ll need 6GB.
>> >> >
>> >> >
>> >> >
>> >> > Log is indicating problem with GC. In our regular builds we use export MAVEN_OPTS="-Xmx6G". use higher Xmx value and try to build again.
>> >> >
>> >> >
>> >> >
>> >> > Thanks
>> >> >
>> >> > Sravan
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > From: Kirill Kotovich <kirillkotovich1@xxxxxxxxx>
>> >> > Sent: 15 April 2021 17:58
>> >> > To: Eclipse platform general developers list.
>> >> > <platform-dev@xxxxxxxxxxx>
>> >> > Subject: [EXTERNAL] Re: [platform-dev] Build from source problem
>> >> >
>> >> >
>> >> >
>> >> > Hello!
>> >> > I apologize for the long answer, I did not notice that the moderators
>> >> > tipped off my previous letter
>> >> >
>> >> > The sequence of commands literally looked like this:
>> >> >
>> >> > $ cd eclipse.platform.releng.aggregator
>> >> > /eclipse.platform.releng.aggregator$ export MAVEN_OPTS=-Xmx2048m
>> >> > /eclipse.platform.releng.aggregator$ git pull --recurse-submodules
>> >> > /eclipse.platform.releng.aggregator$ git submodule update
>> >> > /eclipse.platform.releng.aggregator$ mvn -X clean validate >
>> >> > ./logs.txt
>> >> >
>> >> > Before that, I tried to immediately build using the command "mvn clean verify",as it was written in the Wiki:
>> >> > https://wiki.eclipse.org/Platform-releng/Platform_Build. This response was received:
>> >> >
>> >> > ..................
>> >> > [INFO] eclipse.platform.releng 4.20.0-SNAPSHOT ............ SUCCESS [
>> >> > 0.079 s] [INFO] org.eclipse.test.performance 3.17.100-SNAPSHOT .....
>> >> > SUCCESS [ 39.951 s] [INFO] [bundle] Eclipse IDE UI Application
>> >> > 1.4.0-SNAPSHOT . SUCCESS [ 29.902 s] [INFO]
>> >> > org.eclipse.jdt.core.tests.compiler 3.12.1600-SNAPSHOT FAILURE [
>> >> > 01:46 h] [INFO] org.eclipse.jdt.compiler.tool.tests 1.2.900-SNAPSHOT
>> >> > SKIPPED [INFO] org.eclipse.jdt.core.tests.builder 3.10.1200-SNAPSHOT
>> >> > SKIPPED [INFO] org.eclipse.jdt.compiler.apt.tests 1.1.1500-SNAPSHOT
>> >> > SKIPPED ..................
>> >> > [INFO] platform-aggregator 4.20.0-SNAPSHOT ................ SKIPPED
>> >> > [INFO]
>> >> > ----------------------------------------------------------------------
>> >> > --
>> >> > [INFO] BUILD FAILURE
>> >> > [INFO]
>> >> > ----------------------------------------------------------------------
>> >> > --
>> >> > [INFO] Total time: 04:06 h
>> >> > [INFO] Finished at: 2021-04-02T19:58:44+03:00 [INFO]
>> >> > ----------------------------------------------------------------------
>> >> > --
>> >> > [ERROR] Failed to execute goal
>> >> > org.eclipse.tycho:tycho-surefire-plugin:2.3.0:test (default-test) on
>> >> > project org.eclipse.jdt.core.tests.compiler: There are test failures.
>> >> > [ERROR]
>> >> > [ERROR] Please refer to
>> >> > /home/main/eclipse.platform.releng.aggregator/eclipse.jdt.core/org.ecl
>> >> > ipse.jdt.core.tests.compiler/target/surefire-reports
>> >> > for the individual test results.
>> >> > [ERROR] -> [Help 1]
>> >> > [ERROR]
>> >> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> >> > the -e switch.
>> >> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> >> > [ERROR]
>> >> > [ERROR] For more information about the errors and possible solutions,
>> >> > please read the following articles:
>> >> > [ERROR] [Help 1]
>> >> > INVALID URI REMOVED
>> >> > onfluence_display_MAVEN_MojoFailureException&d=DwIGaQ&c=jf_iaSHvJObTbx
>> >> > -siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=Um4kJ_WXU3SV5
>> >> > LyokQ6EYDEtWPLlMUkNvQsnOf5P1wU&s=CcDecOcpTOCbg2SoN1N4yGD9e3R42-FHWSIyt
>> >> > RR2tGo&e=
>> >> > [ERROR]
>> >> > [ERROR] After correcting the problems, you can resume the build with the command
>> >> > [ERROR] mvn <args> -rf :org.eclipse.jdt.core.tests.compiler
>> >> >
>> >> > I also tried the command "sudo mvn clean verify -DskipTests=true", and the answer was:
>> >> >
>> >> > # A fatal error has been detected by the Java Runtime Environment:
>> >> > #
>> >> > # SIGSEGV (0xb) at pc=0x000045ebd8a0b1d0, pid=12418, tid=12456 # #
>> >> > JRE version: OpenJDK Runtime Environment (11.0.8) (build
>> >> > 11.0.8-internal+0-adhoc.root.openjdk11-11.0.8)
>> >> > # Java VM: OpenJDK 64-Bit Server VM (RVM 4.1.0)
>> >> > (11.0.8-internal+0-adhoc.root.openjdk11-11.0.8, mixed mode, g1 gc,
>> >> > linux-e2k)
>> >> > #
>> >> > # Problematic frame:
>> >> > # V [libjvm.so+0x7261d0] oopDesc::size()+0xf0 # # No core dump will
>> >> > be written. Core dumps have been disabled. To enable core dumping, try
>> >> > "ulimit -c unlimited" before starting Java again # # An error report
>> >> > file with more information is saved as:
>> >> > # /home/main/ecipse_platform/hs_err_pid12418.log
>> >> > Compiled method (c2) 11292643 13916 !
>> >> > java.util.concurrent.ThreadPoolExecutor::runWorker (187 bytes) total
>> >> > in heap [0x000045ebeb4fb690,0x000045ebeb504b38] = 38056
>> >> > relocation [0x000045ebeb4fb7f8,0x000045ebeb4fc590] = 3480
>> >> > main code [0x000045ebeb4fc5a0,0x000045ebeb503520] = 28544
>> >> > stub code [0x000045ebeb503520,0x000045ebeb503640] = 288
>> >> > oops [0x000045ebeb503640,0x000045ebeb503670] = 48
>> >> > metadata [0x000045ebeb503670,0x000045ebeb503938] = 712
>> >> > scopes data [0x000045ebeb503938,0x000045ebeb5040b0] = 1912
>> >> > scopes pcs [0x000045ebeb5040b0,0x000045ebeb5046b0] = 1536
>> >> > dependencies [0x000045ebeb5046b0,0x000045ebeb5046d0] = 32
>> >> > handler table [0x000045ebeb5046d0,0x000045ebeb504a18] = 840 nul chk
>> >> > table [0x000045ebeb504a18,0x000045ebeb504b38] = 288 # # If you would
>> >> > like to submit a bug report, please visit:
>> >> > # https://bugreport.java.com/bugreport/crash.jsp
>> >> > #
>> >> > Aborted
>> >> >
>> >> > I am attaching the logs of the mentioned assembly attempts,because of
>> >> > them my letter was not published
>> >> >
>> >> > Thank you!
>> >> >
>> >> > Kirill
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > platform-dev mailing list
>> >> > platform-dev@xxxxxxxxxxx
>> >> > To unsubscribe from this list, visit
>> >> > https://www.eclipse.org/mailman/listinfo/platform-dev
>> >> _______________________________________________
>> >> platform-dev mailing list
>> >> platform-dev@xxxxxxxxxxx
>> >> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
>> >>
>> >>
>> >> _______________________________________________
>> >> platform-dev mailing list
>> >> platform-dev@xxxxxxxxxxx
>> >> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
>> >
>> > _______________________________________________
>> > platform-dev mailing list
>> > platform-dev@xxxxxxxxxxx
>> > To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
>> _______________________________________________
>> platform-dev mailing list
>> platform-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
>>
>>
>> _______________________________________________
>> platform-dev mailing list
>> platform-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
>_______________________________________________
>platform-dev mailing list
>platform-dev@xxxxxxxxxxx
>To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

--
Kind regards,
Andrey Loskutov

https://www.eclipse.org/user/aloskutov
Спасение утопающих - дело рук самих утопающих
References:
- Re: [platform-dev] Build from source problem
  - From: Jonah Graham
- Re: [platform-dev] Build from source problem
  - From: Sravan K Lakkimsetti
- Re: [platform-dev] Build from source problem
  - From: Kirill Kotovich
Prev by Date: Re: [platform-dev] Build from source problem
Next by Date: Re: [platform-dev] Extensibility of the application model
Previous by thread: Re: [platform-dev] Build from source problem
Next by thread: Re: [platform-dev] Build from source problem
Index(es):
- Date
- Thread
Breadcrumbs
