Downloading C/C++ language components (Linux / x86_64)

最新推荐文章于 2022-01-03 18:27:18 发布
原创 最新推荐文章于 2022-01-03 18:27:18 发布 · 450 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#c++ #linux #vscode

当尝试在远程服务器上通过vscode构建C++环境时，遇到一个无法取消并持续显示的报告问题。解决方案是下载cpptools-linux.vsix文件，上传到服务器任意文件夹，通过vscode的扩展管理器安装指定路径，最后重新加载vscode即可。

Problem

The report from vscode (as shown in the title) cannot be canceled and keep showing there. This happens when I am trying to build a c++ environment on the server via vscode.

Solution

  • Download cpptools-linux.vsix (click to
    download)     from vscode-cpptools and save it at local.

  • upload cpptools-linux.vsix to an arbitrary folder on server.

  • click Extension - ... (on the upper right corner) - Install from VSIX..., then enter the path where you store your cpptools-linux.vsix on the server.

  • Reload vscode, then done!

Reference

a blog from chenwr2018

最低0.47元/天 解锁文章
hc0112
关注
【agent】AI 数字人构建10：FunASR 1：语音识别C++服务/客户端构建
突围
10-14 413
FunASR已转由ModelScope维护，提供了C++客户端的构建教程。构建过程需要依赖OpenSSL、FFmpeg和ONNX Runtime库，通过CMake进行配置。官方指令和本地构建命令均需指定这些依赖库的路径。构建过程中出现了CMake语法警告和OpenSSL未找到的问题，导致构建失败。日志显示OpenSSL相关路径未正确配置，需检查依赖库路径设置。该问题可能与环境变量或库版本兼容性有关。
Rust最新版安装(v1.78.0+)
mengningyun6826的博客
05-20 1614
Rust最新版安装(v1.78.0+)
vscode c/c++扩展(cpptools v0.22.1)离线安装包
03-25
vscode c/c++扩展(cpptools v0.22.1)Linux和windows离线安装包
ms-vscode.cpptools-1.13.0@linux-x64.vsix
09-16
ms-vscode.cpptools-1.13.0@linux-x64.vsix
cpptools-linux.vsix
07-10
VScode cpptool插件 离线安装包2.8.3 To use the "offline" .vsix (that doesn't download OS-based dependencies on extension activation), download the .vsix that matches your OS and run the "Install from VSIX" command in VS Code. Requirements VS Code 1.43.0 or later. 32-bit Linux is no longer supported. #5346 Changes Version 0.28.3: June 9, 2020
vscode: Downloading package ‘C/C++ language components (Linux / x86_64)‘ Failed.
weixin_44583856的博客
10-23 1062
使用vscode远程连接docker容器，进入容器后报错 Updating C/C++ dependencies... Downloading package 'C/C++ language components (Linux / x86_64)' Failed. Retrying... Failed. Retrying... Failed. Retrying...Waiting 8 seconds... Failed. Retrying...Waiting 15 seconds... Failed.
vscode 解决正在下载程序包“C/C++ language components (Linux / x86_64)” 失败引起的符号找不到问题
热门推荐
chenwr2018的博客
04-16 1万+
1.问题 vscode ssh远程查看代码时，大纲无法罗列函数列表。 根本原因是远程c/c++插件没有安装成功 错误信息如下 正在下载程序包“C/C++ language components (Linux / x86_64)” 失败。正在重试... 失败。正在重试... 失败。正在重试...正在等待 8 秒... 失败。正在重试...正在等待 16 秒... 未能下载 https://go.microsoft.com/fwlink/?linkid=2161011 在阶段 downloadPackage
ubuntu16.04 vscode C/C++安装依赖问题
weixin_42769044的博客
04-12 3920
VSCode 安装C/C++插件后，插件还并不能正常使用。因为插件还有许多依赖包需要联网下载。 如果电脑没有联网的话，或者国内代理问题，将会下载依赖包超时 Updating C/C++ dependencies… Downloading package Error: 或者 Failed at stage: installPackages 这里提供一种直接下载依赖并安装的方法： 1.找到你安装vsc...
VS Code报错解决：Error: end of central directory record signature not found
个人博客
06-18 1万+
早上刚配好远程的Linux开发环境：Windows下使用VS Code远程SSH连接Linux服务器进行开发 然后我在安装C/C++插件的时候出现了报错： ownloading package 'C/C++ language components (Linux / x86_64)' Failed. Retrying... Failed. Retrying... Failed. Retrying....
正在下载c/c++ language components
Sparkling_Y的博客
07-12 1968
参考文章链接：https://blog.csdn.net/Emil_/article/details/118656107 最近Vs Code右下角一直显示“正在下载c/c++ language components”，并且一直卡在1/3的位置。在网上找了很多解决方案，以下是我试过有效的方案，参考开头的链接。 第一步 因为在vs code中直接删除C/C++扩展会失败，说什么IDE在占用，所以在C:\Users\你的用户名.vscode\extensions找到这个文件夹，删除 第二步 点击链接，访问官网，
Linux下的C++标准库
06-04
Linux下的std C++ 标准库 下载后，解压，将文件拷贝到/lib或者/usr/lib目录下，可以解决提示libstdc++。so找不到的问题
eclipsec/c++ linux版本
09-16
64位ecplipse for linux 解压即可安装 简单 方便 亲测可用
cpptools-linux-yy.zip
03-16
Set the "C_Cpp.updateChannel" setting to "Insiders" to auto-install the latest Insiders vsix. Or if that doesn't work (such as in the remote scenario with a version older than 0.26.3-insiders2), manually download the vsix that matches the target OS and run the "Install from VSIX" command in VS Code.
cpptools-win-arm64.vsix
07-13
cpptools-win-arm64.vsix
Downloading package ‘C/C++ language components (Windows)‘ Failed
Haipai1998的博客
08-25 458
##Background 发现vscode没法跳转 ##How to solve 尝试卸载C/C++ exetension，再安装，无果 https://github.com/microsoft/vscode-cpptools/releases ， 下载cpptools-win32.vsix，在VSC编辑界面，Install frome VSIX，解决！
vs识别linux代码失败,vscode 解决正在下载程序包“C/C++ language components (Linux / x86_64)” 失败引起的符号找不到问题...
weixin_29231263的博客
05-12 2138
1.问题vscode ssh远程查看代码时，大纲无法罗列函数列表。根本原因是远程c/c++插件没有安装成功错误信息如下 正在下载程序包“C/C++ language components (Linux / x86_64)” 失败。正在重试... 失败。正在重试... 失败。正在重试...正在等待 8 秒... 失败。正在重试...正在等待 16 秒... 未能下载 https://go.micro...
VSCode使用过程中显示一直下载C/C++ language components
y_m_h的博客
01-03 2245
问题：在使用VSCode开始调试代码时，右下角显示“Downloading C/C++ language components”，无法调试代码，且弹出提醒框“Downloading C/C++ language components” 原因：参考Prevent VS Code extensions from updating automatically一文，VSCode默认设置自动检查是否有extension可以更新，如果有，会自动下载安装更新，但是在使用过程中显示“Downloading C/C++ l
vscode Downloading package ‘C/C++ language components (Windows)‘ Failed.问题解决
fuyuande的博客
12-08 1万+
vscode打开项目后无法使用代码跳转等功能，然后提示一堆错误： Downloading package 'C/C++ language components (Windows)' Failed. Retrying... Failed. Retrying... 下载错误，自动重试多次还是不行。因为网络原因。怀疑无法跳转可能和这个问题相关，Google了一下，网上看到一篇文章，说是可以手动下...
linux安装python依赖：[root@VM-16-5-centos noon]# pip3.6 install sqlalchemy WARNING: Running pip install with root privileges is generally not a good idea. Try `pip3.6 install --user` instead. Collecting sqlalchemy Downloading http://mirrors.tencentyun.com/pypi/packages/5e/50/f63ff7811a8d3367a2c7fae6095f08da20e64e09762e4da1bf05706aefb1/SQLAlchemy-1.4.54-cp36-cp36m-manylinux1_x86_64.manylinux2010_x86_64.manylinux_2_12_x86_64.manylinux_2_5_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.6MB) 100% |████████████████████████████████| 1.6MB 1.8MB/s Collecting greenlet!=0.4.17; python_version >= "3" and (platform_machine == "aarch64" or (platform_machine == "ppc64le" or (platform_machine == "x86_64" or (platform_machine == "amd64" or (platform_machine == "AMD64" or (platform_machine == "win32" or platform_machine == "WIN32")))))) (from sqlalchemy) Downloading http://mirrors.tencentyun.com/pypi/packages/1e/1e/632e55a04d732c8184201238d911207682b119c35cecbb9a573a6c566731/greenlet-2.0.2.tar.gz (164kB) 100% |████████████████████████████████| 174kB 920kB/s Collecting importlib-metadata; python_version < "3.8" (from sqlalchemy) Downloading http://mirrors.tencentyun.com/pypi/packages/a0/a1/b153a0a4caf7a7e3f15c2cd56c7702e2cf3d89b1b359d1f1c5e59d68f4ce/importlib_metadata-4.8.3-py3-none-any.whl Collecting zipp>=0.5 (from importlib-metadata; python_version < "3.8"->sqlalchemy) Downloading http://mirrors.tencentyun.com/pypi/packages/bd/df/d4a4974a3e3957fd1c1fa3082366d7fff6e428ddb55f074bf64876f8e8ad/zipp-3.6.0-py3-none-any.whl Requirement already satisfied: typing-extensions>=3.6.4; python_version < "3.8" in /usr/local/lib/python3.6/site-packages (from importlib-metadata; python_version < "3.8"->sqlalchemy) Installing collected packages: greenlet, zipp, importlib-metadata, sqlalchemy Running setup.py install for greenlet ... error Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-xwpa9djj/greenlet/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-5rl6bxpe-record/install-record.txt --single-version-externally-managed --compile: running install running build running build_py creating build creating build/lib.linux-x86_64-3.6 creating build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/__init__.py -> build/lib.linux-x86_64-3.6/greenlet creating build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/__init__.py -> build/lib.linux-x86_64-3.6/greenlet/platform creating build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_generator.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_stack_saved.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_contextvars.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_greenlet.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_cpp.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_gc.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_extension_interface.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_version.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_throw.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_greenlet_trash.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_weakref.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_tracing.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/__init__.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/leakcheck.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_generator_nested.py -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/test_leaks.py -> build/lib.linux-x86_64-3.6/greenlet/tests running egg_info writing src/greenlet.egg-info/PKG-INFO writing dependency_links to src/greenlet.egg-info/dependency_links.txt writing requirements to src/greenlet.egg-info/requires.txt writing top-level names to src/greenlet.egg-info/top_level.txt reading manifest file 'src/greenlet.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'benchmarks/*.json' no previously-included directories found matching 'docs/_build' warning: no files found matching '*.py' under directory 'appveyor' warning: no previously-included files matching '*.pyc' found anywhere in distribution warning: no previously-included files matching '*.pyd' found anywhere in distribution warning: no previously-included files matching '*.so' found anywhere in distribution warning: no previously-included files matching '.coverage' found anywhere in distribution writing manifest file 'src/greenlet.egg-info/SOURCES.txt' copying src/greenlet/greenlet.cpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet.h -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_allocator.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_compiler_compat.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_cpython_compat.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_exceptions.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_greenlet.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_internal.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_refs.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_slp_switch.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_thread_state.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_thread_state_dict_cleanup.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/greenlet_thread_support.hpp -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/slp_platformselect.h -> build/lib.linux-x86_64-3.6/greenlet copying src/greenlet/platform/setup_switch_x64_masm.cmd -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_aarch64_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_alpha_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_amd64_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm32_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm32_ios.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm64_masm.asm -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm64_masm.obj -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_arm64_msvc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_csky_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_m68k_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_mips_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc64_aix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc64_linux.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_aix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_linux.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_macosx.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_ppc_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_riscv_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_s390_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_sparc_sun_gcc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x32_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x64_masm.asm -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x64_masm.obj -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x64_msvc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x86_msvc.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/platform/switch_x86_unix.h -> build/lib.linux-x86_64-3.6/greenlet/platform copying src/greenlet/tests/_test_extension.c -> build/lib.linux-x86_64-3.6/greenlet/tests copying src/greenlet/tests/_test_extension_cpp.cpp -> build/lib.linux-x86_64-3.6/greenlet/tests running build_ext building 'greenlet._greenlet' extension creating build/temp.linux-x86_64-3.6 creating build/temp.linux-x86_64-3.6/src creating build/temp.linux-x86_64-3.6/src/greenlet gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python3.6m -c src/greenlet/greenlet.cpp -o build/temp.linux-x86_64-3.6/src/greenlet/greenlet.o gcc: error trying to exec 'cc1plus': execvp: 没有那个文件或目录 error: command 'gcc' failed with exit status 1 ---------------------------------------- Command "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-xwpa9djj/greenlet/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-5rl6bxpe-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-xwpa9djj/greenlet/ [root@VM-16-5-centos noon]# python3.6 getSalerInfo3.py Traceback (most recent call last): File "getSalerInfo3.py", line 13, in <module> from sqlalchemy import exc, create_engine, text ModuleNotFoundError: No module named 'sqlalchemy' [root@VM-16-5-centos noon]#报错
最新发布
06-19
<think>我们面对的问题是：在CentOS系统上使用pip3.6安装SQLAlchemy时，依赖包greenlet编译失败，出现gcc或cc1plus错误。编译失败通常是由于系统缺少必要的开发工具或库文件。greenlet是一个需要编译的PythonC扩展模块，因此需要系统具备编译环境和必要的依赖。解决步骤一般包括：1.确保系统已安装开发工具（如gcc,g++,make等）和Python开发头文件。2.安装greenlet可能依赖的系统库（如果有的话）。3.检查错误日志，确定具体缺失的内容。4.根据错误信息安装缺失的组件。针对CentOS系统，我们可以按照以下步骤操作：###步骤1：安装开发工具和Python开发包在CentOS上，我们可以通过yum安装必要的开发工具和Python3开发包。```bashsudoyumgroupinstall"DevelopmentTools"sudoyuminstallpython36-devel#注意：根据你的Python版本，包名可能略有不同，如python3-devel,python36u-devel等```###步骤2：安装其他可能的依赖有时还需要安装一些额外的库，例如：```bashsudoyuminstallepel-release#如果还没有安装epel源sudoyuminstallopenssl-develbzip2-devellibffi-devel```###步骤3：尝试重新安装然后再次尝试安装SQLAlchemy（它会安装greenlet）或者直接安装greenlet：```bashpip3.6installSQLAlchemy```或者单独安装greenlet：```bashpip3.6installgreenlet```###步骤4：如果仍然失败，查看错误日志如果上述步骤后仍然失败，请仔细阅读错误日志。错误日志通常会指出具体缺少什么。比如，如果错误提到`Python.h`文件找不到，那说明Python开发包没有正确安装（即步骤1的python36-devel）。###步骤5：考虑使用wheel如果系统环境确实难以编译，可以考虑使用预编译的wheel。但greenlet的wheel可能不适用于所有平台。我们可以尝试：```bashpip3.6install--only-binary:all:greenlet```或者```bashpip3.6install--only-binary:all:SQLAlchemy```这样pip会尝试下载预编译的二进制包，避免编译过程。###其他注意事项-确保pip版本足够新：`pip3.6install--upgradepip`-如果系统中有多个Python版本，确保pip3.6对应的Python版本正确。如果以上步骤仍然不能解决问题，请提供具体的错误信息，以便进一步排查。###相关问题1.在CentOS上安装Python包时遇到编译错误，通常需要安装哪些基础包？2.如何解决PythonC扩展模块编译失败的问题？3.在缺少编译环境的服务器上如何安装需要编译的Python包？</think>### 解决CentOS中pip3.6安装SQLAlchemy时greenlet编译失败问题 在CentOS上安装SQLAlchemy时遇到greenlet编译错误，通常是由于缺少编译依赖或开发工具导致。以下是系统性的解决方案： #### 1. 安装基础编译工具 ```bash sudo yum groupinstall "Development Tools" sudo yum install gcc-c++ python36-devel ``` 这将安装GCC编译器套件、C++支持及Python 3.6开发头文件[^1]。 #### 2. 解决cc1plus错误 若出现`cc1plus: fatal error: Python.h: No such file or directory`： ```bash sudo yum install python36-devel # 确认已安装 export CFLAGS="-I/usr/include/python3.6m" # 手动指定头文件路径 ``` #### 3. 安装依赖库 ```bash sudo yum install openssl-devel bzip2-devel libffi-devel ``` #### 4. 使用预编译二进制（推荐） ```bash pip3.6 install --only-binary :all: SQLAlchemy # 或单独安装greenlet二进制 pip3.6 install --only-binary greenlet greenlet ``` #### 5. 升级工具链 ```bash sudo yum install centos-release-scl sudo yum install devtoolset-9 # 使用新版GCC scl enable devtoolset-9 bash # 激活新工具链 pip3.6 install SQLAlchemy ``` #### 6. 验证安装 ```bash python3.6 -c "from greenlet import greenlet; print('Success!')" ``` #### 常见错误处理： - **C++编译器缺失**：`sudo yum install gcc-c++` - **内存不足**：添加swap分区或使用`-j1`参数： ```bash pip3.6 install greenlet --global-option="-j1" ``` - **权限问题**：使用`--user`参数或虚拟环境 > 提示：完整日志可通过`pip3.6 install --verbose greenlet 2>&1 | tee build.log`获取，便于精确排查[^2]。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值