[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Unable to build a BEAGLEBOARD kernel
On Mon, 17 Sep 2012 12:13:33 -0400, Thor Lancelot Simon wrote:
> On Mon, Sep 17, 2012 at 08:01:19AM -0700, Matt Thomas wrote:
>> There is no way to allocate things at this stage. If SSP can't deal
>> with standard C99 usages, then SSP is broken.
> Well, it's not clear how it would protect such a function, since the
> bounds of the stack can't be known a priori -- can they?
I think Thor is right here.
> The file containing this function, if it must work this way, could be
> built with -Wno-stack-protector, I suppose.
With the following change, I am able to compile an evbarm BEAGLEBOARD-
based kernel again indeed:
RCS file: /cvsroot/src/sys/arch/evbarm/conf/Makefile.evbarm.inc,v
retrieving revision 1.22
diff -p -u -r1.22 Makefile.evbarm.inc
--- Makefile.evbarm.inc 16 Feb 2012 08:08:25 -0000 1.22
+++ Makefile.evbarm.inc 4 Oct 2012 01:31:58 -0000
@@ -1,5 +1,8 @@
# $NetBSD: Makefile.evbarm.inc,v 1.22 2012/02/16 08:08:25 matt Exp $
# If this is a install kernel and the ramdisk image exists in the object
# tree, insert it into the kernel *before* we make the u-boot images.
Can I commit it?
Main Index |
Thread Index |