From: Jigar S. <so...@gm...> - 2008-12-19 20:59:04
|
Hi list, I'm trying to compile HEAD on an Ubuntu : uname -a Linux Karmeliet 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux It doesnt compile (no options, just a basic ./configure) with the following errors : cc1: warnings being treated as errors policy_token.c: In function '__libipseclex': policy_token.l:167: erreur: ignoring return value of 'fwrite', declared with attribute warn_unused_result I've looked at the Changelog and noone has make made changes in that file since a long time.. So i've asked my favouriste friend Google if he knew this Ubuntu issue and, well, he does : https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/299848/+viewstatus https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/299848 I've tried to compile the 0.7 and had the same result with the same error. Does anyone know anything about that ? :-) Thx. -- SOLANKI Jigar --- |
From: VANHULLEBUS Y. <va...@fr...> - 2008-12-22 10:23:05
|
On Fri, Dec 19, 2008 at 09:58:59PM +0100, Jigar SOLANKI wrote: > Hi list, Hi Jigar. > I'm trying to compile HEAD on an Ubuntu : > [...] > I've tried to compile the 0.7 and had the same result with the same error. > > Does anyone know anything about that ? :-) Mmmhhh.... if you have the same issue with 0.7, looks like your're lacking "something" needed to compile.... As it beaks in parsing stiff, check first if you have bison or something like that. Did you try with a 0.7 checkout from SVN or with 0.7(.1) release tarball ? Yvan. |
From: Jigar S. <so...@gm...> - 2008-12-23 10:03:10
|
> > Hi Jigar. > Hello Vanhu, :-) if you have the same issue with 0.7, looks like your're lacking > "something" needed to compile.... > If I lack something, ./configur'ing should tell it to me and abort, right ? > > As it beaks in parsing stiff, check first if you have bison or > something like that. > Yep, all stuff related to parsing, such as bison, yacc and flex is correctly installed and configured well. > > Did you try with a 0.7 checkout from SVN or with 0.7(.1) release > tarball ? > SVN checkout :-) I'll try it with the tarball. Thx. -- SOLANKI Jigar -- Windows make some noise, Linux play music, BSD really rocks ! -- --- PS : félicitations pour ta nouvelle tchu-tchu :) |
From: Jigar S. <so...@gm...> - 2008-12-23 10:03:40
|
> > I'll try it with the tarball. > Tried to compile with the tarball (0.7.1) and had the same result with the same compile error. It's weird because according to the Ubuntu bug report, this bug is just present on Ubuntu Intrepid Ibex version (8.10) (version that I run), and I can confirm it, at less on Ubuntu Hardy Heron (8.04) and Gusty Gibbon (7.10) on wich all ipsec-tools versions compile well. -- SOLANKI Jigar -- Windows makes some noise, Linux plays music, BSD really rocks ! -- --- |
From: Timo T. <tim...@ik...> - 2008-12-23 13:11:27
|
Jigar SOLANKI wrote: > I'll try it with the tarball. > > Tried to compile with the tarball (0.7.1) and had the same result with > the same compile error. > > > It's weird because according to the Ubuntu bug report, this bug is just > present on Ubuntu Intrepid Ibex version (8.10) (version that I run), and > I can confirm it, at less on Ubuntu Hardy Heron (8.04) and Gusty Gibbon > (7.10) on wich all ipsec-tools versions compile well. I think the bug report you referred to is about different problem that is related to bison/yacc/flex. In your case, it looks like the flex generated C code is incompatible with the C-library you are using (it has string fwrite prototype, where as the generated code is not so strict). - Timo |
From: Timo T. <tim...@ik...> - 2008-12-23 13:16:18
|
Timo Teräs wrote: > Jigar SOLANKI wrote: >> I'll try it with the tarball. >> >> Tried to compile with the tarball (0.7.1) and had the same result with >> the same compile error. >> >> >> It's weird because according to the Ubuntu bug report, this bug is just >> present on Ubuntu Intrepid Ibex version (8.10) (version that I run), and >> I can confirm it, at less on Ubuntu Hardy Heron (8.04) and Gusty Gibbon >> (7.10) on wich all ipsec-tools versions compile well. > > I think the bug report you referred to is about different problem that > is related to bison/yacc/flex. > > In your case, it looks like the flex generated C code is incompatible > with the C-library you are using (it has string fwrite prototype, where > as the generated code is not so strict). Actually, I just upgraded from Hardy Heron to Intrepid and now I have to same problem as you. I'm on it. - Timo |
From: Timo T. <tim...@ik...> - 2008-12-23 13:43:53
|
Timo Teräs wrote: > Timo Teräs wrote: >> Jigar SOLANKI wrote: >>> I'll try it with the tarball. >>> >>> Tried to compile with the tarball (0.7.1) and had the same result with >>> the same compile error. > > Actually, I just upgraded from Hardy Heron to Intrepid and now I have > to same problem as you. I'm on it. And it seems to be flex bug. It generates code that is not properly checked when _FORTIFY_SOURCE=2 is defined (and it's defined by default on Ubuntu). See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388438 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505233 Install a new flex from upcoming Ubunty Jaunty. Or alternatively you can disable FORTIFY_SOURCE. You can do that by running configure like: CFLAGS="-D_FORTIFY_SOURCE=1" ./configure <normal-configure-arguments> - Timo |