Solved it!  [For me, anyway]

I decided I'd better get round to building 6.15 on my Mint system,
and yep, I hit the same problem as you!

Noting that, as you saw, the lame header is ...include/lame/lame.h,
I took a wild guess and linked that to .../include/lame.h.

Cmake then easily found it, and libmp3out got compiled!

Not sure where the real mismatch is.  I assume that the header
is always where it is on linux, so it's probably that the Cmake
search is set up wrongly.  I'll leave that to the Cmake gurus, though.

	-- Pete --


On Sat, Aug 29, 2020 at 06:05:59PM -0700, David Bellows wrote:
> > 've noticed that Cmake
> doesn't actually start from scratch when you do a new build. It
> may use decisions it made previously.  Try a fresh build directory.
> 
> Yeah, I couldn't figure out how to "make clean" anyway, so I was using
> new build directories each time.
> 
> So oh well, I'm sure something'll come up eventually.
> 
> Thanks for your help!
> 
> On Sat, Aug 29, 2020 at 2:08 PM Pete Goodeve <pete.goodeve@computer.org> wrote:
> >
> > On Sat, Aug 29, 2020 at 12:51:41PM -0700, David Bellows wrote:
> > > Hi Pete,
> > >
> > > > Use 'csound -z' to see if the opcode is actually there.
> > > I suspect not.
> > >
> > > You are correct, it's not there.
> > >
> > > > It won't get built if you don't have the lame develop kit.  apt-get should
> > > solve that.
> > >
> > > Ok, I installed both libtwolame-dev and libmp3lame-dev and it's still
> > > not working with the same error message.
> > >
> > > I notice that when running cmake ../csound I get the following:
> > > searching for lame.h
> > > not found
> > >
> > > Running "locate lame.h" gets the following:
> > > /usr/include/twolame.h
> > > /usr/include/lame/lame.h
> > >
> > > So I'm not sure what's going on.
> > >
> > > Thanks for your help on this.
> > >
> > I think this is about where any expertise I might have, ends... (:-))
> > I think John is right, though, that 'twolame' is irrelevant.
> > 'libmp3lame' is what you want, I think.  (I never got as far as
> > building 6.14 on Linux, yet.)
> >
> > As a guess on why it's not working for you, I've noticed that Cmake
> > doesn't actually start from scratch when you do a new build. It
> > may use decisions it made previously.  Try a fresh build directory.
> >
> > Goo0d luck!
> >
> >         -- Pete --
> >
> > Csound mailing list
> > Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> > Send bugs reports to
> >         https://github.com/csound/csound/issues
> > Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here