-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Error cloning new version msoffice #31
Comments
If you use an old OpenSSL library, then |
I tried running the current build normally and with |
Oh, I found the reason. I removed bin/*.exe, so there is no |
Now it works!! |
I've been using this package for the last 3 years.
I used it in August 2023, no issues whatsoever.
I used it today (October 3, 2023) and I got the following error
make[1]: Entering directory '/content/msoffice/src' g++ -c msoffice-crypt.cpp -o release/msoffice-crypt.o -g -D_FILE_OFFSET_BITS=64 -Wall -Wextra -Wformat=2 -Wcast-qual -Wcast-align -Wwrite-strings -Wfloat-equal -Wpointer-arith -O2 -DNDEBUG -I/content/msoffice/include -I/content/msoffice/../cybozulib/include g++ -c attack.cpp -o release/attack.o -g -D_FILE_OFFSET_BITS=64 -Wall -Wextra -Wformat=2 -Wcast-qual -Wcast-align -Wwrite-strings -Wfloat-equal -Wpointer-arith -O2 -DNDEBUG -I/content/msoffice/include -I/content/msoffice/../cybozulib/include g++ release/attack.o -o /content/msoffice/bin/attack.exe -lcrypto -L/content/msoffice/lib -lcrypto -lpthread -lrt /usr/bin/ld: cannot open output file /content/msoffice/bin/attack.exe: No such file or directory collect2: error: ld returned 1 exit status make[1]: *** [../common.mk:68: /content/msoffice/bin/attack.exe] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory '/content/msoffice/src' make: *** [Makefile:7: all] Error 2
I used it in Colab which runs on Linux.
I don't understand what it means, so my solution was to make a fork and go back to version 89dbedf add OLD_OPENSSL option. This commit was made back in March 2023. Ran the script again and everything worked.
The text was updated successfully, but these errors were encountered: