1

ARGGHH ? WHY !?

[user@localhost pkgconfig]$ ls

libcrypto.pc libpng16.pc libssh2.pc libtiff-4.pc openssl.pc zlib.pc
libjpeg.pc libpng.pc libssl.pc libtls.pc sqlite3.pc

[user@localhost pkgconfig]$ pkg-config --cflags "openssl"

Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'virtual:world', not found

[user@localhost pkgconfig]$ echo $PKG_CONFIG_PATH

/CustomPath/lib/pkgconfig/

[user@localhost pkgconfig]$ PKG_CONFIG_PATH=/CustomPath/lib/pkgconfig

[user@localhost pkgconfig]$ pkg-config --cflags "openssl"

Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'virtual:world', not found

Comments
  • 0
    @AtuM this is inside the shell. one line at a time.
  • 0
    @AtuM OMFG WHY ???? WHY DID THAT WORK ????
  • 0
    @AtuM SOMEONE NEEDS TO EXPLAIN TO ME RIGHT FING NOW WHY THAT WORKED !!!!! ENVIRONMENT VARIABLES ARE SUPPOSED TO BE ENVIRONMENT VARIABLES IN THE SHELL !

    ONLY SUBPROCESSES OF SCRIPTS ARE SUPPOSED TO NEED EXPORT RIGHT :???
  • 1
    @MadMadMadMrMim Environment variables always have to be exported (if not exported, they are shell variables)

    Shell variables are available for the current shell / current script and sourced scripts, but not subprocesses. They do not need to be exported.
  • 0
  • 0
    @sbiewald so if i source a script ?
  • 0
    @molaram I shall not deprive you of your jip mother fucker lol
Add Comment