CCExtractor 0.79 fails to build on OS X #107

New Issue

claunia · 2026-01-29T16:35:25Z

claunia commented

2026-01-29 16:35:25 +00:00

Originally created by @workflowsguy on GitHub (Jan 31, 2016).

When trying to build CCextractor from Source, besides issuing several warnings, it fails with

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

Building on OS X 10.9.5 with Xcode 6 Command line tools (Apple LLVM version 6.0 (clang-600.0.57)

Originally created by @workflowsguy on GitHub (Jan 31, 2016). When trying to build CCextractor from Source, besides issuing several warnings, it fails with ``` ld: library not found for -liconv clang: error: linker command failed with exit code 1 (use -v to see invocation) : command not foundne 2: ``` Building on OS X 10.9.5 with Xcode 6 Command line tools (Apple LLVM version 6.0 (clang-600.0.57)

claunia closed this issue

2026-01-29 16:35:26 +00:00

claunia commented

2026-01-29 16:35:27 +00:00

@canihavesomecoffee commented on GitHub (Jan 31, 2016):

Hello,

could you verify if liconv is installed? Please post the output of mdfind -name libiconv | sort here, so we can help you further.

The warnings are quite normal, they appear almost every time.

@canihavesomecoffee commented on GitHub (Jan 31, 2016): Hello, could you verify if liconv is installed? Please post the output of `mdfind -name libiconv | sort` here, so we can help you further. The warnings are quite normal, they appear almost every time.

claunia commented

2026-01-29 16:35:27 +00:00

@workflowsguy commented on GitHub (Feb 1, 2016):

Here is the output from mdfind:

/usr/include/php/ext/iconv/php_have_libiconv.h
/usr/include/php/ext/iconv/php_iconv_aliased_libiconv.h
/usr/lib/libiconv.2.dylib
/usr/local/Cellar/pdftk/2.02/lib/libiconv.2.dylib

@workflowsguy commented on GitHub (Feb 1, 2016): Here is the output from mdfind: ``` /usr/include/php/ext/iconv/php_have_libiconv.h /usr/include/php/ext/iconv/php_iconv_aliased_libiconv.h /usr/lib/libiconv.2.dylib /usr/local/Cellar/pdftk/2.02/lib/libiconv.2.dylib ```

claunia commented

2026-01-29 16:35:27 +00:00

@canihavesomecoffee commented on GitHub (Feb 1, 2016):

Could you try to add this to the end of the gcc command inside the .command file? -L/usr/lib

Then you'd get this:

gcc -std=gnu99 -Wno-write-strings -DGPAC_CONFIG_DARWIN -D_FILE_OFFSET_BITS=64 -Dfopen64=fopen -Dopen64=open -Dlseek64=lseek -I ../src/gpacmp4 -I ../src/lib_ccx -I ../src/libpng -I ../src/zlib -o ccextractor $(find ../src/ -name '*.cpp' \! -name 'win_*') $(find ../src/ -name '*.c' \! -name 'win_*') -liconv -L/usr/lib

@canihavesomecoffee commented on GitHub (Feb 1, 2016): Could you try to add this to the end of the gcc command inside the .command file? `-L/usr/lib` Then you'd get this: ``` gcc -std=gnu99 -Wno-write-strings -DGPAC_CONFIG_DARWIN -D_FILE_OFFSET_BITS=64 -Dfopen64=fopen -Dopen64=open -Dlseek64=lseek -I ../src/gpacmp4 -I ../src/lib_ccx -I ../src/libpng -I ../src/zlib -o ccextractor $(find ../src/ -name '*.cpp' \! -name 'win_*') $(find ../src/ -name '*.c' \! -name 'win_*') -liconv -L/usr/lib ```

claunia commented

2026-01-29 16:35:27 +00:00

@workflowsguy commented on GitHub (Feb 1, 2016):

OK,

with the modified command line, a ccextractor binary is built, albeit with the following warning:

`'d: warning: directory not found for option '-L/usr/lib: command not foundne 2:
`

@workflowsguy commented on GitHub (Feb 1, 2016): OK, with the modified command line, a ccextractor binary is built, albeit with the following warning: `'d: warning: directory not found for option '-L/usr/lib : command not foundne 2: `

claunia commented

2026-01-29 16:35:28 +00:00

@iha commented on GitHub (Mar 8, 2016):

I got a lot of warnings, but ccextractor was compiled in El Capitan.

@iha commented on GitHub (Mar 8, 2016): I got a lot of warnings, but ccextractor was compiled in El Capitan.

claunia commented

2026-01-29 16:35:28 +00:00

@cfsmp3 commented on GitHub (Mar 8, 2016):

Are there warnings that don't relate to code itself? (such as the
-L/usr/lib one)
If yes we should solve those and have a clean build if at all possible.

On Tue, Mar 8, 2016 at 1:05 PM, Vitor Massaru Iha notifications@github.com
wrote:

I got a lot of warnings, but ccextractor was builded in El Capitan.

—
Reply to this email directly or view it on GitHub
https://github.com/CCExtractor/ccextractor/issues/271#issuecomment-193755890
.

@cfsmp3 commented on GitHub (Mar 8, 2016): Are there warnings that don't relate to code itself? (such as the -L/usr/lib one) If yes we should solve those and have a clean build if at all possible. On Tue, Mar 8, 2016 at 1:05 PM, Vitor Massaru Iha notifications@github.com wrote: > I got a lot of warnings, but ccextractor was builded in El Capitan. > > — > Reply to this email directly or view it on GitHub > https://github.com/CCExtractor/ccextractor/issues/271#issuecomment-193755890 > .

claunia commented

2026-01-29 16:35:28 +00:00

@iha commented on GitHub (Mar 9, 2016):

There are many implicit conversions like char * to unsigned char * for example, and comparisons always true or false.

Follows the gcc output warnings.

gcc.log.zip

@iha commented on GitHub (Mar 9, 2016): There are many implicit conversions like char \* to unsigned char \* for example, and comparisons always true or false. Follows the gcc output warnings. [gcc.log.zip](https://github.com/CCExtractor/ccextractor/files/164855/gcc.log.zip)

claunia commented

2026-01-29 16:35:29 +00:00

@cfsmp3 commented on GitHub (Mar 9, 2016):

Some of them are quite useful.

On Wed, Mar 9, 2016 at 10:42 AM, Vitor Massaru Iha <notifications@github.com

wrote:

There are many implicit conversions like char * to unsigned char * for
example, and comparisons always true or false.

Follows the gcc output warnings.

gcc.log.zip
https://github.com/CCExtractor/ccextractor/files/164855/gcc.log.zip

—
Reply to this email directly or view it on GitHub
https://github.com/CCExtractor/ccextractor/issues/271#issuecomment-194212238
.

@cfsmp3 commented on GitHub (Mar 9, 2016): Some of them are quite useful. On Wed, Mar 9, 2016 at 10:42 AM, Vitor Massaru Iha <notifications@github.com > wrote: > > There are many implicit conversions like char \* to unsigned char \* for > example, and comparisons always true or false. > > Follows the gcc output warnings. > > gcc.log.zip > https://github.com/CCExtractor/ccextractor/files/164855/gcc.log.zip > > — > Reply to this email directly or view it on GitHub > https://github.com/CCExtractor/ccextractor/issues/271#issuecomment-194212238 > .

claunia commented

2026-01-29 16:35:29 +00:00

@barun511 commented on GitHub (Mar 12, 2016):

The build seems to work fine for me. I did have a libiconv issue, but that was due to conflicting macports and mac installations...removing macports and switching to homebrew fixed it for me, and the compilation went through smoothly.

@barun511 commented on GitHub (Mar 12, 2016): The build seems to work fine for me. I did have a libiconv issue, but that was due to conflicting macports and mac installations...removing macports and switching to homebrew fixed it for me, and the compilation went through smoothly.

claunia commented

2026-01-29 16:35:29 +00:00

@cfsmp3 commented on GitHub (Mar 18, 2016):

Current github confirmed working, reopen if/when it breaks again

@cfsmp3 commented on GitHub (Mar 18, 2016): Current github confirmed working, reopen if/when it breaks again

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ccextractor#107