chicken-janitors
[Top][All Lists]
Advanced

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

[Chicken-janitors] Re: [Chicken-bugs] #312: apply-hack detection broken


From: Chicken Scheme
Subject: [Chicken-janitors] Re: [Chicken-bugs] #312: apply-hack detection broken
Date: Mon, 03 Sep 2007 20:04:15 -0000

#312: apply-hack detection broken
-----------------------+----------------------------------------------------
Reporter:  sjamaan     |        Owner:  felix       
    Type:  defect      |       Status:  assigned    
Priority:  critical    |    Component:  build system
 Version:  2.6         |   Resolution:              
Keywords:  apply-hack  |  
-----------------------+----------------------------------------------------
Comment (by sjamaan):

 Putting

 {{foo:
         echo "arch = ${ARCH}"}}


 just below {{ifdef ARCH}} in {{defaults.make}} prints:
 {{echo "arch ="
 arch =}}

 to the console. Sounds like the documentation lied!  You can test it for
 yourself by simply removing your arch's name from the {{case}} statement
 in {{config-guess.sh}}.

 From [http://www.chemie.fu-berlin.de/chemnet/use/info/make/make_7.html]:

 {{If the variable variable-name has a non-empty value, the text-if-true is
 effective; otherwise, the text-if-false, if any, is effective. Variables
 that have never been defined have an empty value. Note that ifdef only
 tests whether a variable has a value. It does not expand the variable to
 see if that value is nonempty. Consequently, tests using ifdef return true
 for all definitions except those like foo =. To test for an empty value,
 use ifeq ($(foo),).}}

 That last sentence seems to indicate that changing the check to {{ifneq
 ($(foo),)}} should do the trick.  It seems to work for me.  Can you
 verify?

-- 
Ticket URL: <http://trac.callcc.org/ticket/312#comment:4>
Chicken Scheme <http://www.call-with-current-continuation.org/>
The CHICKEN Scheme-to-C compiler

reply via email to

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