pcp
[Top] [All Lists]

Re: [pcp] pcp updates - #shell for pmcpp, gentoo fixes

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pcp updates - #shell for pmcpp, gentoo fixes
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 13 Aug 2015 04:45:19 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <55CC494A.1000000@xxxxxxxxxxxxxxxx>
References: <55CB2A34.2040903@xxxxxxxxxxxxxxxx> <127430246.9646957.1439430874257.JavaMail.zimbra@xxxxxxxxxx> <55CC494A.1000000@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: kVMcJIakBPmZqYOcvn/E1hZjsLf18A==
Thread-topic: pcp updates - #shell for pmcpp, gentoo fixes

----- Original Message -----
> >> [...]
> >>        configure.ac: make sure some optional gcc flags make it into the
> >>        build
> > 
> > This one seems to have broken the Windows build:
> > http://buildbot.pcp.io/builders/fedora-mingw64/builds/3/steps/shell/logs/stdio
> 
> Could be the configure.ac change, the others are not implicated.

Yep, definitely a new CFLAGS setting getting through that wasn't before.

> [...]
> pulling this apart ....
> 
> -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> --param=ssp-buffer-size=4 ... no clue where this comes from
> 
> -fno-strict-aliasing ... initial CFLAGS setting in configure for target_os =
> mingw?
> 
> -fstack-protector-all -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 ... from
> configure in the place I made a change

The (linker) errors look related to stack checking, so I'm guessing its
one of the above lines, probably -fstack-protector-all?

The key failure message is this one... (repeats)
src/libpcp/src/connect.c:269: undefined reference to `__stack_chk_fail'

> and the rest is sort of expected
> 
> or here?

(these ones are pre-existing compiler warnings, things still needing a
bit more attention to clean up - but not causing build failure)

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>