cURL / Mailing Lists / curl-library / Single Mail


Re: possible problem with curl-config

From: Dan Fandrich <>
Date: Mon, 25 Feb 2013 21:34:22 +0100

On Mon, Feb 25, 2013 at 11:23:56AM -0500, Dennis Clarke wrote:
> sure enough I check curl-config :
> $ which curl-config
> /usr/local/bin/curl-config
> $ curl-config --cflags
> -I/usr/local/include
> $ curl-config --configure
> '--enable-shared' '--enable-static' '--with-libidn=/usr/local' '--enable-tls-srp' '--with-ssl' 'CC=/opt/solarisstudio12.3/bin/cc' 'CFLAGS=-errfmt=error -erroff=%none -errshort=full -xstrconst -xildoff -m64 -xmemalign=8s -xnolibmil -Xa -xcode=pic32 -xregs=no%appl -xlibmieee -mc -g -xs -ftrap=%none -Qy -xbuiltin=%none -xdebugformat=dwarf -xunroll=1 -xtarget=ultraT2 -xcache=8/16/4:4096/64/16' 'CPPFLAGS=-I/usr/local/include -I/usr/local/ssl/include -I/opt/mysql/mysql/include -D_TS_ERRNO -D_POSIX_PTHREAD_SEMANTICS -D_LARGEFILE64_SOURCE'
> Not sure what curl-config --cflags should return but the script does not look to reply with cflags at all :

curl-config --cflags should return the compiler flags necessary to compile a
libcurl-using application with libcurl. If libcurl were installed in
/usr/local, it's quite possible that -I/usr/local/include is the only compiler
flag that would be needed. Note also that libcurl vendors often modify
curl-config from what is generated by the normal curl-supplied build tools.
Sometimes that is necessary, but sometimes they mess it up.

> Should curl-config --cflags not reply with the actual CFLAGS ?

You can put the curl-config --cflags output into a variable called CFLAGS if
you want, and that is often how it is done in a makefile, e.g.

CFLAGS=$(shell curl-config --cflags)
   $(CC) $(CFLAGS) -c -o $@ $<

>>> Dan
List admin:
Received on 2013-02-25