[mythtv-users] Mythtv Plugins Deb Light Packaging Problem
Peter Bennett
pb.mythtv at gmail.com
Mon May 23 13:30:54 UTC 2022
On 5/23/22 08:57, Adam Skinner wrote:
> Hi All,
>
> Im trying to use the mythtv deb light packaging to build the plugins
> for Mythtv on rasberian bullseye.
>
> The main mythtv frontend package builds fine with the ~/.buildrc options
>
> MYTHTV_CONFIG_OPT_EXTRA="--enable-opengl --disable-vdpau --disable-vaapi"
>
> When I try to use these options to build the plugins package
>
> MYTHTV_CONFIG_OPT_EXTRA="--disable-mythnetvision
> --disable-mythbrowser --disable-mythnews --disable-mythzoneminder
> --disable-mythzmserver --enable-mythweather --enable-mythmusic
> --disable-fftw --disable-mytharchive --disable-mythgame --enable-opengl"
>
>
> It falls over with the following:
>
>
> rmdir: removing directory, './usr/local/share/perl'
> rmdir: removing directory, './usr/local/lib/python3.9'
> rmdir: removing directory, './usr/local/lib/arm-linux-gnueabihf'
> rmdir: removing directory, './usr/share/doc'
> rmdir: removing directory, './usr/share/mythtv/html'
> rmdir: removing directory, './usr/local/share'
> rmdir: removing directory, './usr/local/lib'
> rmdir: removing directory, './usr/local'
> rmdir: missing operand
> Try 'rmdir --help' for more information.
> find:
> ‘/Roms/pi/32build/mythplugins-light_32.0-32-gb6286af7d8-0_armhf_bullseye/usr/bin/’:
> No such file or directory
> Usage: strip <option(s)> in-file(s)
> Removes symbols and sections from files
> The options are:
> -I --input-target=<bfdname> Assume input file is in format
> <bfdname>
> -O --output-target=<bfdname> Create an output file in format
> <bfdname>
> -F --target=<bfdname> Set both input and output format to
> <bfdname>
> -p --preserve-dates Copy modified/access timestamps to
> the output
> -D --enable-deterministic-archives
> Produce deterministic output when
> stripping archives (default)
> -U --disable-deterministic-archives
> Disable -D behavior
> -R --remove-section=<name> Also remove section <name> from the
> output
> --remove-relocations <name> Remove relocations from section <name>
> -s --strip-all Remove all symbol and relocation
> information
> -g -S -d --strip-debug Remove all debugging symbols & sections
> --strip-dwo Remove all DWO sections
> --strip-unneeded Remove all symbols not needed by
> relocations
> --only-keep-debug Strip everything but the debug
> information
> -M --merge-notes Remove redundant entries in note
> sections (default)
> --no-merge-notes Do not attempt to remove redundant
> notes
> -N --strip-symbol=<name> Do not copy symbol <name>
> --keep-section=<name> Do not strip section <name>
> -K --keep-symbol=<name> Do not strip symbol <name>
> --keep-file-symbols Do not strip file symbol(s)
> -w --wildcard Permit wildcard in symbol comparison
> -x --discard-all Remove all non-global symbols
> -X --discard-locals Remove any compiler-generated symbols
> -v --verbose List all object files modified
> -V --version Display this program's version number
> -h --help Display this output
> --info List object formats & architectures
> supported
> -o <file> Place stripped output into <file>
> strip: supported targets: elf32-littlearm elf32-littlearm-fdpic
> elf32-bigarm elf32-bigarm-fdpic elf32-little elf32-big srec symbolsrec
> verilog tekhex binary ihex plugin
>
>
> I dont use the plugins that are disabled - but I use Mythmusic a lot.
> I am keen to reduce ram usage as my pi only has 2G - and often run out
> of memory playing music.
>
> I can build ALL the plugins when I have a blank buildrc with no options.
>
> Anyone have any ideas?
>
> Thanks in advance
>
The problem is that MYTHTV_CONFIG_OPT_EXTRA applies to mythtv options,
not to plugin options. When building the plugins you have to leave the
MYTHTV_CONFIG_OPT_EXTRA exactly the same as it was when you built
mythtv. The script does not have an ability to insert extra plugin
options or to change the options.
What is happening is that the plugin build runs the mythtv configure
again with a different destination directory and the
MYTHTV_CONFIG_OPT_EXTRA options are used for the MythTV configure. That
would be failing since --disable-mythnetvision etc are not valid MythTV
build options.
Also remember that the plugin build makes use of the intermediate files
from the prior mythtv build, so if the mythtv build has been damaged you
may have to run it again in order to get the plugin build to work.
If you want some plugins disabled I recommend delete the applicable
".so" files from your system after installing.
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220523/aea0eff8/attachment.htm>
More information about the mythtv-users
mailing list