Logitechmediaserver fails to build

Walter Schwarzenfeld w.schwarzenfeld at utanet.at
Tue Apr 3 12:27:31 UTC 2018


It is a little more complicated as I thought in the first moment:

You also need add to your patch:

@@ -520,7 +537,7 @@ function build {
              ;;

          Class::XSAccessor)
-            if [ "$PERL_516" -o "$PERL_518" -o "$PERL_520" -o 
"$PERL_522" -o "$PERL_524" ]; then
+            if [ "$PERL_516" -o "$PERL_518" -o "$PERL_520" -o 
"$PERL_522" -o "$PERL_524" -o "$PERL_526" ]; then
                  build_module Class-XSAccessor-1.18
                  cp -pR $PERL_BASE/lib/perl5/$ARCH/Class $PERL_ARCH/
              else
@@ -536,7 +553,7 @@ function build {
              ;;

          DBI)
-            if [ "$PERL_518" -o "$PERL_520" -o "$PERL_522" -o 
"$PERL_524" ]; then
+            if [ "$PERL_518" -o "$PERL_520" -o "$PERL_522" -o 
"$PERL_524" -o "$PERL_526" ]; then
                  build_module DBI-1.628
                  cp -p $PERL_BASE/lib/perl5/$ARCH/DBI.pm $PERL_ARCH/
                  cp -pR $PERL_BASE/lib/perl5/$ARCH/DBI $PERL_ARCH/
@@ -546,7 +563,7 @@ function build {
              ;;

          DBD::SQLite)
-            if [ "$PERL_518" -o "$PERL_520" -o "$PERL_522" -o 
"$PERL_524" ]; then
+            if [ "$PERL_518" -o "$PERL_520" -o "$PERL_522" -o 
"$PERL_524" -o "$PERL_526" ]; then
                  build_module DBI-1.628 "" 0
              else
                  build_module DBI-1.616 "" 0
@@ -632,7 +649,7 @@ function build {
                  rm -rf DBD-SQLite-1.34_01
              else
                  cd ..
-                if [ "$PERL_516" -o "$PERL_518" -o "$PERL_520" -o 
"$PERL_522" -o "$PERL_524" ]; then
+                if [ "$PERL_516" -o "$PERL_518" -o "$PERL_520" -o 
"$PERL_522" -o "$PERL_524" -o "$PERL_526" ]; then
                     build_module DBD-SQLite-1.34_01 "" 0
                  fi
                  build_module DBD-SQLite-1.34_01
@@ -714,7 +731,7 @@ function build {
          JSON::XS)
              build_module common-sense-2.0

-            if [ "$PERL_518" -o "$PERL_520" -o "$PERL_522" -o 
"$PERL_524" ]; then
+            if [ "$PERL_518" -o "$PERL_520" -o "$PERL_522" -o 
"$PERL_524" -o "$PERL_526" ]; then
                  build_module JSON-XS-2.34
                  cp -pR $PERL_BASE/lib/perl5/$ARCH/JSON $PERL_ARCH/
              else
@@ -744,7 +761,7 @@ function build {
              ;;

          YAML::LibYAML)
-            if [ "$PERL_516" -o "$PERL_518" -o "$PERL_520" -o 
"$PERL_522" -o "$PERL_524" ]; then
+            if [ "$PERL_516" -o "$PERL_518" -o "$PERL_520" -o 
"$PERL_522" -o "$PERL_524" -o "$PERL_526" ]; then
                  build_module YAML-LibYAML-0.35 "" 0
              else
                  build_module YAML-LibYAML-0.35
@@ -1403,7 +1420,7 @@ find $BUILD -name '*.packlist' -exec rm

  # create our directory structure
  # rsync is used to avoid copying non-binary modules or other extra stuff
-if [ "$PERL_512" -o "$PERL_514" -o "$PERL_516" -o "$PERL_518" -o 
"$PERL_520" -o "$PERL_522" -o "$PERL_524" ]; then
+if [ "$PERL_512" -o "$PERL_514" -o "$PERL_516" -o "$PERL_518" -o 
"$PERL_520" -o "$PERL_522" -o "$PERL_524" -o "$PERL_526" ]; then
      # Check for Perl using use64bitint and add -64int
      ARCH=`$PERL_BIN -MConfig -le 'print $Config{archname}' | sed 
's/gnu-//' | sed 's/^i[3456]86-/i386-/' | sed 's/armv.*?-/arm-/' `
  fi


but this conflicts with the extrapatch.

(vendorpatch-CPAN_buildme.sh)

It build if I remove the first part 
(./slimserver-vendor-1463b00/CPAN/buildme.sh) of this patch.

But in this patch is another conditional patch. And if I remove the 
first part of it, there is no condition anymore:

# because it takes so damn long on slow platforms
              if [ ! -f build/lib/libicudata_s.a ]; then
                  tar_wrapper zxvf icu4c-4_6-src.tgz
=>+               patch << END

  So the second part will applied if needed or not.

I got it to build.

For installation we need a new pkg-plist.

I could install it with a new pkg-plist, but it has the variable 
%%AMD64_ONLY%% (must added per hand). And I am not really clear

in which line it is needed.


So I think it is better, you make a PR.






More information about the freebsd-ports mailing list