id3lib

[rac]

I ran into a few problems building id3lib-3.8.0_pre2-r1 using GCC 3.1, and here's how
I solved a few of them. I'm not yet sure whether the library actually functions correctly or
not, but it does build now.

a. The GCC 3 patch in -r1 didn't fire for me under 3.1. I don't have a 3.0.4 handy to
confirm this, but I suspect that 3.1 is more verbose in its responses to

solution: change the version checking logic in src_unpack from:

if [ "`gcc --version | cut -f1 -d.`" -eq 3 ]

to:

if [ "`gcc -v 2>&1 | sed -n 's/gcc version //p' | cut -f1 -d.`" -eq 3 ]

b. configure is explicitly checking for header files that are deprecated, and tanks out
if it can't find them. I simply eliminated the checks, by tagging the following on to the
GCC 3 patch file:

diff -w -b -B -u -U 5 -r -P -x '*~' -x '*.[oa]' id3lib-3.8.0pre2/configure id3lib-3.8.0pre2.rac/configure
--- id3lib-3.8.0pre2/configure Sat Sep 8 15:14:00 2001
+++ id3lib-3.8.0pre2.rac/configure Fri May 31 13:51:08 2002
@@ -2614,11 +2614,8 @@
fi
done

for ac_hdr in \
string \
- fstream.h \
- iostream.h \
- iomanip.h \

do
ac_safe=`echo "$ac_hdr" | sed 'y%./+-%__p_%'`
diff -w -b -B -u -U 5 -r -P -x '*~' -x '*.[oa]' id3lib-3.8.0pre2/configure.in id3lib-3.8.0pre2.rac/configure.in
--- id3lib-3.8.0pre2/configure.in Sat Sep 8 14:38:20 2001
+++ id3lib-3.8.0pre2.rac/configure.in Fri May 31 13:50:56 2002
@@ -134,11 +134,8 @@
AC_CHECK_HEADERS(libcw/sys.h)
AC_CHECK_HEADERS(cctype climits cstdio cstdlib cstring)
AC_CHECK_HEADERS(fstream iostream iomanip)
AC_CHECK_HEADERS( \
string \
- fstream.h \
- iostream.h \
- iomanip.h \
,,AC_MSG_ERROR([Missing a vital header file for id3lib])
)
_________________
For every higher wall, there is a taller ladder

[lasse]

I had a similar problem with config.in checking for deprecated header files when building htdig. You can pass an option to the pre-processor used by ./configure to get around this:

CPPFLAGS=-Wno-deprecated emerge id3lib

The same option can be added to CFLAGS and CXXFLAGS if you want to get rid of the warnings during compilation.

This doesn't solve the first problem though but is perhaps a bit cleaner for the second...

/Lasse

[rac]

GCC3 to Portage & Programming. Even though the bozo that started the thread (who really needs to learn how to make code blocks) wasn't really asking for help, I guess it qualifies for the "heads up" post loophole.
_________________
For every higher wall, there is a taller ladder