Closed smclinden closed 6 years ago
Thx for the feedback. I'll try to reproduce this to determine what has changed on macOS.
I did see this warning:
checking for egrep... /usr/bin/grep -E
checking whether gcc needs -traditional... no
checking whether make sets $(MAKE)... (cached) yes
configure: WARNING: Libtool does not cope well with whitespace in pwd
Yes I also cannot install the tool on OS X High Sierra (10.13.3)
Clicking install anyways errors out. Any pointers in making it work on my version of OS X?
I did not see the warning @smclinden mentioned.
@deeg libpff does not come with an macOS installation pkg, what did you try to install?
@joachimmetz, thanks for quick response.
I followed the instructions on this page, in order to build a .pkg install file. I then tried running that install file.
FWIW, it was the same steps I tried previously on an older version of Mac OS X (Yosemite) which worked successfully the first time.
I even tried the old .pkg file which I successfully built and installed on Yosemite before updating. After updating I tried both that .pkg as well as running through the steps from scratch again and creating the .pkg over again. I made sure to install and update all dependencies listed in your documentation.
I get no errors along the way when trying to generate the .pkg as far as I could tell.
this is likely a different issue then initially reported in this issue.
/usr/local
due to "System Integrity Protection"@joachimmetz, sorry for hijacking another thread, didn't realize it was discussing different topics.
try changing the prefix to /usr/local due to "System Integrity Protection"
This did the trick, thanks very much!
Ran default build from a path with a space on High Sierra.
/Users/username/Projects/with space/libpff
../libtool: line 5679: cd: /Users/username/Projects/with: No such file or directory
../libtool: line 1720: cd: .libs/libpff.lax/libcerror.a: No such file or directory
This looks like an issue in ../libtool
which is generated by glibtoolize on MacOS.
glibtoolize --version
glibtoolize (GNU libtool) 2.4.6
For now the recommendation is not to build from a path with spaces.
Closing issue, seeing this is a short coming in one of the dependencies
As an example, to correct errors such as the following, I have had to manually build all the dependencies rather than use the "synclibs.sh" script.
libtool: link: (cd ".libs" && rm -f "libpff.dylib" && ln -s "libpff.1.dylib" "libpff.dylib") ../libtool: line 5679: cd: /Users/seanmclinden/Cyfir/Murray/Exchange: No such file or directory libtool: link: (cd .libs/libpff.lax/libcsplit.a && ar x "/Users/seanmclinden/Cyfir/Murray/Exchange Logs/libpff/libpff/../libcsplit/.libs/libcsplit.a") ../libtool: line 1720: cd: .libs/libpff.lax/libcsplit.a: No such file or directory