Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ice-users] [EXTERNAL] Developing MOOSE with ICE
Hi Jay,

Thank you for examining the logs. The relevant system details are:

1) OS:
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

Also, the OS is the 64-bit version.

2) Java version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

3) ICE version
Same as earlier, i.e. the 10th July build.
Version: next
Build id: 20160710

Hope this helps. Thank you.

On Wed, Jul 13, 2016 at 5:23 PM, Billings, Jay Jay <billingsjj@xxxxxxxx> wrote:

Ram,


Thanks for sending that! It looks like the actual bug is in CDT, which is part of the platform along with ICE. Can you share some details about your system and we will file a bug report with the CDT team? What OS are you running, its version, etc.?


If you can get it working from the command line, then I guess that is a "good enough" work around for now. Alternatively, you can go to "Window->Show View->Terminal" to get a shell inside the workbench if you don't want to hit alt+tab all the time.


Jay


Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
From: ice-users-bounces@xxxxxxxxxxx <ice-users-bounces@xxxxxxxxxxx> on behalf of K. N. Ramachandran <knram06@xxxxxxxxx>
Sent: Wednesday, July 13, 2016 5:08 PM
To: Ice user discussions
Subject: Re: [ice-users] [EXTERNAL] Developing MOOSE with ICE
 
Hello Jay,

Please find attached my log file in this mail here.

If I click "OK", I am still not able to edit the toolchain. I was able to work around this, by just calling 'make all' from the terminal instead of the ICE GUI and I am able to build the 'animal' project.

I checked the Tool Chain Editor error on a colleague's machine and I was able to reproduce the same NullPointer Exception. I also ensured that the settings from a Java 7 installation was not interfering, i.e. the Java_Home was pointing to the Java 8 installation if that matters.

Hope this helps. Please let me know if you need any other information.




On Wed, Jul 13, 2016 at 3:31 PM, Jay Jay Billings <jayjaybillings@xxxxxxxxx> wrote:
K.N.,

This is a very interesting issue that we unfortunately can't produce here. I think there might be a workaround though. 

First, can you look in your workspace and send us your .log file? There must be a more detailed error in there since it says check the log.

Second, if you just click "OK" on the error, can you edit the tool chain? There are two workarounds that come to my mind. If you can click "OK" and just get the error box to go away, can you uncheck the box that says "Display Compatible Tools Chains Only?" If so, then you should be able to select Linux GCC from the list. Another alternative is to update the configuration itself by clicking "Manage Configurations" in the top right and then "importing" the build configuration from your LibMesh project, which should be Linux GCC as you said.

Let us know if any of that work. Of course, if the error dialog blocks you from doing anything, then it will be back to the drawing board.

Jay

On Wed, Jul 13, 2016 at 2:02 PM, K. N. Ramachandran <knram06@xxxxxxxxx> wrote:
Hi Alex,

I have retried the same steps and I still facing the same issue, i.e. I am not able to change the Tool Chain from within the GUI. Please find attached the following screenshots:

1) eclipse_ice_error_07_13: Screenshot of the same error.
2) version_info: ICE Version 20160710 (so it doesn't seem to be the 12th July build, although I guess that doesn't matter)

Additionally, I noticed the following in the earlier build and I encountered it in the latest also. I don't know if this is a valid issue.

1) Since the 'make all' for the Moose app doesn't work through the GUI, i.e. the console prints "Nothing to be done for animal", I execute "make all" from the terminal instead. This produces:

Makefile:19: ~/ICE/workspace/moose/framework/build.mk: No such file or directory
Makefile:20: ~/ICE/workspace/moose/framework/moose.mk: No such file or directory
Makefile:24: ~/ICE/workspace/moose/modules/modules.mk: No such file or directory
make: ~/ICE/workspace/moose/framework/scripts/find_dep_apps.py: Command not found
Makefile:32: ~/ICE/workspace/moose/framework/app.mk: No such file or directory
make: *** No rule to make target `/home/ram/ICE/workspace/moose/framework/app.mk'.  Stop.

It looks like the Makefile expects the moose/ folder to be under workspace/ which is fine. I created a softlink to my original moose folder and then the 'make all' command works, with my default Linux GCC toolchain and doesn't ask for LLVM-GCC.

Hope this helps in narrowing down the issue.


On Wed, Jul 13, 2016 at 9:32 AM, K. N. Ramachandran <knram06@xxxxxxxxx> wrote:
Hi Alex,

I have got the build files now and will install them. I will revert if I face an issue on this again.

On Wed, Jul 13, 2016 at 9:15 AM, McCaskey, Alex <mccaskeyaj@xxxxxxxx> wrote:
Good catch. That is because our nightly build did not complete successfully last night due to some application signing issues with the build server. Check it again, I’ve updated the latest binaries at that link to be the ones from 07-12-2016.

Alex

On Jul 13, 2016, at 9:10 AM, K. N. Ramachandran <knram06@xxxxxxxxx> wrote:

Hi Alex,

I went to the link that was included to download the latest binary. If I go to


all of the folders under that directory gives me a "404 Not found" error. Please advise. I can retry my steps with a more up to date build.

On Tue, Jul 12, 2016 at 4:48 PM, McCaskey, Alex <mccaskeyaj@xxxxxxxx> wrote:
Would you mind trying out a more recent version of ICE and letting us know if you still experience this issue?


Alex

On Jul 11, 2016, at 5:42 PM, K. N. Ramachandran <knram06@xxxxxxxxx> wrote:

Hi Alex,

Thank you for your detailed reply. I was able to resolve the first issue by updating the Paths and Symbols.

I am having trouble with the second problem. When I click on the Tool Chain Editor, I get an error, which I have attached as an image in this mail (eclipse_ice_error.png.

My Eclipse ICE build details are:

---------------------------------------------------------------
ICE - Integrated Computational Environment

Version: master
Build id: 20160419
---------------------------------------------------------------

At this point, I am not able to select a different toolchain and I am stuck here. Please advise on how best to resolve this.

Thank You.

On Mon, Jul 11, 2016 at 3:00 PM, McCaskey, Alex <mccaskeyaj@xxxxxxxx> wrote:
Sorry for the delay, I just returned from vacation. 

The first problem you reference is due to the fact that the current implementation of Fork the Stork action looks for moose in the current ICE workspace / Project Explorer. You can change this by right-clicking testMoose and selecting Properties > C/C++ General > Paths and Symbols and changing the Include Directories to wherever your moose repository is located. This is of course pretty repetitive and takes time, since there is no make install for MOOSE and you have to instead point to all the include directories individually. To get around this, you could just use our Developer > Frameworks > MOOSE > Clone MOOSE action. This will pull down moose and configure your CDT Indexer to appropriately index the header files. That should get rid of your unresolved inclusion problems. 

I think the second/third problem is more related to the Eclipse C++ tooling. The LLVM toolchain isn’t necessary if you are using GCC. It just means that your current CDT toolchain is set as that, and you need to change it to the GCC one. You could right click on testMoose and select Properties > C/C++ Build > Tool Chain Editor and see if you could change to the current toolchain to Linux GCC. Let me know if that works for you.

Please let me know if you have any more questions or problems. I’m happy to help out!

Best, 

Alex

On Jul 8, 2016, at 4:44 PM, Billings, Jay Jay <billingsjj@xxxxxxxx> wrote:

Great! Thanks. Alex will answer it then.

Jay

Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
From: ice-users-bounces@xxxxxxxxxxx <ice-users-bounces@xxxxxxxxxxx> on behalf of K. N. Ramachandran <knram06@xxxxxxxxx>
Sent: Friday, July 08, 2016 3:49 PM
To: Ice user discussions
Subject: Re: [ice-users] Developing MOOSE with ICE
 
Hi Jay,

Thanks for your quick reply. This can wait till Monday, no problem.

Thank You.

On Fri, Jul 8, 2016 at 3:40 PM, Billings, Jay Jay <billingsjj@xxxxxxxx> wrote:
Alex McCaskey can help you with this, but he is out of the office until Monday. Can this wait until then or is it immediate?

In the meantime, I have created a ticket to track progress on getting this fixed (and assigned it to Alex). You can see it here:


Jay

Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
From: ice-users-bounces@xxxxxxxxxxx <ice-users-bounces@xxxxxxxxxxx> on behalf of K. N. Ramachandran <knram06@xxxxxxxxx>
Sent: Friday, July 08, 2016 3:21 PM
To: ice-users@xxxxxxxxxxx
Subject: [ice-users] Developing MOOSE with ICE
 
Hello all,

I have just started becoming familiar with Eclipse ICE and obtained a Linux binary build using the Python install script. I am currently following the instructions at https://wiki.eclipse.org/Developing_MOOSE_Applications_with_ICE and I am having some trouble here.

I am stuck at the "Adding a Kernel" section. I am facing the following issues and I feel I followed all the preceding instructions clearly.

1) I am able to Add the Kernel and I get the header and src files. But Eclipse is not able to find the "Kernel.h" and I get an "Unresolved inclusion" there as well as other places in the file.

2) Trying to execute the Make target for the Moose App only results in "Info: Nothing to build for testMoose" where testMoose is my app name.

3) When I check the Properties for testMoose, I notice an error message under the "C/C++ Build" section which says:

Toolchain "LLVM with GCC (Linux)" is not detected.

So is the LLVM toolchain necessary? I compiled libMesh using the standard Linux GCC toolchain and I had no issues there.

Any help would be greatly appreciated here.


Thanking You,
K.N.Ramachandran

_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users




-- 
K.N.Ramachandran
_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users


_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users




--
K.N.Ramachandran
<eclipse_ice_error.png>_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users


_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users




--
K.N.Ramachandran
_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users


_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users




--
K.N.Ramachandran



--
K.N.Ramachandran

_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users




--
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings

_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users




--
K.N.Ramachandran

_______________________________________________
ice-users mailing list
ice-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-users




--
K.N.Ramachandran

Back to the top