Re: [Mingw-w64-public] two winpthreads build machinery issues

[NightStrike <nig...@gm...>]

On Tue, Aug 16, 2011 at 10:17 AM, Ruben Van Boxem
<van...@gm...> wrote:
> Op 16 aug. 2011 16:13 schreef "JonY" <jo...@us...> het
> volgende:
>
>>
>> On 8/16/2011 20:57, Ruben Van Boxem wrote:
>> > Hi,
>> >
>> > Since Kai fixed the winpthreads/libgomp problem (Kai, you are a
>> > hero!), I have been trying to finalize the winpthreads build stuff in
>> > my scripts and testing, which lead to two issues:
>> >
>> > 1. I can't link to winpthreads statically, better said, if I compile
>> > the small openmp test program with the added -static option, I get
>> > undefined references to pthreads functions. When I check the size of
>> > the static libpthread.a, it's smaller than the DLL import lib, which
>> > is not right. I think the autotools stuff is missing something here.
>> >
>>
>> Check if adding -lpthread works, If so check your openmp specs file, I
>> can't remember what its called, it probably did something weird for the
>> static case.
>>
>> > 2. In order to get the DLL installed into <sysroot>/bin where it
>> > belongs (for non-multilib setups), I passed the --bindir=<sysroot>/bin
>> > option to configure, but the dll was still placed in prefix/bin
>> > instead. I can move it over myself, but autotools can do this, so it
>> > really should be fixed there.
>> >
>> > Thanks!
>>
>> Yes, you can do that, but I'm trying to figure out how to fixup the
>> install dir without breaking cross builds.
>>
>> if build==host, then append ../../bin to bindir, hmmm.
>
> Just fix the autotools --bindir option, so one can decide for oneself if
> it's needed/wanted. It's a custom step that may not be wanted everywhere you
> build winpthreads in that configuration.

Change autoconf?