Re: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Richard Levitte
On Tue, 08 Oct 2019 18:53:37 +0200, Dan Heinz wrote: > > Another question is why I now need to link pthreads when I did not > in the 1.0.2 version? I've added no-threads to the configuration, > but I'm curious why I didn't need to previously link it. And I'd > prefer not to change too many confi

RE: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Dan Heinz
> > > >The no-dso is silently not valid in 1.1.1c. That option didn't work > > > >right, so it was unusable in practice anyway. However, someone recently > > > >fixed that up, unfortunately after the last 1.1.1 release. > > > >The specific patch may be possible to find on github (unless that br

Re: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Richard Levitte
On Tue, 08 Oct 2019 14:59:23 +0200, Richard Levitte wrote: > > On Mon, 07 Oct 2019 21:55:50 +0200, > Dan Heinz wrote: > > > > >The no-dso is silently not valid in 1.1.1c. That option didn't work > > >right, so it was unusable in practice anyway. However, someone recently > > >fixed that up, u

Re: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-08 Thread Richard Levitte
On Mon, 07 Oct 2019 21:55:50 +0200, Dan Heinz wrote: > > >The no-dso is silently not valid in 1.1.1c. That option didn't work right, > >so it was unusable in practice anyway. However, someone recently fixed that > >up, unfortunately after the last 1.1.1 release. > >The specific patch may be po

RE: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-07 Thread Dan Heinz
>The no-dso is silently not valid in 1.1.1c. That option didn't work right, so >it was unusable in practice anyway. However, someone recently fixed that up, >unfortunately after the last 1.1.1 release. >The specific patch may be possible to find on github (unless that branch has >been deleted)

Re: Linux linking issues moving from 1.0.2t to 1.1.1c

2019-10-07 Thread Richard Levitte
The no-dso is silently not valid in 1.1.1c. That option didn't work right, so it was unusable in practice anyway. However, someone recently fixed that up, unfortunately after the last 1.1.1 release. The specific patch may be possible to find on github (unless that branch has been deleted), otherw