mark brethen <mbrethen@aim.com> on Tuesday, May 15, 2007 at 5:18 PM -0800 wrote:

port search for libmad-dev & libmad-devel showed no ports available. What are my options? I need this to compile a program.

Do you mean audio/libmad? I'm not familiar with it but have you seen that? Mark

mark brethen <mbrethen@aim.com> on Tuesday, May 15, 2007 at 5:59 PM -0800 wrote:

Well, I already installed libmad, and checked its contents

Port libmad contains: /opt/local/include/mad.h /opt/local/lib/libmad.0.2.1.dylib /opt/local/lib/libmad.0.dylib /opt/local/lib/libmad.a /opt/local/lib/libmad.dylib /opt/local/lib/libmad.la

Why then does it not find it when I do a make root_install? The error below,

checking for mad_frame_decode in -lmad... no configure: error: libmad needed! Download the latest version at http://www.mars.org/home/rob/proj/mpeg/ make: *** [root_libmp3splt] Error 1

Well it looks like it has all the files: http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/audio/libmad/pkg-plis... I wonder if this is normal? Anyone? otool -L /opt/local/lib/libmad.0.2.1.dylib /opt/local/lib/libmad.0.2.1.dylib: /opt/local/lib/libmad.0.dylib (compatibility version 3.0.0, current version 3.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.4) I'm beyond my knowledge on this, but I see the freebsd port set it in pkg-config. Could configure be consulting that? If so, uninstall it and try the fixed up one I attached. Just cd to the unzipped directory and do a port install from there. It adds: /opt/local/lib/pkgconfig/mad.pc And so pkg-config works: $ pkg-config --libs mad -L/opt/local/lib -lmad -lm If that doesn't do it I'm out of guesses. If it does, tell me and I'll commit the changes. Mark

mark brethen <mbrethen@aim.com> on Wednesday, May 16, 2007 at 3:55 AM -0800 wrote:

...

mark brethen <mbrethen@aim.com> on Tuesday, May 15, 2007 at 5:59 PM -0800 wrote:

...

Well, I already installed libmad, and checked its contents

Port libmad contains: /opt/local/include/mad.h /opt/local/lib/libmad.0.2.1.dylib /opt/local/lib/libmad.0.dylib /opt/local/lib/libmad.a /opt/local/lib/libmad.dylib /opt/local/lib/libmad.la

Why then does it not find it when I do a make root_install? The error below,

checking for mad_frame_decode in -lmad... no configure: error: libmad needed! Download the latest version at http://www.mars.org/home/rob/proj/mpeg/ make: *** [root_libmp3splt] Error 1

Well it looks like it has all the files:

http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/audio/libmad/ pkg-plist?rev=1.3;content-type=text%2Fplain

I wonder if this is normal? Anyone?

otool -L /opt/local/lib/libmad.0.2.1.dylib /opt/local/lib/libmad.0.2.1.dylib: /opt/local/lib/libmad.0.dylib (compatibility version 3.0.0, current version 3.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.4)

I'm beyond my knowledge on this, but I see the freebsd port set it in pkg-config. Could configure be consulting that? If so, uninstall it and try the fixed up one I attached. Just cd to the unzipped directory and do a port install from there. It adds:

/opt/local/lib/pkgconfig/mad.pc

And so pkg-config works:

$ pkg-config --libs mad -L/opt/local/lib -lmad -lm

If that doesn't do it I'm out of guesses. If it does, tell me and I'll commit the changes.

Mark

<libmad.zip>

I'll try it later today. One thing I noticed, this file:

libdata/pkgconfig/mad.pc

is not in my /opt/local directory. In fact, I can't find it anywhere.

That's the one that my modifications added. That was the one that the freebsd port had that the MacPorts one lacked. Mark

mark brethen <mbrethen@aim.com> on Wednesday, May 16, 2007 at 6:37 PM -0800 wrote:

...

...

I'll try it later today. One thing I noticed, this file:

libdata/pkgconfig/mad.pc

is not in my /opt/local directory. In fact, I can't find it anywhere.

That's the one that my modifications added. That was the one that the freebsd port had that the MacPorts one lacked.

Mark

I installed your modified port but I get this:

brethen-familys-Computer:~ marbre$ pkg-config --libs mad Package mad was not found in the pkg-config search path. Perhaps you should add the directory containing `mad.pc' to the PKG_CONFIG_PATH environment variable No package 'mad' found

Not sure why. Everything else is there.

I updated the portfile to revision 1. Try it after it revision 1 appears via selfupdate. It is always possible that the problem you are experiencing has nothing to do with pkg-config. If so this will make no difference of course. I have my fingers crossed. If not, tell us exactly are you trying to do with the port. I know nothing about libmad. Mark

mark brethen <mbrethen@aim.com> on Saturday, May 19, 2007 at 7:05 AM -0800 wrote:

Just to update you on the status. I contacted the mp3splt author at sourceforge.net and he was able to walk me through the install. After updating the libmad port I had to use

export CFLAGS="$CFLAGS -I/opt/local/include" export LDFLAGS="$LDFLAGS -L/opt/local/lib"

before configuring libmp3splt. The latest build of mp3splt (subversion) fixes the cddb function. This doesn't work in the version that the mp3splt port installs. If someone would guide me, I could create an alternate (i.e. subversion) port install.

Ah I see. When installing software manually, it will usually need to be told where to find MacPorts libraries. That is only one reason I don't do it anyore. If a port I need doesn't exist, I create it. I don't understand the difference between libmp3splt and mp3splt. Do we need a port for each? Also, there are several ways to handle updating a macport to handle newer (but beta or alpha) code. 1) One way is to create a portname-devel package in cases where a new version introduces incompatibilities *and* actual users we currently have will want to use both. Just the mere hypothetical possibility of needing both is insufficent to create to ports, and only to be done when necessary. 2) If the alpha or beta is fairly stable, or the user base of the port is low, or the bugs solved are significant enough that is is preferred to use the beta over the release for most users, then it is justified to use betas, release candiates, and even alpha code under the right circumstances. We don't like port and variant proliferation without good reasons. So the question is, is the mp3splt2.2_rc1 solve your problem? And in your judgement does it meet the criteria of #2? If so, we could update the port to rc_1. If not, if the particular bugfix in subversion is a discrete patch or patches, those could be added to the port to make the port more usable. Mark