advice for GMPC in TC5.x

[coreplayer2]

Exactly...   I use automake which installes autoconf , otherwise the build will complain about autoreconf  which is part of  autoconf.

Also the build log specifically used bash at some point, maybe because bash was installed and is now the shell...??    Was strange to see a command using bash in the log though

[bmarkus]

Please use prefix=/usr/local it is the TC standard.

You can disable static, probably no one need static build later. It will reduce -dev size. In worst case you can rebuild it with static

dbus is used by desktop environments like Xfce, Gnome, KDE, not in the basic GUI. You can disable. See note above

[gavs]

Thanks to everyone, compilation of libunique completed without error, as far as I can tell. I will adjust permissions, set root:root as owner, split out the dev files using the TC4.x as a guide (I do not know what is dev and what is not), strip to reduce file size and use mksquash to make the extensions. If all goes well I will try to submit.

There was a bit of difference in the files created that I have questions about.

Question 1. The file /usr/local/lib/libunique-1.0.a was not created. This file was in libunique-dev for TC4.x. Is this OK?

Question 2. Directories /usr/local/share/gir-1.0 and /usr/local/lib/girepository-1.0 were created. Should I include these in libunique or libunique-dev? They were not present in the TC4.x extensions.

[bmarkus]

Put gir files to libunique-gir.tcz

Put include, *.a, *.la, pkgconfig to libunique-dev.tcz if they exist.

Study extensions in the repo, try to enable/disable static and look for diffrenece. It will help

[gavs]

Thank you bmarkus for the hints. After some investigation, I am guessing that the *.a file (which I found out was a static library file) was not generated because I used the option --disable-static in the configuration.

I made some progress. I built libunique in TC5.x. With this, I was successful in building gmpc in TC5.x. But perhaps, even though the make worked, everything is not well. Starting with a clean TinyCore, I installed alsa.tcz, mpd-minimal.tcz (I was able to build this extension in TC5.x) and gmpc.tcz. The alsa command speaker-test gives output, so alsa should be working. I started mpd and it created its database and did not report any error. When I tried to start gmpc it complained about missing libunique-1.0.so. Libunique had not been listed as a dependency in TC4.x. I added it. I also the dependency gnutils2.tcz to gnutils.tcz. They look similar but it appears that gnutils is a newer version? When I tried gmpc again I get the following error:

** (gmpc:10576): Warning **: Unable to open a connection to the session bus: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory

(gmpc:10576): GLib-GIO-CRITICAL **: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

Does this have anything to do with using the configuration option --disable-dbus? Since that option made GDBus default, is there a missing dependency?

[Juanito]

As mentioned a couple of posts back, there is more recent version of gnutls in tc-5.x - if you compiled libunique and gmpc on tc-5.x then there should be no problem with this and you just need to update the dep file to reference gnutls rather than gnutls2.

Although you compiled libunique without the dbus dep, it seems like gmpc is looking for dbus - did you try loading the dbus extension and starting the daemon?

[gavs]

Thank you Juanito, loading dbus.tcz worked. I had compiled libunique, libmpd and gmpc in TC5.x and I updated the dependency to gnutils instead of gnutils2. Now GMPC opened, connected to the mpd daemon and I was able to play music. Nice.

I will try completing all the steps needed to submit the extensions. Thanks to all.

[gavs]

Forgot to mention that this was done with gob2.tcz from the TC4.x repo.

Will that extension get copied to the TC5.x repo or is further testing needed?

[Juanito]

It looks like it should work - gob2 copied to the 5.x repo

Did you manage to submit the extensions?

[gavs]

Thank you for copying gob2 to the TC5.x repo, I see it there now.

Question 1: I compiled with the gob2 that I had obtained from the TC4.x repo. I assume that I do not need to recompile and rebuild everything again with the gob2 from the TC5.x repo, since it was just a copy? Please confirm.

I have prepared the following extensions for submission:
libunique
mpd-minimal
libmpd
gmpc
gmpc-tagedit
gmpc-albumview

I have not run them through submitqc yet, but I have loaded them locally and all seems to be working. I have not heard back from the maintainers of mpd-minimal (gutmensch) or gmpc (TaoTePuh). I was holding back on submitting any extensions because when I compiled mpd-minimal I left out missing dependencies libmpcdec and wavpack (I do not use these encodings). I thought I should go back and try to include these though for consistency. I heard back from the maintainers (Jason W and bmarkus respectively) that they were not planning to do anything with these and I should go ahead and compile in TC5.x. Wavpack compiled without complication and I am in the process of preparing it. Libmpcdec was not straightforward. The tar did not contain a configure, but there was a configure.in. I guessed (perhaps wrongly??) that I could use automake/autoconf. When I tried autoconf, I got an error message for "possibly undefined macro" followed by "if this token is legitimate, please use m4_pattern_allow. There are 5 such tokens listed. I was going to do some research on the autoconf documentation to see how I would use m4_pattern_allow. Any advice welcome, as I am just fumbling through this.

Question 2. I suppose adding the missing dependencies to mpd-minimal should not have any impact on the other extensions, so I should proceed with using submitqc to check and then I guess bcrypt is recommended before e-mailing?

Question 3. Is it preferred that each of -dev, -gir, -locale, - doc and the gmpc-plugins extensions be submitted separately with their respective .info, .dep, .list and .md5.txt files or is it preferred if they are bundled in one submission per package name, e.g. libunique, libunique-dev and libunique-gir.

[Juanito]

I assume that I do not need to recompile and rebuild everything again with the gob2 from the TC5.x repo, since it was just a copy? Please confirm.

Affirmative - no need to recompile

The tar did not contain a configure, but there was a configure.in.

There would normally be a script named autogen.sh that requires automake and libtool-dev to run and will create the configure script.

Question 2. I suppose adding the missing dependencies to mpd-minimal should not have any impact on the other extensions, so I should proceed with using submitqc to check and then I guess bcrypt is recommended before e-mailing?

Please go ahead

Question 3. Is it preferred that each of -dev, -gir, -locale, - doc and the gmpc-plugins extensions be submitted separately with their respective .info, .dep, .list and .md5.txt files or is it preferred if they are bundled in one submission per package name, e.g. libunique, libunique-dev and libunique-gir.

I guess it depends on the size - for large extensions submit extension by extension and for smaller ones bundle by extension name.

..and thanks for your contribution to tinycore

[gavs]

Regarding the musepack tar, I tried
$ cd musepack_src_r475
$ find -name auto*
$ find -name *.sh
Nothing was returned. Not sure where to go from here. I could just leave out libmpcdec during compile, but maybe I should pm the previous maintainer, Jason W to ask for advice on how he compiled.

I tried submitqc5 with the extensions I have prepared. Submitqc5 reports corrupt tcz files. It asks 'PLEASE VERIFY THEY ARE GOOD OR REMAKE'. Libunique was used during compilation. I have loaded mpd-minimal, gmpc and the gmpc plugins. They appear to load cleanly and I am able to play music files. Is there something further I should do to verify?

[Juanito]

Would this be of any use:

http://repo.tinycorelinux.net/tcz/src/libmpcdec-1.2.6/libmpcdec-1.2.6.tcbuild

As for the 'PLEASE VERIFY THEY ARE GOOD OR REMAKE' message, I have not come across this before - maybe you could submit anyway?

[gavs]

I was able to compile libmpcdec-1.2.6. I had been trying to compile musepack_src_r475 because it is a more recent release. Apparently libmpcdec-1.2.6 uses SV7 while the newer version uses SV8. As I mentioned, I do not use this encoder, so I do not really know if the version makes a difference. Using the libmpcdec-1.2.6 maintains consistency with TC4.x so I will build that extension and submit it and use it to compile the mpd-minimal extension.

I will submit the extensions if they are working, despite the warning from submitqc5.

[coreplayer2]

'PLEASE VERIFY THEY ARE GOOD OR REMAKE'

I've seen this before, frankly it puzzled me for a while.   Though I can't remember exactly the cause off the top of my head, the best answer I can give at the moment is that it's system related.  I found that the tcz squash'd archive was in perfect condition when  "submitqc5" tested on other systems (I use the script below to automate the process and while unrelated it reveals also we may need to use sudo submitqc5).  All I can suggest is be sure the current build system is updated and run "submitqc5" on the tcz using another system to verify (iirc the issue may have been with an x86_64 extension I had installed at the time, but I'm not sure..).


perhaps this script will help you when making many extensions,
create many directories each complete with files to test with submitqc5 then tar and submit, run
from the parent directory which will also tar the contents ready to email.   once an extension tar file has been created
the script will not test the contents again, will pass up that dir and move on to the next etc etc
each time i add a new directory containing tcz and info file.I simply run the script again