From: Bernard Pidoux F6BVP <f6bvp@free.fr>
To: Ray Wells <vk2tv@exemail.com.au>
Cc: Jose Ng Lee <jng@psi.net.pa>, linux-hams@vger.kernel.org
Subject: Re: fbbsrc.704r5 compile error
Date: Fri, 18 Sep 2009 15:17:55 +0200 [thread overview]
Message-ID: <4AB38883.2090805@free.fr> (raw)
In-Reply-To: <4AB2E34E.7070907@exemail.com.au>
Hi Jose,
FBB 704r5 is a pre release.
As such it is experimental in term of program code.
Thus I had to validate a number of debuging options.
However, if needed you can, as suggested remove
-fstack-protector-all
argument in ../src/Makefile
73 de Bernard, f6bvp
Ray Wells a écrit :
> Jose,
>
> Stack protection was added after 2.6.16. I first encountered it
> somewhere after 2.6.18, possibly in 2.6.22 but my memory is dim.
>
> There are advantages in moving to a newer kernel and that will fix your
> current problem, but you'll possibly run into stack smashing with xfbb,
> and it won't run.
>
> Bernard F6BVP is working on the xfbb code to eliminate some problems.
> Some users are having success with Bernard's later releases but on my
> Debian 4.0 system (2.6.28) I still have to compile fbb with
> -fno-stack-protection. I have the same issue on another system running
> Debian 4.0 with kernel 2.6.29-6. Both systems run fbb 7.04s-test.
>
> If you really need to stick with that old kernel you might get away with
> commenting out the -DPROTOTYPES line. That's what I would try, but be
> warned, I'm not a programmer.
>
> Bernard is across this list and may make comment.
>
> Ray vk2tv
>
> Jose Ng Lee wrote:
>> Hi,
>>
>> I am using an old Linux Fedora 4 with kernel 2.6.16.14. On this old
>> machine, a few years ago I compiled OK fbb 7.04l and tried again today
>> and compiles OK for that version.
>>
>> I downloaded the source for fbbsrc.704r5 and tried to compile but got
>> this error:
>>
>> [root@hp2at src]# make
>> gcc -Wall -Wstrict-prototypes -O2 -ggdb2 -funsigned-char -D__LINUX__
>> -Wformat-security -D_FORTIFY_SOURCE=3D2 -DPROTOTYPES -I../include
>> -fstack-check -fstack-protector-all -DUSE_NCURSES -c -o arbre.o arbre.c
>> cc1: error: unrecognized command line option "-fstack-protector-all"
>> make: *** [arbre.o] Error 1
>> [root@hp2at src]#
>>
>> Please, anyone can help me or what I have to change in the Makefile to
>> make it compile OK.
>>
>> Thanks,
>> 73s Jose / HP2AT
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-18 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 0:00 fbbsrc.704r5 compile error Jose Ng Lee
2009-09-18 1:21 ` Dave Platt
2009-09-18 1:33 ` Ray Wells
2009-09-18 13:17 ` Bernard Pidoux F6BVP [this message]
[not found] ` <BC95AC1740034FE796CAA73C11319A31@HOLLYWOOD.HOLLYWOOD.COM>
2009-09-20 10:34 ` Bernard Pidoux F6BVP
2009-09-18 13:38 ` fbbsrc.704r4-5 stack smashing Bernard Pidoux F6BVP
2009-09-18 20:47 ` Ray Wells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AB38883.2090805@free.fr \
--to=f6bvp@free.fr \
--cc=jng@psi.net.pa \
--cc=linux-hams@vger.kernel.org \
--cc=vk2tv@exemail.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox