Date: Sun, 21 Sep 2003 16:55:20 +0200 From: Harald Schmalzbauer <h@schmalzbauer.de> To: "Scot W. Hetzel" <hetzelsw@westbend.net> Cc: Dan Naumov <dan.naumov@ofw.fi> Subject: Re: Getting -pthread support back into local source tree Message-ID: <3F6DBBD8.8050203@schmalzbauer.de> In-Reply-To: <003201c37fd6$e2e0fb70$13fd2fd8@Admin02> References: <1064101768.13585.4.camel@localhost.localdomain> <003201c37fd6$e2e0fb70$13fd2fd8@Admin02>
next in thread | previous in thread | raw e-mail | index | archive | help
Scot W. Hetzel wrote:
> From: "Dan Naumov" <dan.naumov@ofw.fi>
>
>>Seeing as -pthread support has been removed from -CURRENT breaking
>>_LOTS_ of ports, is it possible to "get it back" into a local source
>>tree ? If so, how ? Thanks in advance.
>>
>
> All you need to do is add:
>
> CONFIGURE_ENV+= PTHREAD_LIBS=${PTHREAD_LIBS} \
> PTHREAD_CFLAGS=${PTHREAD_CFLAGS}
>
> To the port that is broken by having -pthread support removed, then compile
> the port.
>
> If it still fails to compile, then you'll need to add a sed command to the
> port that replaces -pthread with ${PTHREAD_LIBS} and -DTHREAD_SAFE with
> ${PTHREAD_LIBS} in the configure script or the Makefiles.
Well, that'd fit my skills, but what is for example with the jdk13? I
have no idea how to fix this one.
Thanks,
-Harry
>
> After you have it working, send-pr your patch to gnats and the port
> maintainer. This is the only way to get these problems fixed, if the port
> maintainer doesn't have time to fix the port to work on -CURRENT.
>
> Scot
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F6DBBD8.8050203>