On 03/07/2020 02:35 PM, Daniel Stenberg wrote:
On Sat, 7 Mar 2020, Ben Greear via curl-library wrote:
21517LDFLAGS: -L/usr/lib
Usually, when -L/usr/lib appears in LDFLAGS, the reason is that some package
that configure picked up has a bad pkg-config that includes that (and
confi
On Sat, 7 Mar 2020, Ben Greear via curl-library wrote:
21517LDFLAGS: -L/usr/lib
Usually, when -L/usr/lib appears in LDFLAGS, the reason is that some package
that configure picked up has a bad pkg-config that includes that (and
config.log can help you figure out which).
I just c
On Sat, Mar 7, 2020 at 4:38 PM Ben Greear via curl-library
wrote:
>
> On older platforms where libcares is old, it seems that my builds are broken
> because the -L/usr/lib comes before the -L that is generated with the
> --with-cares [dir]
> argument:
>
> From config.log:
>
> 21516CPPFLAGS:
Hello,
On older platforms where libcares is old, it seems that my builds are broken
because the -L/usr/lib comes before the -L that is generated with the
--with-cares [dir]
argument:
From config.log:
21516CPPFLAGS:-I/home/greearb/git/btbits/l4libs/c-ares.ct/include
21517LDFLAGS
