mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #2] Can't install - package requirements #2
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jacobischwartz on GitHub (Dec 25, 2013).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2
Hi,
I've installed s3fs before on other Ubuntu systems but this time I'm running into issues. This is also the first time I'm using a Bitnami Ubuntu stack so it's completely possible that's related. Here's my install attempt:
The interesting thing is that the packages listed ARE installed and DO meet the version requirements:
Obviously pkg-config can see those packages so I'm not sure why the installer can't. Any ideas what's going on?
Cheers,
Jacob
@stuart-warren commented on GitHub (Dec 27, 2013):
Try (should work for Ubuntu precise)
sudo apt-get install libfuse-dev libcurl4-openssl-dev libxml++2.6-dev libssl-dev
@jacobischwartz commented on GitHub (Dec 27, 2013):
Thanks - just tried that. Here's the package install output:
Unfortunately I got the exact same errors when trying to install s3fs.
Here's the updated pkg-config --list-all output:
Are you aware of any hard path dependencies? I know that Bitnami puts things in different locations than most Ubuntu instances. I had to modify the PATH variable just to get pkg-config to list those packages. See here:
http://flummox-engineering.blogspot.com/2011/06/workaround-for-bitnamis-custom-path.html
@jonstanley commented on GitHub (Jan 14, 2014):
Build the source the Debian way... and works for me on Ubuntu 12.04.4LTS (precise) and 14.04 (trusty). Install
dh-makepackage if you haven't already... I ignored themake testequivalent part as didn't want to run the build as root. There's something about shoulds3fsever go into the Debian/Ubuntu repo, the Debianised source needs to be able to build without invoking root.My
./debian/controllooks like this:@jacobischwartz commented on GitHub (Jan 25, 2014):
Cheers, that all seemed to work (though I used the more recent 1.76 version of s3fs). The first time I tried building, it quit with the following error:
So I changed the source and package names to s3fs-fuse and it seemed to install without errors (some warnings):
But to be honest this is stretching the limit of my experience... I guess I'm not really confident that things installed correctly and I don't even know where the installed package sits :P
So based on all this,
Thanks a lot!
Jacob
@jonstanley commented on GitHub (Jan 26, 2014):
You can issue a
which s3fsto see where it was installed (/usr/binIIRC), then issue aman s3fswhich tells you how to use it... then just try out some of the commands, mounting an S3 bucket and seeing if you can read/write/delete to it.@jacobischwartz commented on GitHub (Jan 26, 2014):
The which command returned nothing and man couldn't find a manual for s3fs. So I'm guessing that unfortunately the install didn't succeed...?
@jonstanley commented on GitHub (Jan 28, 2014):
After the package built, did you install the
.debfile (found in the parent dir of the source-tree) withsudo dpkg -i s3fs_1.74-1_amd64.deb?@jacobischwartz commented on GitHub (Feb 2, 2014):
Silly me. Looks like that did the trick. Cheers for all your help!
@jacobischwartz commented on GitHub (Feb 2, 2014):
Er I might have spoken too soon. Sorry it took me a couple days to get back to this.
The install seemed to go well but I still can't verify/use the installation. Here's the install output:
Which and man can't find s3fs (or s3fs-fuse).
@jsanpedro commented on GitHub (May 22, 2014):
I may have found an easy workaround for this problem. I was able to build this in Ubuntu 14.04 just by using the following:
autoreconf --install
CPPFLAGS=-I/usr/include/libxml2 ./configure
make install
For some reason the include directory for libxml2 is different than the configure script expects. Let me know if this worked for you guys!
@ggtakec commented on GitHub (May 25, 2014):
I don't know why libxml2 include path is not generate in Makefile.
Could you check the DEPS_CFLAGS value in Makefile before you installed autoreconf?
(And now what value does your Makefile have for DEPS_CFLAGS after installed?)
My Makefile on ubuntu 14.04 has following:
DEPS_CFLAGS = -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse -I/usr/include/libxml2
Regards,
@intelliant01 commented on GitHub (Aug 12, 2015):
Am on an Ubuntu 12.04 LTS Bitnami Magento stack, hence am posting it herein as it seems a quiet similar problem.
Have been trying to install s3fs latest release available herein.
Will a lot of struggle managed to get some of the package dependencies resolved. However, have not succeeded completely. Hence am here seeking help before giving up.
Had to adjust the PKG_CONFIG_PATH to ensure all library modules were being picked up -
as I found several non-standard module installations -
Am not sure if the problem is more due to the bitnami way of organising stuff or plain ubuntu problem.
Any guidance in this regard will be much appreciated.
The alternate solution seems to be to upgrade the bitnami stack to 14.04 Ubuntu, which is something I would like to avoid for another month or so at least.
@kahing commented on GitHub (Aug 12, 2015):
my guess is that it's picking up libcurl from /opt but that's incompatible with your libssl in /lib.
@intelliant01 commented on GitHub (Aug 13, 2015):
@kahing You were spot on -
Modified
to
and it is all working perfectly fine.
Thank you.
@ggtakec commented on GitHub (Jan 17, 2016):
I closed this issue, but if you have more problem, pleae post new issue.
Thanks in advance for your help.