Re: [Tuxpaint-devel] Per-locale default font
An award-winning drawing program for children of all ages
                
                Brought to you by:
                
                    wkendrick
                    
                
            
            
        
        
        
    | 
     
      
      
      From: Shin-ichi T. <dol...@wm...> - 2023-06-16 09:01:19
      
     
   | 
Hi!
As a workaround on my build environment, I've purged paths containing
spaces and parentheses from the "$PATH" and added paths of symbolic
links from /usr/local/* to actual directories.
It looks O.K. so far.
Thanks.
On Thu, 15 Jun 2023 23:03:20 +0900, Shin-ichi TOYAMA wrote:
>On Tue, 13 Jun 2023 22:20:40 -0700, Bill Kendrick wrote:
>>> By the way, I had to revert the commit "cf94635713b9dc7977af131a6b3ec89cc872d0e1"
>>> to build Tux Paint on Windows from current git repo because of the error as follows.
>>
>>Ah, I wonder if adding quotes would help.  (I get the feeling the "(" in question
>>might be from the "(x86)"?)
>
>Sure, I confirmed that the parentheses and whitespaces in the PATH, which are common
>on Windows, are the evil.
>
>>Does https://sourceforge.net/p/tuxpaint/tuxpaint/ci/7febf719d02e9c78d4554d2388d793726e19b0af/
>>help?
>
>Unfortunately it doesn't.
>
>I confirmed that not using 'eval' causes no error after trial and error aproach, but
>I'm not sure if it is a right way or not.
>
>----------------------------------------------------
>-       @(eval export PATH="$(shell pwd)":"$(PATH)")
>+       @export PATH="$(shell pwd)":"$(PATH)"
>----------------------------------------------------
>
>
>_______________________________________________
>Tuxpaint-devel mailing list
>Tux...@li...
>https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
-- 
Shin-ichi TOYAMA <dol...@wm...>
 |