oqgraph-dev team mailing list archive

[Antony T Curtis <atcurtis@xxxxxxxxx>]

Regarding the FindJUDY error... I think I forgot to check in a file.
Oops...


Antony T Curtis
atcurtis@xxxxxxxxx



On Feb 14, 2013, at 4:23 AM, Andrew McDonnell <bugs@xxxxxxxxxxxxxxxxxxx> wrote:

> Hi people
> 
> I managed to branch Antonys branch then locally checkout a working copy.
> It builds cleanly for me on a hybrid Squeeze amd64. (See below for some notes)
> 
> I then use the following instructions to run up mysqld in my tree:
>  https://kb.askmonty.org/en/running-mariadb-from-the-source-directory/
> 
> The first error was:
> `Cannot change ownership of the database directories to the 'mysql' user`
> 
> This was at odds with the mysql_install_db --help:
>  --user=user_name     The login username to use for running mysqld.  Files
>                       and directories created by mysqld will be owned by this
>                       user.  You must be root to use this option.  By default
>                       mysqld runs using your current login name and files and
>                       directories that it creates will be owned by you.
> 
> Looking through mysql_install_db, it first seems to grab the defaults from
> extra/my_print_defaults, which yields user=mysql, and then parse the command
> line.  Which means that defaulting to the current user never happens.
> 
> Therefore I propose to change the help to remove the bit about the current
> user and instead indicate the default is uid mysql, and that you need to
> specify --user=$LOGNAME, etc.
> 
> 
> Anyway, I then tried running as follows:
> 
> sh scripts/mysql_install_db --user=andrew --srcdir=$PWD
> --datadir=/home/maria/test/data
> 
> This started a database installation process which looked like it was working.
> This proceeded to create ibdata1 etc.
> 
> But then it aborted:
> 
> 130214 22:32:58 [ERROR]
> /home/andrew/develop/maria/repo/andrew-dev/build/sql/mysqld: unknown option
> '--skip-locking'
> 130214 22:32:58 [ERROR] Aborting
> 
> 130214 22:32:58 InnoDB: FTS optimize thread exiting.
> 130214 22:32:58 InnoDB: Starting shutdown...
> 130214 22:32:59 InnoDB: Shutdown completed; log sequence number 1595679
> 130214 22:33:00 [Note]
> /home/andrew/develop/maria/repo/andrew-dev/build/sql/mysqld: Shutdown complete
> 
> 
> Installation of system tables failed!  Examine the logs in
> /home/maria/test/data for more information.
> 
> (etc)
> 
> Repeating from scratch with --defaults-file=~/.my.cnf as suggested didn't
> help, and no debug logs were created.
> 
> Adding skip-grant-tables to the file .my.cnf (based on other suggestions in
> the error output) also didn't help.
> 
> As a last resort I added set -x to mysql_install_db and discovered that actual
> command line used doesn't even have --skip-locking:
> 
> + /home/andrew/develop/maria/repo/andrew-dev/build/sql/mysqld
> --defaults-file=~/.my.cnf
> --lc-messages-dir=/home/andrew/develop/maria/repo/andrew-dev/build/sql/share/english/..
> --bootstrap --basedir=/home/andrew/develop/maria/repo/andrew-dev/build
> --datadir=/home/maria/test/data --log-warnings=0 --loose-skip-ndbcluster
> --loose-skip-pbxt --user=andrew --max_allowed_packet=8M
> --default-storage-engine=myisam --net_buffer_length=16K
> 
> Running `mysqld --help --verbose` doesnt have a skip-locking option.
> 
> If I then run `mysqld --user=andrew` it again fails on the skip locking error
> message.
> 
> So I am not sure how to make it work from here...
> 
> 
> (full log attached)
> 
> 
> thanks,
> Andrew
> 
> 
> TL;DR Other stuff:
> 
> Note that I actually make a separate build/ directory and run `cmake .. &&
> make, but this is not completely catered for.
> 
> 
> 
> However `scripts/mysql_install_db` does not have the executable bit set, so
> unlike the instructions I had to run it using sh.  This failed looking for
> 
> fill_help_tables.sql
> 
> which is located in $BZR_ROOT/scripts but not copied to build/scripts.
> 
> So for now I hacked it by symlinking the sql files to build/scripts
> 
> ( cd scripts ; ln -s ../../scripts/*.sql )
> 
> Now it works.
> 
> 
> 
> 
> 
> I noted the following message during cmake, but then during make it seemed to
> build a local copy of the library anyway.
> 
> <snipped>
> -- Configuring OQGraph
> -- Boost version: 1.42.0
> CMake Warning at storage/oqgraph/CMakeLists.txt:9 (FIND_PACKAGE):
>  Could not find module FindJUDY.cmake or a configuration file for package
>  JUDY.
> 
>  Adjust CMAKE_MODULE_PATH to find FindJUDY.cmake or set JUDY_DIR to the
>  directory containing a CMake configuration file for JUDY.  The file will
>  have one of the following names:
> 
>    JUDYConfig.cmake
>    judy-config.cmake
> 
> 
> 
> -- Judy not found
> <snipped>
> 
> 
> PS using thunderbird I need to find an extension that lets me unwrap just
> selected sections of text, I hope the pasted commands are not too mangled for you
> 
> 
> -- 
> 
> 
> https://launchpad.net/~andymc73
> http://blog.oldcomputerjunk.net
> Twitter: @andymc73
> GPG: http://www.andrewmcdonnell.net/gpg.html
> <attach0.txt><attach1.txt>-- 
> Mailing list: https://launchpad.net/~oqgraph-dev
> Post to     : oqgraph-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oqgraph-dev
> More help   : https://help.launchpad.net/ListHelp