Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can't make a new build during trying to update rtree branch

Open
#236 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, sqlite, wasm

Research direction

Start by comparing the rtree branch with master and inspecting the Makefile, then reproduce the reported make failure with the Emscripten setup described in the issue. Verify that the build enables SQLITE_ENABLE_RTREE and produces a current build usable by the Geopackage JS library.

Written by the indexing model from the issue text.

Description

Hi guys!

Recently I found out, that sql.js has a branch with R-Tree module support. Unfortunately it's quite outdated, so I'm not able to use it with the current Geopackage JS library. According to this issue #59 it needs actually just to add -DSQLITE_ENABLE_RTREE=1 to the make file on master and create a new build.
But when I run make command, I receive this errors:

incorrect target triple 'le32-unknown-nacl' (did you use emcc/em++ on all source files and not clang directly?) LLVM ERROR: Invalid SIMD cast between items of different bit sizes!

I installed emscripten as it described here and here because it looks like the problem described in this FAQ.
But unfortunately it doesn't work.

Could you please help me to solve this issue? Or maybe it would be possible to update rtree branch to the master state, so I can easy include it into a package config? I guess it would be the best solution in my case.

Looking forward to your reply

Dominant language
JavaScript
Stars
13.7k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sql-js/sql.js

All issues in sql-js/sql.js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.