CYGWIN_DIR, LINUX_DIR and KERNELCONFIG in all.sh

[Steve Papacharalambous]

Hi Robert,

You're right, there is a potential problem in all.sh when building 
cygwin targets with KERNELCONFIG.  :-(

I've attached a patch to all.sh which should prevent this problem from 
occuring,

Best regards,

Steve

Daniel Kegel wrote:
> Daniel Kegel wrote:
> 
>> Robert P. J. Day wrote:
>>
>>>   a short question about some logic in all.sh.  if you're building a
>>> CYGWIN target, then obviously you don't need to set LINUX_DIR, which
>>> would normally mean that there's no associated need to set
>>> KERNELCONFIG either, right?
>>>
>>>   however, even if you're building a CYGWIN target, the value of
>>> KERNELCONFIG will still be tested, which seems kind of redundant.  in
>>> fact, if KERNELCONFIG refers to an unreadable file, the script will
>>> abort, even though CYGWIN really doesn't need this variable at all.
>>
>>
>>
>> The cygwin support is new, and may need a bit of polish, so
>> this kind of issue is not surprising.  Feel free to submit a
>> patch to fix it.
> 
> 
> If you do, please avoid wholesale reformatting or rewriting,
> and make the patch as small as possible.
> - Dan
> 
> ------
> Want more information?  See the CrossGCC FAQ, 
> http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
> 
> 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: all.sh.patch
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20041110/4b9cfbd5/attachment.ksh>
-------------- next part --------------
------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com