-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add sei chain #99
Add sei chain #99
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the bash changes were fairly large, but I trust the builds are working as intended.
If I had more time, I'd ask ChatGPT to explain what all the bash is doing as part of this review. 😆
RUN bash -c 'set -eux;\ | ||
i=0; for BIN in /root/bin/*; do\ | ||
echo "Getting $(uname -m) libs for bin: $BIN";\ | ||
readarray -t LIBS < <(ldd "$BIN");\ | ||
for LIB in "${LIBS[@]}"; do\ | ||
PATH1=$(echo $LIB | awk "{print \$1}");\ | ||
if [ "$PATH1" = "linux-vdso.so.1" ]; then continue; fi;\ | ||
PATH2=$(echo $LIB | awk "{print \$3}");\ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No change now. But I had a thought. I bet these long bash commands will be easier to read if in a .sh
or .bash
file that's copied into the container. We'd get IDE syntax highlighting, for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. Will handle that as a follow up
* Add Sei chain * wip * Move to cargo build strategy * Update chains.yaml * Integrate optional go install/build into cargo dockerfile
set -eux
to all dockerfile script steps to catch any errors along the way instead of proceeding past them.