lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUB on kainhofer: still cross/gcc


From: Graham Percival
Subject: Re: GUB on kainhofer: still cross/gcc
Date: Tue, 2 Jun 2009 03:05:56 -0700
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Jun 02, 2009 at 09:12:35AM +0200, Jan Nieuwenhuizen wrote:
> Op zondag 31-05-2009 om 22:49 uur [tijdzone -0700], schreef Graham
> Percival:
> 
> > None of the other places I put -fno-stack-protector had any
> > effect, so I was just trying everything.  :(
> 
> Yeah, I know that mode.  Sometimes it works, but what always
> helps best is to really look what's going on.

I'd say that it's *always* best to stop and try to really
understand things.  It almost always saves time and effort in
the long run.


Anyway, with this patch, the darwin-x86::cross/gcc build
succeedes:

diff --git a/gub/specs/darwin/odcctools.py
b/gub/specs/darwin/odcctools.py
index ee953c0..6f99c49 100644
--- a/gub/specs/darwin/odcctools.py
+++ b/gub/specs/darwin/odcctools.py
@@ -62,3 +62,7 @@ cd %(install_prefix)s%(cross_dir)s/bin && ln
%(toolchain_pref
     def install (self):
         cross.AutoBuild.install (self)
         self.install_librestrict_stat_helpers ()
+    def configure_command (self):
+        return (cross.AutoBuild.configure_command (self)
+                + ' CFLAGS=-D_FORTIFY_SOURCE=0 ')
+


I should figure out if it requires CFLAGS or whether CPPFLAGS
would be ok, and also whether it needs to be in the main odcctools
class, or whether it can be in a subclass (as you were proposing).

Anything else for the proper handling of this item?  (I may report
another build failure in a few hours; it's building
darxin-x86::lilypond now, and after taht I'll try the complete
lilypond build)

Cheers,
- Graham




reply via email to

[Prev in Thread] Current Thread [Next in Thread]