CFLAGS/CPPFLAGS/LDFLAGS

Nathan Owens

unread,

May 13, 2013, 10:00:01 PM5/13/13

to

I get W-dpkg-buildflags-missing|CPPFLAGS 25 (of 25), CFLAGS 25 (of 25),
LDFLAGS 25 (of 25) missing|
when I do blhc --build and I was wondering how to get the CPPFLAG. I
tried overriding auto build and do make CFLAGS+=$(shell dpkg-buildflags
--get CFLAGS) and same with CPPFLAGS but it still doesn't work.

I tried also just setting CFLAGS and CPPFLAGS in debian/rules but it
gives no results

--
To UNSUBSCRIBE, email to debian-ment...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/51915333...@gmx.us

Paul Wise

unread,

May 13, 2013, 10:20:02 PM5/13/13

to

Please show us your debian/rules file and a full build log with
DH_VERBOSE=1 set.

--
bye,
pabs

http://wiki.debian.org/PaulWise

--
To UNSUBSCRIBE, email to debian-ment...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/CAKTje6FxOJu5bcr71cuOQ3BT...@mail.gmail.com

Andrey Rahmatullin

unread,

May 14, 2013, 1:20:02 AM5/14/13

to

On Mon, May 13, 2013 at 08:55:15PM +0000, Nathan Owens wrote:
> when I do blhc --build and I was wondering how to get the CPPFLAG.
> I tried overriding auto build and do make CFLAGS+=$(shell
> dpkg-buildflags --get CFLAGS) and same with CPPFLAGS but it still

^^^^^^
CPPFLAGS

--
WBR, wRAR

signature.asc

Peter Pentchev

unread,

May 14, 2013, 8:30:03 AM5/14/13

to

...well, he did write "and same with CPPFLAGS" :) Or maybe you meant
something else (see below).

Nathan, I believe that what Andrey may have meant is that there are some
upstream packages that simply pay no attention to the CPPFLAGS
environment variable - just as there are some that do not pay any
attention to CFLAGS and LDFLAGS, either. In this case, if it turns out
that your package is one of those, you basically have two options:
- patch the package's build system so that it honors CPPFLAGS
- do what Andrey said: in the debian/rules file, add the contents of
CPPFLAGS to the CFLAGS variable that the package supposedly already
honors

In both cases, write to the upstream authors and ask them to honor
CPPFLAGS, too.

But, as somebody else wrote, we'll need to see a build log and a copy of
your debian/rules file before that. Actually, it might be good to see
upstream's build files (Makefile, CMakeLists.txt, etc), too, just to
make sure that they do (or don't) pay attention to CPPFLAGS at all.

G'luck,
Peter

--
Peter Pentchev ro...@ringlet.net ro...@FreeBSD.org p.pe...@storpool.com
PGP key: http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
This sentence is false.

signature.asc

Nathan Owens

unread,

May 16, 2013, 10:20:02 PM5/16/13

to

On 05/14/2013 02:54 AM, Nathan Owens wrote:

> I have attached the two files. the config.mk file contains the flags.
> I did make a patch for config.mk and got it down to the CPPFLAGS(3),
> CFLAGS(3), and LDFLAGS(3) warning.
I also have attached the build log. I also have tried putting the
CPPFLAGS/CFLAGS/LDFLAGS in the rules file with the buildflags as well
and still no change

dwb_20130503hg-2_amd64.build

Andrey Rahmatullin

unread,

May 17, 2013, 1:10:01 AM5/17/13

to

On Thu, May 16, 2013 at 09:06:19PM -0500, Nathan Owens wrote:
> make[1]: Entering directory `/tmp/buildd/dwb-20130503hg'
> Build options:
> CC = cc
> CFLAGS = -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Werror=format-security -pipe --ansi -std=c99 -D_POSIX_SOURCE -O2 -g -D_BSD_SOURCE -D_NETBSD_SOURCE -pthread -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/p11-kit-1 -I/usr/include/webkitgtk-3.0 -DWITH_LIBSOUP_2_38=1 -DHAS_EXECINFO
> LDFLAGS = -Wl,-z,relro -Wl,--as-needed -lwebkitgtk-3.0 -lgtk-3 -lsoup-2.4 -lgdk-3 -latk-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo-gobject -lpango-1.0 -lcairo -lgio-2.0 -lgobject-2.0 -ljavascriptcoregtk-3.0 -lglib-2.0 -lgnutls -lpthread
> CPPFLAGS = -D_FORTIFY_SOURCE=2 -DGTK_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGSEAL_ENABLE
> cc convert_transport_security.c
Impossible to know what is happening here. You need to find a way to
display full compiler/linker commands first.

--
WBR, wRAR

signature.asc