精华内容
下载资源
问答
  • 2021-06-05 18:34:13

    Android5.0 Gallery2上编译Gallery模块出错

    在L上面,编译整个project可以编译通过,但是单独编译Gallery2模块出错,build gallery模块出现refocus的error

    target C++: libjni_jpegstream <= packages/apps/Gallery2/jni_jpegstream/src/outputstream_wrapper.cpp

    target C++: libjni_jpegstream <= packages/apps/Gallery2/jni_jpegstream/src/stream_wrapper.cpp

    target SharedLib: libjni_jpegstream (out/target/product/gionee6735_65c_l/obj/SHARED_LIBRARIES/libjni_jpegstream_intermediates/LINKED/libjni_jpegstream.so)

    target Symbolic: libjni_jpegstream (out/target/product/gionee6735_65c_l/symbols/system/lib64/libjni_jpegstream.so)

    Export includes file: packages/apps/Gallery2/jni_jpegstream/Android.mk -- out/target/product/gionee6735_65c_l/obj/SHARED_LIBRARIES/libjni_jpegstream_intermediates/export_includes

    target Strip: libjni_jpegstream (out/target/product/gionee6735_65c_l/obj/lib/libjni_jpegstream.so)

    Install: out/target/product/gionee6735_65c_l/system/lib64/libjni_jpegstream.so

    make: *** 没有规则可以创建“out/target/product/xxxxxxx/obj_arm/SHARED_LIBRARIES/libjni_image_refocus_intermediates/import_includes”

    需要的目标“out/target/product/xxxxxxx/obj_arm/STATIC_LIBRARIES/libutilitysw_intermediates/export_includes”。 停止。

    有两种解决办法:

    第一种方法:若mmm packages/apps/Gallery2来build的话,请将packages/apps/Gallery2/src/jni_refocus/Android.mk文件删除

    第二种方法:或者使用mmma packages/apps/Gallery2来编译,它会检查dependence

    更多相关内容
  • springcloud多模块报错

    2022-01-24 19:51:39
    这次项目的总模块为springcloud01, 结果发现原因是:我在common中的父模块为springcloud01,然后在springcloud01又添加了common依赖,provider中父模块为springcloud01,所以加载依赖是出现了循环调用,导致无法打成...

    The POM for 0.0.1-SNAPSHOT is missing, no dependency informat

    这次项目的总模块为springcloud01, 结果发现原因是:我在common中的父模块为springcloud01,然后在springcloud01又添加了common依赖,provider中父模块为springcloud01,所以加载依赖是出现了循环调用,导致无法打成jar包。

    解决方案:

    方案一:在springcloud01的pom中删掉common依赖

    方案二:在修改common的父模块,修改为springcloud01的父模块,即:

      <parent>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-parent</artifactId>
            <version>2.2.4.RELEASE</version>
            <relativePath/> <!-- lookup parent from repository -->
        </parent>

    展开全文
  • Android编译模块报错的奇葩错误

    千次阅读 2022-02-08 17:43:27
    intermediates/aplay: Is a directory 看out下文件aplay.o已经生成,就在最后一步报错了,不像是代码问题 为了验证是否是代码问题,写了个空main函数的aplay.c来编译还是报一样的错误,证明不是代码问题 报错时...

    移植编译alsa-util时遇到一个奇葩错误如下

    [ 98% 218/222] target  C: aplay <= vendor/xxxx/bin/alsa-utils-1.1.9/aplay/aplay.c
    vendor/xxxx/bin/alsa-utils-1.1.9/aplay/aplay.c:3:1: warning: return type of 'main' is not 'int' [-Wmain-return-type]
    void main()
    ^
    vendor/xxxx/bin/alsa-utils-1.1.9/aplay/aplay.c:3:1: note: change return type to 'int'
    void main()
    ^~~~
    int
    1 warning generated.
    [ 99% 221/222] target Strip: aplay (out/target/product/xxxx/obj/EXECUTABLES/aplay_intermediates/aplay)
    FAILED: out/target/product/se1000/obj/EXECUTABLES/aplay_intermediates/aplay
    /bin/bash -c "CLANG_BIN=prebuilts/clang/host/linux-x86/clang-r383902b1/bin      CROSS_COMPILE=prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-      XZ=prebuilts/build-tools/linux-x86/bin/xz     build/soong/scripts/strip.sh -i out/target/product/xxxx/symbols/system/bin/aplay -o out/target/product/xxxx/obj/EXECUTABLES/aplay_intermediates/aplay -d out/target/product/xxxx/obj/EXECUTABLES/aplay_intermediates/aplay.strip.d  --keep-mini-debug-info"

    rm: out/target/product/xxxx/obj/EXECUTABLES/aplay_intermediates/aplay: Is a directory

    看out下文件aplay.o已经生成,就在最后一步报错了,不像是代码问题

    为了验证是否是代码问题,写了个空main函数的aplay.c来编译还是报一样的错误,证明不是代码问题

    报错时Android.mk写法如下:

    LOCAL_PATH:= $(call my-dir)
    include $(CLEAR_VARS)
    LOCAL_MODULE := aplay
    LOCAL_C_INCLUDES += \
         $(LOCAL_PATH)/include \
    	 $(LOCAL_PATH)/../alsa-lib-1.1.9/include 
    
    LOCAL_SRC_FILES := \
    	aplay/aplay.c
    
    #LOCAL_SHARED_LIBRARIES := libasound
    LOCAL_STATIC_LIBRARIES := libasound
    LOCAL_CFLAGS += -Wall -Wno-unused-parameter -std=gnu99 
    include $(BUILD_EXECUTABLE)

    分析难道是module  name与C文件或文件夹重名导致的?

    修改LOCAL_MODULE 后编译OK

    LOCAL_PATH:= $(call my-dir)
    include $(CLEAR_VARS)
    LOCAL_MODULE := alsa_aplay
    LOCAL_C_INCLUDES += \
         $(LOCAL_PATH)/include \
    	 $(LOCAL_PATH)/../alsa-lib-1.1.9/include 
    
    LOCAL_SRC_FILES := \
    	aplay/aplay.c
    
    #LOCAL_SHARED_LIBRARIES := libasound
    LOCAL_STATIC_LIBRARIES := libasound
    LOCAL_CFLAGS += -Wall -Wno-unused-parameter -std=gnu99 
    #LOCAL_WHOLE_STATIC_LIBRARIES := alpu_fa_000_static
    include $(BUILD_EXECUTABLE)

    展开全文
  • 在中标麒麟(neokylin)系统中部署某服务,使用到了ansible,但是执行时发现有yum模块的task报错如下: TASK [common : Install basic rpms] ******************************************************************...

    问题现象

    在中标麒麟(neokylin)系统中部署某服务,使用到了ansible,但是执行时发现有yum模块的task报错如下:

    TASK [common : Install basic rpms] **************************************************************************
    fatal: [node01]: FAILED! => {"changed": false, "msg": ["Could not detect which major revision of yum is in use, which is required to determine module backend.", "You can manually specify use_backend to tell the module whether to use the yum (yum3) or dnf (yum4) backend})"]}
    

    报错为yum模块无法判断出系统的yum版本,提示需要手工执行yum的use_backend参数。同样的task在原生RHEL7系统执行没有遇到任何问题,看样子调入了中标麒麟的某个坑里。

    问题分析

    根据报错,很明确是因为ansible无法自动判断出系统使用的yum版本导致,我们知道当ansible中yum模块不指定use_backend参数时,将尝试自动判断,而ansible的setup模块可以获取对应的必要信息, 其中一个变量ansible_pkg_mgr及对应yum后端模块,接下来我们执行setup模块输出ansible_pkg_mgr变量来验证下我们的判断:

    # ansible -i hosts node01 -m setup -a "filter=ansible_pkg_mgr"
    node01 | SUCCESS => {
        "ansible_facts": {
            "discovered_interpreter_python": "/usr/bin/python"
        },
        "changed": false
    }
    

    果然没有办法获取到ansible_pkg_mgr变量,先看下系统版本信息:

    ~]# cat /etc/neokylin-release
    NeoKylin Linux Advanced Server release V7Update6 (Chromium)
    

    接下来根据报错提示信息找到ansible相关代码,在yum.py中,相关代码如下: ansible/plugins/action/yum.py

            if module not in ["yum", "yum4", "dnf"]:
                facts = self._execute_module(module_name="setup", module_args=dict(filter="ansible_pkg_mgr", gather_subset="!all"), task_vars=task_vars)
                display.debug("Facts %s" % facts)
                module = facts.get("ansible_facts", {}).get("ansible_pkg_mgr", "auto")
                if (not self._task.delegate_to or self._task.delegate_facts) and module != 'auto':
                    result['ansible_facts'] = {'pkg_mgr': module}
    
            if module != "auto":
    
                if module == "yum4":
                    module = "dnf"
    
                if module not in self._shared_loader_obj.module_loader:
                    result.update({'failed': True, 'msg': "Could not find a yum module backend for %s." % module})
                else:
                    # run either the yum (yum3) or dnf (yum4) backend module
                    new_module_args = self._task.args.copy()
                    if 'use_backend' in new_module_args:
                        del new_module_args['use_backend']
    
                    display.vvvv("Running %s as the backend for the yum action plugin" % module)
                    result.update(self._execute_module(module_name=module, module_args=new_module_args, task_vars=task_vars, wrap_async=self._task.async_val))
                    # Now fall through to cleanup
            else:
                result.update(
                    {
                        'failed': True,
                        'msg': ("Could not detect which major revision of yum is in use, which is required to determine module backend.",
                                "You can manually specify use_backend to tell the module whether to use the yum (yum3) or dnf (yum4) backend})"),
                    }
                )
                # Now fall through to cleanup
    
    

    如代码所示,当执行yum未指定use_backend参数时,ansible会执行setup模块并根据ansible_pkg_mgr来自动判断yum的版本,获取不到则会报错,继续看下该参数的获取过程,找到pkg_mgr.py,关键代码如下:

    ansible/module_utils/facts/system/pkg_mgr.py

        def collect(self, module=None, collected_facts=None):
            facts_dict = {}
            collected_facts = collected_facts or {}
    
            pkg_mgr_name = 'unknown'
            for pkg in PKG_MGRS:
                if os.path.exists(pkg['path']):
                    pkg_mgr_name = pkg['name']
    
            # Handle distro family defaults when more than one package manager is
            # installed or available to the distro, the ansible_fact entry should be
            # the default package manager officially supported by the distro.
            if collected_facts['ansible_os_family'] == "RedHat":
                pkg_mgr_name = self._check_rh_versions(pkg_mgr_name, collected_facts)
    ... ...
    
     def _check_rh_versions(self, pkg_mgr_name, collected_facts):
            if collected_facts['ansible_distribution'] == 'Fedora':
                if os.path.exists('/run/ostree-booted'):
                    return "atomic_container"
                try:
                    if int(collected_facts['ansible_distribution_major_version']) < 23:
                        for yum in [pkg_mgr for pkg_mgr in PKG_MGRS if pkg_mgr['name'] == 'yum']:
                            if os.path.exists(yum['path']):
                                pkg_mgr_name = 'yum'
                                break
                    else:
                        for dnf in [pkg_mgr for pkg_mgr in PKG_MGRS if pkg_mgr['name'] == 'dnf']:
                            if os.path.exists(dnf['path']):
                                pkg_mgr_name = 'dnf'
                                break
                except ValueError:
                    # If there's some new magical Fedora version in the future,
                    # just default to dnf
                    pkg_mgr_name = 'dnf'
            elif collected_facts['ansible_distribution'] == 'Amazon':
                pkg_mgr_name = 'yum'
            else:
                # If it's not one of the above and it's Red Hat family of distros, assume
                # RHEL or a clone. For versions of RHEL < 8 that Ansible supports, the
                # vendor supported official package manager is 'yum' and in RHEL 8+
                # (as far as we know at the time of this writing) it is 'dnf'.
                # If anyone wants to force a non-official package manager then they
                # can define a provider to either the package or yum action plugins.
                if int(collected_facts['ansible_distribution_major_version']) < 8:
                    pkg_mgr_name = 'yum'
                else:
                    pkg_mgr_name = 'dnf'
            return pkg_mgr_name
    
    

    以上代码可以看到当判断系统为红帽系,则会继续判断系统版本信息,当主版本号<8则使用yum,否则使用dnf,这里我们初步判断为麒麟对系统做了某些修改导致无法获取到主版本号。先执行setup获取发行版代号验证下是否执行了上述逻辑:

    # ansible -i hosts node01 -m setup -a "filter=ansible_distribution"
    node01 | SUCCESS => {
        "ansible_facts": {
            "ansible_distribution": "RedHat",
            "discovered_interpreter_python": "/usr/bin/python"
        },
        "changed": false
    }
    
    # ansible -i hosts node01 -m setup -a "filter=ansible_distribution_major_version"
    node01 | SUCCESS => {
        "ansible_facts": {
            "ansible_distribution_major_version": "V7Update6",
            "discovered_interpreter_python": "/usr/bin/python"
        },
        "changed": false
    }
    

    通过setup模块的输出结果可看到系统是判断为redhat发行版,但是通过ansible_distribution_major_version获取到的发行版主版本号为V7Update6, 而和上面判断yum版本的代码关联起来看就会发现问题所在,int(collected_facts['ansible_distribution_major_version']) < 8 中,ansible_distribution_major_version 变量在其初始化的代码中对应为为distribution_version.split('.')[:2][0]的取值,而当系统中获取到的值是V7Update6时,该显然无法满足转换为int的要求。接下来看下V7Update6这个关键字的定义位置,根据经验系统版本相关信息应该在/etc/os-release中:

    ~]# cat /etc/os-release
    NAME="NeoKylin Linux Advanced Server"
    VERSION="V7Update6 (Chromium)"
    ID="neokylin"
    ID_LIKE="fedora"
    VARIANT="Server"
    VARIANT_ID="server"
    VERSION_ID="V7Update6"
    PRETTY_NAME="NeoKylin Linux Advanced Server V7Update6 (Chromium)"
    ANSI_COLOR="0;31"
    CPE_NAME="cpe:/o:neokylin:enterprise_linux:V7Update6:GA:server"
    HOME_URL="https://www.cs2c.com.cn/"
    BUG_REPORT_URL="https://bugzilla.cs2c.com.cn/"
    
    NEOKYLIN_BUGZILLA_PRODUCT="NeoKylin Linux Advanced Server 7"
    NEOKYLIN_BUGZILLA_PRODUCT_VERSION=V7Update6
    NEOKYLIN_SUPPORT_PRODUCT="NeoKylin Linux Advanced Server"
    NEOKYLIN_SUPPORT_PRODUCT_VERSION="V7Update6"
    

    这里果然可以看到VERSION_ID的值被定义为V7Update6,而系统原生发行版中该值是7,我们来看下os-release中对VERSION_ID参数的说明:

    man os-release
    ... ...
    
           VERSION_ID=
               A lower-case string (mostly numeric, no spaces or other characters outside of 0-9, a-z, ".",
               "_" and "-") identifying the operating system version, excluding any OS name information or
               release code name, and suitable for processing by scripts or usage in generated filenames. This
               field is optional. Example: "VERSION_ID=17" or "VERSION_ID=11.04".
    ... ...
    

    根据man文档中的描述,VERSION_ID取值范围为全小写,通常为数值型,不应有空格或其他特殊字符,可包含的字符为0-9a-z._-,那么这里可以看到两个问题, 第一个问题是kylin的VERSION_ID不符合此描述,包含了大写字符,第二个问题是VERSION_ID可以包含a-z字母,但是通常是数值如17,11.04等。 但由于常见发行版都将此处处理为数值型,就导致ansible按照此约定俗成固化了其获取系统版本的方法,并试图将一个字符串转换为int,不能满足当VERSION_ID包含了字母的情况。

    验证结论

    通过以上判断看到VERSION_ID是导致该问题现象的关键,那么我们可以尝试修改一下该参数值,再执行setup看看是否可以正常工作:

    # grep VERSION_ID /etc/os-release
    VERSION_ID="7"
    

    这里我把VERSION_ID修改成了数字7,再执行setup观察ansible_pkg_mgr变量是否能获取到:

    # ansible -i hosts node01 -m setup -a "filter=ansible_pkg_mgr"
    node01 | SUCCESS => {
        "ansible_facts": {
            "ansible_pkg_mgr": "yum",
            "discovered_interpreter_python": "/usr/bin/python"
        },
        "changed": false
    }
    

    可以看到,修改os-release中VERSION_ID为纯数值后,setup就可以正常判断到系统版本,进而可以获取到正确的yum版本了。 通过以上可以看到操作系统中即便是一些不起眼的细枝末节,处理不当也可能引发"连锁反应"。

    展开全文
  • 关于同级目录下模块的引入问题请问为什么报错,sys.path.insert(0,BASE_DIR)将应用包加入系统变量, 便于模块导入sys.path.insert(0,os.path.join(BASE_DIR, 'db_tools'))sys.path.insert(0,os.path.join(BASE_DIR, '...
  • 安装psutil模块报错的解决方法

    千次阅读 2017-01-24 15:29:13
    Loaded plugins: product-id, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Setting up Install Process ...
  • java.lang.NoClassDefFoundError: scala/Product$class at org.apache.spark.sql.types.BooleanType$.<init>(BooleanType.scala:52) at org.apache.spark.sql.types.BooleanType$.<clinit>(Boolean...
  • 文章目录1. 异常处理1.1 常见异常1.2 异常的处理1.2.1 try... 模块简介2.1 广义模块分类2.2 模块导入2.2.1 导入整个模块2.2.2 导入模块中的类或函数2.2.2 导入模块中的所有类和函数2.3 模块的查找路径 1. 异常处理...
  • 今天在安装我自己的一个继承了product模型的form视图时报错另一个模块的一个方法不是对product.product的有效操作。 分析:报错的那个方法是继承product_template_form_view视图添加上去的,然而这个视图被product....
  • /bin/bash -c "(( diff --old-line-format=\"Removed %L\" --new-line-format=\"Added %L\" --unchanged-line-format=\"\" build/make/target/product/vndk/28.txt out/target/product/evk_8mq/obj/PACKAGING/vndk_...
  • 情况1:启动报错 maven包引入问题ClassNotFoundException: org.elasticsearch.client.Cancellable 原因:父pom引入ES 版本了,导致版本冲突 解决方案:修改父pom的ES的版本即可启动成功 情况2:java.lang....
  • 该楼层疑似违规已被系统折叠隐藏此楼查看此楼代码已简化如下:import csvfile_order=[*date*,*product_name*,*product_price*,*evaluation_num*]fields={*date*:*Date*, *product_name*:*Name*, *product_price*:*...
  • "https://img.alicdn.com/tfs/TB1dmALntTfau8jSZFwXXX1mVXa-200-200.png","contentLink":"https://www.aliyun.com/product/mq4iot","title":"微消息队列 MQTT 版","des":" 微消息队列 MQTT 专为物联网(IoT)、移动...
  • 在迁移别人写好的脚本时,发现pychartdir没有导入,脚本执行报错。以下是报错内容: [modps@LGJF-ZYC5-MMSC-WEB02 ~]$ python /opt/aspire/product/modps/mopps/shell/dayreport_linux.py /etc/host.conf: line 1: ...
  • 此项报错主要是构建系统在Android.bp或Android.mk文件中的信息与Manifest清单之间进行构建时一致性检查,要求声明请求使用的libraries跟AndroidManifest.xml中声明的一致,否则将报错。 接下来查看编译报错: error:...
  • 问题:ssis中新建链接管理器,类型选择oledb类型,提供程序选择“Oracle Provider for OLE DB” 后,提示“oraoledbpus11.dll 找不到指定的模块” 解决办法: 先在oracle安装路径下bin目录查找是否有oraoledbpus11....
  • 并且无论怎么样注释公共模块的坐标也无法把公共模块给剔除出去,也可能是自己误操作的原因导致maven刷新坐标不起作用,但是错误原因很明显,所以根据报错去解决问题 io.renren:renren-fast:jar:3.0.0 构建有效模型...
  • 一招解决OpenERP8.0安装旧版模块报错 有喜欢尝鲜的网友开始玩8.0了,可是版本还没发布,社区的很多特别好的模块还没有升级到8,所以经常碰到模块无法安装的问题. No module name osv 网友提出将模块的 from osv im ......
  • 主要解决办法:注释掉renren-fast中pom.xml中oss包 注释后我出现一个问题,启动后依旧会报错,试了很多方法发现注释oss包,idea查看maven依赖这个包依旧存在。 重启idea无效 重启电脑无效 重新下载项目可行,但是会...
  • mathtype安装报错解决

    2022-04-12 23:15:00
    不管怎么样老是报错,尝试了网上很多解决方法,包括b站,包括官网都不行,总结一下错误原因,这里忘截图了。 我的win10 64位pdd买的激活码已经永久激活了,office2019也使用kms也激活了,不过180天需激活一次。然后...
  • 报错如下:-bash: export: `=': not a valid identifier-bash: export: `/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/php/bin': not a valid identifier原因:在编辑 /etc/profile ...
  • 编译Bluetooth报错如下所示: 1、使用mm编译 out/target/product/uis8581a2h10/obj/CONFIG/kati_packaging/dist.mk was modified, regenerating... FAILED: ninja: 'out/target/common/obj/JAVA_LIBRARIES/...
  • 解决办法:刷新idea的缓存后,恢复正常
  • Simulink模块介绍

    千次阅读 2021-06-13 13:07:14
    在库模块浏览器中单击Simulink前面的“+”号, 就能够看到Simulink的模块库, 如图7.2所示。
  • Maven项目多模块打包时报错: [ERROR] 'packaging' with value 'jar' is invalid. Aggregator projects require 'pom' as packaging. @ 指定模块:[unknown-version], poml文件位置, line 4, column 109 @ [ERROR...
  • 一开源项目,多maven模块的。打包报错。 看子模块涉及:mybatis-generator-maven-plugin 看了原因是:和数据库相关的。忘了记录。 大致是这里报错。 <jdbcConnection driverClass="com....
  • Angular 报错解决

    2019-08-23 17:08:11
    当在其他service文件中引入http模块时,页面会报错: ERROR Error: Uncaught (in promise): Error: StaticInjectorError(AppModule)[ToolService -> Http]:   StaticInjectorError(Platform: core)[ToolService...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 10,654
精华内容 4,261
关键字:

product模块报错