Jean-Frederic,

Hmmm....  I used this construction instead of `basename $(PWD)`
so that Unix implementations that do not have basename(1) or
dirname(1) do not have to mess with writing one for sake of
compatibility.

In the two intevening days here, have you been able to find out
what the problem was?  (I have used this construction on quite a
number of Unix system Makefile implementations for this same
reason and have never had a problem.  Did I miss something here?)

Dan Lydick

-----Original Message-----
From: Jean-frederic Clere <[EMAIL PROTECTED]>
Sent: Oct 29, 2005 3:50 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [BootJVM] configure

[EMAIL PROTECTED] wrote:

>Jean-Frederic,
>
>The _first_ thin to do is:
>
>  $ svn update
>  $ rm -rf ./config
>  $ ./config.sh
>
>You will notice some changes, per harmony-commits@
>list. 
>
The gmake complains about:
DIRNAME:=$(shell expr $(PWD) : '\(.*[^/]\)/*$' : '.*/\(..*\)')

> After doing SVN update, removing the existing
>configuration and starting _completely_ over will show
>you where I have changed things.  The other thing
>you could do would be,
>
>  $ mv ./config ./config.save
>  $ ./config.sh
>  $ diff ./config.save ./config
>
>This would show you what changed in the SVN update
>in the results it produces.
>
>
>Dan Lydick
>
>
>-----Original Message-----
>From: Jean-frederic Clere <[EMAIL PROTECTED]>
>Sent: Oct 28, 2005 4:55 PM
>To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Subject: Re: [BootJVM] configure
>
>[EMAIL PROTECTED] wrote:
>
>  
>
>>Jean-Frederic,
>>
>>Take a look at the new Makefiles in the top
>>level directory and each source directory.
>>These should provide all functionality that
>>I see for the time being with the exception
>>of distribution rules, whose requirements
>>may change over time.  Notice that one
>>important requirement is to be able to run
>>the documentation compiler 'doxygen',
>>which requires an explicit list of files.  The
>>current 'config.sh' provides these to both
>>the Makefiles and Doxygen (via 'bootjvm.dox')
>>as include files.
>> 
>>
>>    
>>
>+++
>[EMAIL PROTECTED]:~/harmony/enhanced/trunk/sandbox/contribs/bootjvm/bootJVM> 
>make
>/bin/sh: -c: line 1: unexpected EOF while looking for matching `''
>/bin/sh: -c: line 2: syntax error: unexpected end of file
>MakeSetup:98: config/config_build_steps.mak: No such file or directory
>Makefile:163: config/config_dox_setup.mak: No such file or directory
>make: *** No rule to make target `config/config_dox_setup.mak'.  Stop.
>+++
>Ok: I see that configure have to create config/config_build_steps.mak 
>and config/config_dox_setup.mak
>"/bin/sh: -c: line 1/2" strange.
>
>  
>
>>I'll take a look at your configuration proposal
>>soon.
>> 
>>
>>    
>>
>Great-
>
>  
>
>>Dan Lydick
>>
>>
>>-----Original Message-----
>>From: Jean-frederic Clere <[EMAIL PROTECTED]>
>>Sent: Oct 28, 2005 4:17 PM
>>To: harmony-dev@incubator.apache.org
>>Subject: Re: [BootJVM] configure
>>
>>Geir Magnusson Jr. wrote:
>>
>> 
>>
>>    
>>
>>>If you wish to contribute this, could you post it to a JIRA?
>>>   
>>>
>>>      
>>>
>>Until I get commit rights ;-)
>>
>>It is now: http://issues.apache.org/jira/browse/HARMONY-10
>>Now I go for the Makefiles or the build.xml.
>>make is more strandard for C project but ant is probably before the 
>>harmony community.
>>
>>Any commit?
>>
>>Cheers
>>
>>Jean-Frederic
>>
>> 
>>    
>>
>...snip...
>
>
>
>
>
>Dan Lydick
>
>  
>





Dan Lydick

Reply via email to