Date: Sat, 23 Dec 2000 01:13:05 -0500 From: Will Andrews <will@physics.purdue.edu> To: Anarcat <beaupran@IRO.UMontreal.CA> Cc: will@physics.purdue.edu, freebsd-ports@FreeBSD.ORG Subject: Re: Porting ecasound suite to FreeBSD Message-ID: <20001223011305.U328@argon.firepipe.net> In-Reply-To: <874rzwidpz.wl@localhost.anarcat.yi.org>; from beaupran@IRO.UMontreal.CA on Fri, Dec 22, 2000 at 12:10:32PM -0500 References: <87puilbdwu.wl@localhost.anarcat.yi.org> <20001221224539.J328@argon.firepipe.net> <874rzwidpz.wl@localhost.anarcat.yi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 22, 2000 at 12:10:32PM -0500, Anarcat wrote:
> Humm.. I agree. But FreeBSD way is kinda strange. Why doesn't it use
> the '-lpthread' syntax? Autoconf has "problems" detecting libs that
> are not link with -l<libname>. Actually, it's more a problem of not
> having the good macro available..
I don't really know why it does it that way. You'll have to ask Jason
Evans, the pthread (libc_r) maintainer. I've never really understood
why pthread was put in a library called "c_r" instead of "pthread",
among a few other things.
> But I fixed the scripts. Unfortunatly, since my fixes go back to
> ecasound's main source it has to be in LICQ's style:
>
> case "$host" ...
> freebsd)
> CFLAGS...
>
> This is annoying. Is there a better way?
perl -pi -e "s@-lpthread@-pthread@g" ${WRKSRC}/configure
in your port Makefile. Sure, it's a hack, but it works (usually). The
configure script should have the necessary autoconf hooks to check for
-pthread on FreeBSD.. some projects already have this sort of thing.
> I know it's there. The problem occurs upon link.
It would be nice to see the exact error.
> Also, there's no mlockall man page. Is there a reason (e.g. "secret
> function" :)?
There are plenty of undocumented function calls in FreeBSD, just like
any other operating system.
> Well-well-well.. It seems you're right! I have no idea how their
> libtool stuff works, in fact, I know *nothing* about libtool. One
> thing I know though... libtool is installed on my system
> (/usr/local/bin/libtool) and the makefiles are usings the package's
> libtool! And this one adds annoying -lc and -lc_r libs!
>
> Fixed.
Yeah, libtool is pretty stupid when it comes to FreeBSD. Thankfully,
this problem is not usually caused by libtool. Sometimes it is,
usually not.
> Ah-ah! I knew there was something I was missing. This is the first
> "major" port I do (pthreads, libtool, messy dependencies...), so I
> knew I was missing some stuff.
Quite an experience, isn't it?
> Thanks a lot for your help, you can expect a port to pop up in PRs
> soon enough. :)
Sure.
--
wca
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001223011305.U328>