Building nightlies on Linkstation 2(MIP SEL)

[spakment]

Hi
Can anyone walk me through building the mt-daapd nightlies?
I’m new to linux, here’s what I’ve done so far;
I’ve built the stable 0.2.4 version which works perfectly on hte linkstation (I’ve installed openlink firmware & all dev tools)

I have id3 libs in /usr/lib from previous installs

I built sqlite3, the “make install” put the libs & includes into /usr/local/lib & /usr/local/include
the sqlite3 binary is in /usr/local/bin
it runs fine, gives me the sqlite3 prompt and works okay.

now onto the configure script for the nightlies(I’ve tried 1197, 1159 & 1206)….
I give the configure script the following arguements:

./configure –enable-sqlite3 –with-sqlite3-includes=/usr/local/include –with-sqlite3-libs=/usr/local/lib –enable-browse –enable-query –with-id3tag=/usr/local

Now “./configure” happily completes (no errors)
“make” runs fine
“make install” puts the binary into /usr/local/sbin
then I update the mt-daapd config file in /etc/mt-daapd.conf
(update for my sys paths.. and have double checked that
db_type = sqlite3)

running
./mt-daapd -d5 -f -y
gives:

setting dest to 1

Loading new config file.

Starting with debuglevel 5

Starting rendezvous daemon

Starting signal handler

SetupInterfaceList

mDNS_RegisterInterface: InterfaceID 10008BC0 192.168.0.55 not represented in list; marking active and retriggering queries

Adding 10008BD0 LINK300GB.local. (Addr) to active record list

Adding 10008E7C 55.0.168.192.in-addr.arpa. (PTR) to active record list

Not creating HINFO record: platform support layer provided no information

SetupOneInterface: eth0 192.168.0.55 Registered

Error opening db: No backend database support for type: sqlite

Signal handler started

Stopping mDNS

Stopping signal handler

mDNS_Close: RR Cache was using 0 records, 0 active

mDNS_Close: No deregistering records remain

mDNS_Close: mDNSPlatformClose

mDNS_DeregisterInterface: Last representative of InterfaceID 10008BC0 deregistered; marking questions etc. dormant

mDNS_Close: done

Got shutdown signal. Notifying daap server.

I know I’ve missed something and / or done something wrong, many thanks to anyone who can point me in the right direction.
Cheers
Dave

[rpedde]

@spakment wrote:

Error opening db: No backend database support for type: sqlite

It’s reading the config from /usr/local/etc. You’ll want to use a “-c /etc/mt-daapd.conf”, or put the config you want to run in /usr/local/etc.

This misfeature is going to go away soon, and it will always look in /etc/mt-daapd/mt-daapd.conf, then /etc/mt-daapd.conf and then fail.

— Ron

[whocares]

@rpedde wrote:

This misfeature is going to go away soon, and it will always look in /etc/mt-daapd/mt-daapd.conf, then /etc/mt-daapd.conf and then fail.

Erm. Would it be too much to ask for mt-daapd to honor –sysconfdir= when doing a configure? I mean, that’s the way most other software behaves and you could still check for configs in /etc/mt-daapd and /etc if you’re so inclined.

Cheers,
Stefan

[rpedde]

@whocares wrote:

@rpedde wrote:

This misfeature is going to go away soon, and it will always look in /etc/mt-daapd/mt-daapd.conf, then /etc/mt-daapd.conf and then fail.

Erm. Would it be too much to ask for mt-daapd to honor –sysconfdir= when doing a configure? I mean, that’s the way most other software behaves and you could still check for configs in /etc/mt-daapd and /etc if you’re so inclined.

Sounds reasonable.

[spakment]

put the config you want to run in /usr/local/etc

works perfectly now!
thanks Ron

[Author]

Posts