-
Notifications
You must be signed in to change notification settings - Fork 161
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
lftp 4.9.1 alpine linux static build - lftp -v and linked libraries issue #569
Comments
Most probably the problem is with dlsym function which does not work in the
static binary. It's only used in the version output. I think it's better to
suppress the libraries message if it cannot detect any.
ср, 29 янв. 2020, 23:53 userdocs <notifications@github.com>:
… I have managed to create fully static and portable build on Alpine linux
3.11 but i have encountered an odd issue.
Here is the build script and example binary for reference and testing -
https://github.com/userdocs/lftp-static
The problem?
When i build lftp only using -static i see this (binary size 10829KB)
Please note the Libraries used: line showing linked libraries.
[image: lftp-not-static]
<https://user-images.githubusercontent.com/16525024/73395942-51257580-42d8-11ea-90ba-0f0103e41784.png>
When i then build using --static -static i see this (binary size 12637KB)
[image: lftp-static]
<https://user-images.githubusercontent.com/16525024/73395982-64384580-42d8-11ea-8ea6-08a25114d331.png>
When i do lftp -v there Libraries used: section is blank for for all my
testing it appears to be a fully functional and portable binary.
I can move this binary to another Linux distro like Debian 10 and use it
with no obvious issues.
*Is this a bug where statically linked libraries are not listed properly
in when using lftp -v?*
I tested using ftps/sftp this test server https://test.rebex.net/ and it
worked fine so it appears the libraries are linked and functional but not
showing in lftp -v
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#569?email_source=notifications&email_token=AAHLWXEU4NFLWQG76C5FVFTRAHUEJA5CNFSM4KNLJ2H2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IJUZ6VQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHLWXE5G6I6JIIOJYNMQMLRAHUEJANCNFSM4KNLJ2HQ>
.
|
Ok, thanks for the info. I just wanted to check if it was something minor i can ignore or if my build was failing to link the libraries. What you said about suppressing the output makes sense. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have managed to create fully static and portable build on Alpine linux 3.11 but i have encountered an odd issue.
Here is the build script and example binary for reference and testing - https://github.com/userdocs/lftp-static
The problem?
When i build lftp only using
-static
i see this (binary size 10829KB)Please note the
Libraries used:
line showing linked libraries.When i then build using
--static -static
i see this (binary size 12637KB)When i do
lftp -v
thereLibraries used:
section is blank but for all my testing it appears to be a fully functional and portable binary. I can move this binary to another Linux distro like Debian 10 and use it with no obvious issues.Is this a bug where statically linked libraries are not listed properly in when using
lftp -v
?I tested it using
ftps
/sftp
with this test server https://test.rebex.net/ and it worked fine so it appears the libraries are linked and functional but not showing inlftp -v
The text was updated successfully, but these errors were encountered: