You were right .. error log snippet:

Transparent huge pages are enabled, according to /sys/kernel/mm/transparent_hugepage/enabled

141209 12:26:00 [ERROR] TokuDB: Huge pages are enabled, disable them before continuing

141209 12:26:00 [ERROR] ************************************************************

141209 12:26:00 [ERROR]                                                             

141209 12:26:00 [ERROR]                         @@@@@@@@@@@                         

141209 12:26:00 [ERROR]                       @@'         '@@                       

141209 12:26:00 [ERROR]                      @@    _     _  @@                      

141209 12:26:00 [ERROR]                      |    (.)   (.)  |                      

141209 12:26:00 [ERROR]                      |             ` |                      

141209 12:26:00 [ERROR]                      |        >    ' |                      

141209 12:26:00 [ERROR]                      |     .----.    |                      

141209 12:26:00 [ERROR]                      ..   |.----.|  ..                      

141209 12:26:00 [ERROR]                       ..  '      ' ..                       

141209 12:26:00 [ERROR]                         .._______,.                         

141209 12:26:00 [ERROR]                                                             

141209 12:26:00 [ERROR] TokuDB will not run with transparent huge pages enabled.        

141209 12:26:00 [ERROR] Please disable them to continue.                            

141209 12:26:00 [ERROR] (echo never > /sys/kernel/mm/transparent_hugepage/enabled)  

141209 12:26:00 [ERROR]                                                             

141209 12:26:00 [ERROR] ************************************************************

141209 12:26:00 [ERROR] Plugin 'TokuDB' init function returned error.

141209 12:26:00 [ERROR] Plugin 'TokuDB' registration as a STORAGE ENGINE failed.

141209 12:35:03 [Note] /usr/sbin/mysqld: Normal shutdown

141209 12:35:03 [Note] Event Scheduler: Purging the queue. 0 events

141209 12:35:03 [Note] InnoDB: FTS optimize thread exiting.

141209 12:35:03 [Note] InnoDB: Starting shutdown...

141209 12:35:04 [Note] InnoDB: Shutdown completed; log sequence number 1617333

141209 12:35:04 [Note] /usr/sbin/mysqld: Shutdown complete

I found this

https://mariadb.com/kb/en/mariadb/documentation/storage-engines/tokudb/how-to-enable-tokudb-in-mariadb/

and after 

linux-hwpu:/home/peter # echo never > /sys/kernel/mm/transparent_hugepage/enabled

linux-hwpu:/home/peter # echo never > /sys/kernel/mm/transparent_hugepage/defrag 

(and next from any MySQL client as root)

INSTALL SONAME 'ha_tokudb';

SHOW WARNINGS;

-- Warning    1105  Cannot enable tc-log at run-time. XA features of TokuDB are disabled (so I will need to add it during boot as the link also describes) 

SHOW ENGINES;--and it *IS* there NOW.

-- Peter

On Tue, Dec 9, 2014 at 2:46 PM, Peter Laursen <peter_laursen@webyog.com> wrote:

It seems they are not yet in the RPMs of the MariaDB repo for OpenSuSE. At least they were not 5-6 hours ago. But I am not in a hurry.

-- Peter

On Tue, Dec 9, 2014 at 2:41 PM, Sergei Golubchik <serg@mariadb.org> wrote:

Hi, Peter!

On Dec 09, Peter Laursen wrote:
>
> But most important TokuDB plugin does not load. This may because this is
> SuSE 12.3 (that may ship with another  C-runtime etc. than what 12.1 and
> 12.2 did).
> INSTALL SONAME 'ha_tokudb';
> -- Error Code: 1123
> -- Can't initialize function 'TokuDB'; Plugin initialization function
> failed.

See the error log, it might contain more specific error messages.
One probable reason could be transparent_hugepage enabled on your
computer.

> BTW: I also had some communication on Fedora's mailinglist. They have
> MariaDB 10.0.14 in Fedora 21 repos.  But without TokuDB.  They cannot build
> it. They have reported to MariaDB (they say).

Yes, there were issues with TokuDB and gcc 4.9 (MDEV-6446, MDEV-6449),
but they were fixed.

And there was binutils bug in Fedora (it resulted in crashes when
compiling TokuDB): https://bugzilla.redhat.com/show_bug.cgi?id=1149660
As far as I understand, it's also fixed by now.

Regards,
Sergei