Forum: Ruby ID3Lib 0.5.0 problems installing on FreeBSD

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
(Guest)
on 2007-08-01 22:08
(Received via mailing list)
Gems is not finding my id3.h file which is clearly inside of /usr/
local/include/id3.h. When I try to install I get the following
message:

> sudo gem install id3lib-ruby
Password:
Need to update 2 gems from http://gems.rubyforge.org
..
complete
Select which gem to install for your platform (i386-freebsd4)
 1. id3lib-ruby 0.5.0 (ruby)
 2. id3lib-ruby 0.5.0 (mswin32)
 3. id3lib-ruby 0.4.1 (mswin32)
 4. id3lib-ruby 0.4.1 (ruby)
 5. Skip this gem
 6. Cancel installation
> 1
Building native extensions.  This could take a while...
ERROR:  While executing gem ... (Gem::Installer::ExtensionBuildError)
    ERROR: Failed to build gem native extension.

ruby extconf.rb install id3lib-ruby
checking for main() in -lstdc++... yes
checking for main() in -lz... yes
checking for id3.h... no
You must have id3lib installed in order to use id3lib-ruby.
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.  Check the mkmf.log file for more
details.  You may need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/usr/local/bin/ruby18
        --with-stdc++lib
        --without-stdc++lib
        --with-zlib
        --without-zlib


Gem files will remain installed in /usr/local/lib/ruby/gems/1.8/gems/
id3lib-ruby-0.5.0 for inspection.
Results logged to /usr/local/lib/ruby/gems/1.8/gems/id3lib-ruby-0.5.0/
ext/gem_make.out

I printed out the log and I get:
have_library: checking for main() in -lstdc++... --------------------
yes

"cc -o conftest -I. -I/usr/local/lib/ruby/1.8/i386-freebsd4 -I.  -g -O
-pipe -D$
checked program was:
/* begin */
1: /*top*/
2: int main() { return 0; }
3: int t() { void ((*volatile p)()); p = (void ((*)()))main; return
0; }
/* end */

--------------------

have_library: checking for main() in -lz... -------------------- yes

"cc -o conftest -I. -I/usr/local/lib/ruby/1.8/i386-freebsd4 -I.  -g -O
-pipe -D$
checked program was:
/* begin */
1: /*top*/
2: int main() { return 0; }
3: int t() { void ((*volatile p)()); p = (void ((*)()))main; return
0; }
/* end */

--------------------

have_header: checking for id3.h... -------------------- no

"cc -E -I. -I/usr/local/lib/ruby/1.8/i386-freebsd4 -I.  -g -O -pipe -
DISERVER $
conftest.c:1: id3.h: No such file or directory
checked program was:
/* begin */
1: #include <id3.h>
/* end */

--------------------

any ideas? TIA!
Felipe C. (Guest)
on 2007-08-02 12:06
(Received via mailing list)
Hi,

On 8/1/07, removed_email_address@domain.invalid 
<removed_email_address@domain.invalid> wrote:
> Gems is not finding my id3.h file which is clearly inside of /usr/
> local/include/id3.h. When I try to install I get the following
> message:

You could try libmtag instead.
http://code.google.com/p/libmtag/

I created that project so if you have any problems I'll be glad to help
you.

Cheers.
Lance C. (Guest)
on 2007-08-02 19:38
(Received via mailing list)
I will definately check it out. I was using mp3info before id3lib but
it was unreliable. ID3Lib produces the best results thusfar, but if
your library works better I would be glad to use this one over any
alternatives. I will let you know how it goes!
Lance C. (Guest)
on 2007-08-09 00:01
(Received via mailing list)
btw, i figured it out. My comments on this page should help anyone
that runs into this problem in the future:

http://rubyforge.org/tracker/index.php?func=detail...
This topic is locked and can not be replied to.