Coder Social home page Coder Social logo

Comments (25)

Trent54 avatar Trent54 commented on August 16, 2024

Oops, forgot to attach output of make
libcaes error

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

how did you get the source via git or from the source distribution package ?

Can you attach your config.log

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

@Trent54 it looks like your previous message did not contain all the data, don't use the reply via email option it has limitations.

You are running the development version as explained here https://github.com/libyal/libcaes/wiki/Building#read-first
If you're not developing libcaes or libfsapfs, then I opt to not use this version.

(I repeat) can you attach your config.log

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

It is attached. Thank you again!

It is not, since you did use reply via email again

Per the github reply "it looks like your previous message did not contain all the data, don't use the reply via email option it has limitations."

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

config.log

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

#elif defined( HAVE_LIBCRYPTO ) && defined( HAVE_OPENSSL_EVP_H ) && ( defined( HAVE_EVP_CRYPTO_AES_CBC ) || defined( HAVE_EVP_CRYPTO_AES_ECB ) )

#elif defined( HAVE_LIBCRYPTO ) && defined( HAVE_OPENSSL_EVP_H ) && ( defined( HAVE_EVP_CRYPTO_AES_CBC ) || defined( HAVE_EVP_CRYPTO_AES_ECB ) )

Per config.log

| #define HAVE_OPENSSL_EVP_H 1
| #define HAVE_LIBCRYPTO 1
| #define HAVE_OPENSSL_AES_H 1
...
ac_cv_libcrypto=yes
ac_cv_libcrypto_CPPFLAGS=-I/opt/local/include
ac_cv_libcrypto_LIBADD=-lcrypto
ac_cv_libcrypto_aes=no
ac_cv_libcrypto_aes_cbc=no
ac_cv_libcrypto_aes_ecb=no
ac_cv_libcrypto_aes_xts=no
ac_cv_libcrypto_dummy=no
ac_cv_libcrypto_evp=yes
ac_cv_libcrypto_evp_cipher=no

But the following are missing:

HAVE_AES_CBC_ENCRYPT
HAVE_AES_ECB_ENCRYPT
HAVE_EVP_CRYPTO_AES_CBC
HAVE_EVP_CRYPTO_AES_ECB

So LIBCAES_HAVE_AES_SUPPORT is not set in

#elif defined( HAVE_LIBCRYPTO ) && defined( HAVE_OPENSSL_EVP_H )
since both HAVE_LIBCRYPTO and HAVE_OPENSSL_EVP_H are set but your OpenSSL build does not appear to have the EVP Cypher functions.

I'll have a look to change m4/libcrypto.m4 to account for this case in the mean time run configure with --with-openssl=no to disable OpenSSL support.

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

Awesome, I'll give it a try now. Thank you!

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

Or this might be related to your build environment not properly configured:

ld: library not found for -lcrypto
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Try setting (or equivalent that corresponds with your system):

export CFLAGS="-I/usr/local/include -I/usr/local/opt/[email protected]/include ${CFLAGS}";
export LDFLAGS="-L/usr/local/lib -L/usr/local/opt/[email protected]/lib ${LDFLAGS}";

before running ./configure

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

Hmmm...

Was getting another error with before (see below) but will try that way
image

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

Still same error after setting CFLAGS & LDFLAGS per above.
image

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

You'll need to run ./synclibs.sh and ./autogen.sh as indicated here https://github.com/libyal/libcaes/wiki/Building#git

I repeat using the source from git is NOT recommended if you're not developing libcaes.

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

Here is an ls of my libcerror directory
image

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

I tried following directions, really :) I did that but had an error.

image

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

This error:
image

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

Why is that an error?

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

It isn't?

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

I thought it was because reinstalling libcaes didn't fix the original problem. (attached).

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

I also installed liberror separately - I'm guessing I shouldn't have done that because there is a libcerror directory inside libcaes and one in the git directory

image

from libcaes.

joachimmetz avatar joachimmetz commented on August 16, 2024

You are not listening to my advise nor are you following the instructions that have been written to prevent people falling in to the trap of trying to use the version that is intended for development only.

  1. Stop using the source from git directly.
  2. Use https://github.com/libyal/libfsapfs/releases/download/20200416/libfsapfs-experimental-20200416.tar.gz

It has all the dependencies included. Use --with-openssl=no or make sure to set up CFLAGS & LDFLAGS as indicated before.

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

I am sorry, I am new to using git.

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

I will build from inside the .tar.gz which I have downloaded. I didn't understand which part of your directions applied to what. I remember I started with Mac OS build from package, then after that failed I found the build from source directions.

from libcaes.

Trent54 avatar Trent54 commented on August 16, 2024

I see now. This is more to my unfamiliarity with git I think. I found an article about libfsapfs, searched and found the project on git, clicked documentation and clicked "build from source." I actually thought that's all anyone could use GitHub for and did not understand the concept of separate releases.

I don't mean to imply the documentation does not make this clear. Thank you again for all your help.

image

from libcaes.

Related Issues (16)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.