Re: [sqlite] Minor bug reports during build.

[Rowan Worth]

On 22 December 2017 at 23:57, Michael Tiernan 
wrote:

>
> >  It just doesn’t install to a directory it can’t write to, because you
> > told it to install system-level things.
>
> Not going to hash it out here but I didn't tell it to install system-level
> things, I told it to compile and install everything locally. Just like I do
> with lots of other source packages especially when I'm not very familiar
> with the software and wish to make sure of what I'm doing before committing
> it to the system.
>

How is the build system supposed to differentiate "local" vs "system-level"?

It's obvious from your perspective, but --prefix does not clearly
disambiguate between the two; it's also used for system-level builds. Eg.
--prefix=/opt or --prefix=/usr (for package maintainers).

AFAIK there's no standard way to tell configure to avoid touching any
system-level dirs. If you want to know what an unfamiliar package is going
to do before the fact your best bet is `make -n install`, or `make
DESTDIR=/tmp/foo install` if the package supports staged installs (sqlite
does, probably most autoconf projects do).


The tests rely on tcl, but they run here without installing the tcl
extension so not sure what's going wrong in your situation. They run on a
DB in the current directory, so maybe related to you running under a
dropbox vfs (which I don't know if implements properly locking?).


Dunno about OSX either; do you have tcl installed there?
-Rowan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Michael Tiernan]

On Fri, Dec 22, 2017 at 10:26 AM, Warren Young  wrote:

> On Dec 22, 2017, at 7:07 AM, Michael Tiernan 
> wrote:
> >
> > "Working as advertised" Okay, that's just funny. That it doesn't build is
> > correct?
>
> It does build.


Okay, it does build the binaries. Valid point.

  It just doesn’t install to a directory it can’t write to, because you
> told it to install system-level things.



Not going to hash it out here but I didn't tell it to install system-level
things, I told it to compile and install everything locally. Just like I do
with lots of other source packages especially when I'm not very familiar
with the software and wish to make sure of what I'm doing before committing
it to the system.



> > Just as an FYI, it builds correctly on MacOSX and doesn't complain about
> > things it can't control.
> I’m guessing you’re using Homebrew,


Nope, not at all. It doesn't seem to try and touch the things it has no
right to touch.

-- 
<< MCT >>   Michael C Tiernan.http://www.linkedin.com/in/mtiernan

Non Impediti Ratione Cogatationis
Women and cats will do as they please, and
men and dogs should relax and get used to the idea. -Robert A. Heinlein
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Warren Young]

On Dec 22, 2017, at 7:07 AM, Michael Tiernan  wrote:
> 
> "Working as advertised" Okay, that's just funny. That it doesn't build is
> correct?

It does build.  It just doesn’t install to a directory it can’t write to, 
because you told it to install system-level things.  Rowan also gave you the 
solution, forcing installation of Tcl extension to other than the default you 
implicitly selected by not overriding the default.

> Just as an FYI, it builds correctly on MacOSX and doesn't complain about
> things it can't control.

I’m guessing you’re using Homebrew, which gives your normal user all rights to 
/usr/local, which is atypical for POSIX machines.  In fact on macOS’s closest 
cousin, FreeBSD, giving that level of access to /usr/local would be a major 
security problem.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Michael Tiernan]

"Working as advertised" Okay, that's just funny. That it doesn't build is
correct?

Also, despite the "disable-tcl" flag, the tests all fail because of
something involving tcl. Don't think I read that in the advertisement.

Just as an FYI, it builds correctly on MacOSX and doesn't complain about
things it can't control.
-- 
<< MCT >>   Michael C Tiernan.http://www.linkedin.com/in/mtiernan

Non Impediti Ratione Cogatationis
Women and cats will do as they please, and
men and dogs should relax and get used to the idea. -Robert A. Heinlein


On Dec 21, 2017 10:36 PM, "Rowan Worth"  wrote:

Seems to be working as advertised.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Rowan Worth]

Seems to be working as advertised. Unless you specify --disable-tcl, the
configure script defaults to building an sqlite extension for TCL.

The extension can't go in $PREFIX, since tcl wouldn't be able to find it.
So your options for a non-root install are:

1) --disable-tcl
2) set the environment variable TCLLIBDIR to somewhere you have write
access (presumably you'll also need to configure tcl to look here for
extensions)
3) install your own tcl to $PREFIX and make sure its tclsh is the first one
in your $PATH

-Rowan

On 22 December 2017 at 03:41, Michael Tiernan 
wrote:

> Sorry for the top post. Sadly the android client forces it.
>
> In short, I'm building two copies of sqlite3, one of which works fine, the
> attempt to build it on the Linux host (using the prefix flag of course)
> causes the build to begin but it to fail when it runs into the attempt at
> modifying the (non-existent) file /usr/share/tcl8.5/sqlite3
>
> All the other warnings and considerations are secondary to the point that
> the makefile is attempting to change the permissions on an external (to the
> user) tool which it neither built or should be able to modify.
>
> Thanks for everyone's time!
> --
> << MCT >>   Michael C Tiernan.http://www.linkedin.com/in/mtiernan
>
> Non Impediti Ratione Cogatationis
> Women and cats will do as they please, and
> men and dogs should relax and get used to the idea. -Robert A. Heinlein
>
> On Dec 21, 2017 2:26 PM, "Warren Young"  wrote:
>
> On Dec 21, 2017, at 11:37 AM, Michael Tiernan 
> wrote:
> >
> > I'm trying to build two copes of sqlite3 in a shared dropbox folder.
>
> Do you intend to use SQLite inside the Dropbox folder once you’ve got it
> working?  That’s only safe if only one person is using the database at a
> time, and you wait for the sync to finish before trying to use the DB on
> another machine.
>
> If you need a networked DBMS, SQLite is generally not what you want, at
> least not as-stock.  There are add-ons and alternatives that work far
> better for this.  Google “SQLite Dropbox”.  It’s come up many times before.
>
> > On a "Scientific Linux 6.7" (RHEL 6.7) system I did a built then build
> > install *as a user* and not as root. Looking to create a localized copy
> > specifically.
>
> Try this:
>
> $ ./configure --prefix="$HOME/sqlite3"
>
> That will allow the “make install” to work without root privileges.  The
> sqlite3 binary would land in $HOME/sqlite3/bin, with that configuration
> option.
>
> You can set the prefix to somewhere under your Dropbox folder if you’re
> willing to take the risks to data safety that that entails.
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Michael Tiernan]

I found that if I use "disable-tcl" it builds correctly.

(Testing is an issue but that's separate right now.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Michael Tiernan]

Sorry for the top post. Sadly the android client forces it.

In short, I'm building two copies of sqlite3, one of which works fine, the
attempt to build it on the Linux host (using the prefix flag of course)
causes the build to begin but it to fail when it runs into the attempt at
modifying the (non-existent) file /usr/share/tcl8.5/sqlite3

All the other warnings and considerations are secondary to the point that
the makefile is attempting to change the permissions on an external (to the
user) tool which it neither built or should be able to modify.

Thanks for everyone's time!
-- 
<< MCT >>   Michael C Tiernan.http://www.linkedin.com/in/mtiernan

Non Impediti Ratione Cogatationis
Women and cats will do as they please, and
men and dogs should relax and get used to the idea. -Robert A. Heinlein

On Dec 21, 2017 2:26 PM, "Warren Young"  wrote:

On Dec 21, 2017, at 11:37 AM, Michael Tiernan 
wrote:
>
> I'm trying to build two copes of sqlite3 in a shared dropbox folder.

Do you intend to use SQLite inside the Dropbox folder once you’ve got it
working?  That’s only safe if only one person is using the database at a
time, and you wait for the sync to finish before trying to use the DB on
another machine.

If you need a networked DBMS, SQLite is generally not what you want, at
least not as-stock.  There are add-ons and alternatives that work far
better for this.  Google “SQLite Dropbox”.  It’s come up many times before.

> On a "Scientific Linux 6.7" (RHEL 6.7) system I did a built then build
> install *as a user* and not as root. Looking to create a localized copy
> specifically.

Try this:

$ ./configure --prefix="$HOME/sqlite3"

That will allow the “make install” to work without root privileges.  The
sqlite3 binary would land in $HOME/sqlite3/bin, with that configuration
option.

You can set the prefix to somewhere under your Dropbox folder if you’re
willing to take the risks to data safety that that entails.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Warren Young]

On Dec 21, 2017, at 11:37 AM, Michael Tiernan  wrote:
> 
> I'm trying to build two copes of sqlite3 in a shared dropbox folder.

Do you intend to use SQLite inside the Dropbox folder once you’ve got it 
working?  That’s only safe if only one person is using the database at a time, 
and you wait for the sync to finish before trying to use the DB on another 
machine.

If you need a networked DBMS, SQLite is generally not what you want, at least 
not as-stock.  There are add-ons and alternatives that work far better for 
this.  Google “SQLite Dropbox”.  It’s come up many times before.

> On a "Scientific Linux 6.7" (RHEL 6.7) system I did a built then build
> install *as a user* and not as root. Looking to create a localized copy
> specifically.

Try this:

$ ./configure --prefix="$HOME/sqlite3"

That will allow the “make install” to work without root privileges.  The 
sqlite3 binary would land in $HOME/sqlite3/bin, with that configuration option.

You can set the prefix to somewhere under your Dropbox folder if you’re willing 
to take the risks to data safety that that entails.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Michael Tiernan]

Here's my error report.
I'm trying to build two copes of sqlite3 in a shared dropbox folder. It's
crude but I'm doing it to prove the ability I want.

On a "Scientific Linux 6.7" (RHEL 6.7) system I did a built then build
install *as a user* and not as root. Looking to create a localized copy
specifically. At the bottom is the error, the make is attempting to modify
a system tool instead of a local one.

make install
> rm -rf tsrc
> mkdir tsrc
> cp -f /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/alter.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/analyze.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/attach.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/auth.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/backup.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/bitvec.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btmutex.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btree.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btree.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/btreeInt.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/build.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/callback.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/complete.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/ctime.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/date.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/dbpage.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/dbstat.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/delete.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/expr.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/fault.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/fkey.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/func.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/global.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/hash.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/hash.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/hwtime.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/insert.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/legacy.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/loadext.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/main.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/malloc.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem0.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem1.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem2.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem3.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mem5.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/memjournal.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/msvc.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex_noop.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex_unix.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/mutex_w32.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/notify.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_common.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_setup.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_unix.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_win.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/os_win.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pager.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pager.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/parse.y
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pcache.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pcache.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pcache1.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pragma.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/pragma.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/prepare.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/printf.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/random.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/resolve.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/rowset.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/select.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/status.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/shell.c.in
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqlite.h.in
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqlite3ext.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqliteInt.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/sqliteLimit.h
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/table.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/tclsqlite.c
> /home/mct/Dropbox-MIT/Sqlite3/Linux/../sqlite/src/threads.c
> 

Re: [sqlite] Minor bug reports during build.

[Michael Tiernan]

Thank you.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Minor bug reports during build.

[Richard Hipp]

On 12/21/17, Michael Tiernan  wrote:
> Is there a route for reporting an error for an average user without
> creating an account and all the overhead of the ticket system?

Send an email to this mailing list, or directly to me.

-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Minor bug reports during build.

[Michael Tiernan]

Is there a route for reporting an error for an average user without
creating an account and all the overhead of the ticket system?
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users