Hrm. That's quite odd.

The workaround is quite easy, but any other J package maintainers for linux
distributions are likely to run into this. Since it seems to have been
introduced recently between d and e, ideally, we could find a way to smooth
over the quirk that breaks neither your nor path-agnostic build systems.

What build setup are you using?

Henry Rich <[email protected]> wrote:
> The funny includes are required on the build system I use.  If you put 
> your source under a /jsource directory you will be able to use the files 
> as is.
> 
> Henry Rich
> 
> On 1/29/2020 11:47 PM, ethiejiesa via Programming wrote:
> > Compilation on linux breaks for me:
> >
> >      ../../../../jsrc/cip.c:6:10: fatal error: ../../jsource/jsrc/j.h: No 
> > such file or directory
> >          6 | #include "../../jsource/jsrc/j.h"
> >            |          ^~~~~~~~~~~~~~~~~~~~~~~~
> >
> > It looks like `jsrc/cip.c' includes paths that back all the way out of the
> > jsource parent directory. This fails because my source tree is extracted to 
> > a
> > directory not named `jsource'.
> >
> > These includes are for files that coexist in `jsrc' alongside `cip.c', so
> > patching out the (unnecessary?) path munging fixes compilation in my case:
> >
> >      --- jsrc/cip.c 2020-01-30 13:31:22.463687182 +0900
> >      +++ jsrc/cip.c 2020-01-30 13:33:47.707458248 +0900
> >      @@ -3,9 +3,9 @@
> >       /*                                                                    
> >      */
> >       /* Conjunctions: Inner Product                                        
> >      */
> >       
> >      -#include "../../jsource/jsrc/j.h"
> >      -#include "../../jsource/jsrc/vasm.h"
> >      -#include "../../jsource/jsrc/gemm.h"
> >      +#include "j.h"
> >      +#include "vasm.h"
> >      +#include "gemm.h"
> >       
> >       #define MAXAROWS 384  // max rows of a that we can process to stay in 
> > L2 cache   a strip is m*CACHEHEIGHT, z strip is m*CACHEWIDTH   this is 
> > wired to 128*3 - check if you chage
> >       
> >      @@ -1057,15 +1057,15 @@
> >        switch(c){
> >         case CPLUSDOT:
> >       #define F |=
> >      -#include "../../jsource/jsrc/cip_t.h"
> >      +#include "cip_t.h"
> >          break;
> >         case CSTARDOT:
> >       #define F &=
> >      -#include "../../jsource/jsrc/cip_t.h"
> >      +#include "cip_t.h"
> >          break;
> >         case CNE:
> >       #define F ^=
> >      -#include "../../jsource/jsrc/cip_t.h"
> >      +#include "cip_t.h"
> >          break;
> >        }
> >        R z;
> >
> > bill lam <[email protected]> wrote:
> >
> >> raspberry and android release-e are available now.
> >>
> >> no release-d, sorry.
> >>
> >> Wed, 29 Jan 2020, Eric Iverson написал(а):
> >>> j901-release-e is available for windows/linux/macos
> >>>
> >>> It has minor bug fixes to the previous release. In case you were curious,
> >>> release-d got lost in the shuffle.
> >>>
> >>> Please upgrade your j901 install when convenient with:
> >>>
> >>> start J
> >>>     load 'pacman'
> >>>     'upgrade' jpkg 'jengine'
> >>>
> >>> ***
> >>> raspberry and android release-e will be announced when available.
> >>> ----------------------------------------------------------------------
> >>> For information about J forums see http://www.jsoftware.com/forums.htm
> >> -- 
> >> regards,
> >> ====================================================
> >> GPG key 1024D/4434BAB3 2008-08-24
> >> gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3
> >> ----------------------------------------------------------------------
> >> For information about J forums see http://www.jsoftware.com/forums.htm
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
> 
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to