-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
input-mesh
fails to compile on queenbee2
#1119
Comments
wgrid2
fails to compile on queenbee2input-mesh
fails to compile on queenbee2
Basic approach to troubleshoot is:
|
…linking on QB. Issue 1119: Added explicitly the required libraries during the linking phase, seems everything was correct except this final step. It's a mystery why this was only being exposed on queenbee2 (LONI), but this changes fixes it. Resolves #1119.
…linking on QB. Issue 1119: Added explicitly the required libraries during the linking phase, seems everything was correct except this final step. It's a mystery why this was only being exposed on queenbee2 (LONI), but this changes fixes it. Resolves #1119. Resolves #1121 (PR). (cherry picked from commit 7b0b5d6) Signed-off-by: wwlwpd <46434714+wwlwpd@users.noreply.github.com>
…linking on QB. Issue 1119: Added explicitly the required libraries during the linking phase, seems everything was correct except this final step. It's a mystery why this was only being exposed on queenbee2 (LONI), but this changes fixes it. Resolves #1119. Resolves #1121 (PR). (cherry picked from commit 7b0b5d6) Signed-off-by: wwlwpd <46434714+wwlwpd@users.noreply.github.com>
I just tried to login to hatteras, and I don't think my login works any more. Here's how I debug everything. Given,
You can straight up skip breaking steps for debugging purposes. For example,
You can skip multiple steps, via:
This is how I debug. Basically I skip whatever is breaking, then the given command build; then you can run Also, look at the created
|
An extreme command to immediately get to the shell, with nothing built but the environment set up would be:
|
All the debugging tips are very useful. It turns out that the issue I was hitting when I ran with --force and the other TMPDIR was actually before the perl creation step, so I may have closed the other issue too early! At any rate, I'm now hitting a similar error message to the above even without the updated TMPDIR and the --force flag, so it is something I'll also have to deal with. Maybe --force works by uninstalling and reinstalling everything and something that it tried to reinstall failed? Unsure. Here's the error I'm hitting:
At any rate, when I run with "--skip-steps util,perl-modules" I'm able to get past both errors (the one like #766 and this one); the full install isn't done yet, but it's been chugging along for another 10+ minutes thus far. I'm going to try to debug more later from within ASGSH as you suggested. |
I feel like I should be able to figure these out, but so far it's just been a lot of unsuccessful trial and error. I'm attaching the output I'm getting from running these commands individually from within ASGSH in the hope that you may have thoughts. For util, I submitted the following command, and received the output in the attached make_util.txt.
The error looks like it's having trouble finding the NetCDF module, and the "NETCDFPATH := /usr" here feels sketchy, but given the lines below it it could be just fine; I just don't know what we actually need to include. For perl-modules, I submitted the following command, and received the output in the attached perl-modules.txt.
Its output specifically references a build.log file which should have more details on the failure, and I've also attached this. Per build.log, it looks like the build processed errored out after the following command:
It looks like this needs to be run from within asgs/opt/perl5/perls/perl-5.38.0/lib/5.38.0 given the lib paths near the end of the command, but when I try this from the shell I get:
And, sure enough, lib/Params only has a single file in it: Check.pm. There isn't even a Validate folder. So, I'm not sure if that should all be created during the compilation process / elsewhere in init-perl-modules.sh, or if I'm running this in the wrong place, or what. Would appreciate any tips or answers you may have! |
@notstarboard I am closing this issue because it was an already solved one. I know it's a little extra work, but please open this up as either another issue or in the discussions. I will converse with you there and will add my debugging steps to the wiki. |
Troubleshooting steps outlined above: |
The text was updated successfully, but these errors were encountered: