buildroot

制作MySQL RPM安装包Spec

我是研究僧i 提交于 2020-01-07 12:01:11
适用环境: 数据库版本:MySQL 5.7.26 操作系统:CentOS 7 制作思路: 将数据库初始化和配置工作放到安装脚本中方便定制: 1、打包MySQL应用目录 2、不自动生成配置文件 3、不自动生成数据目录 4、不自动初始化数据 Spec代码: # ========================================= # # MySQL参数配置 # mysql源码路径 # 源码包版本 %global src_base mysql %global version 5.7.26 %global src_dir %{src_base}-%{version} %global cmake_bin /home/rpmbuilder/cmake-3.16.2-Linux-x86_64/bin/cmake Name: %{src_base} Version: %{version} # 安装版本 Release: 1 # 安装包介绍 Summary: MySQL Server # 遵循协议 License: GPLv2 # 打包需要 # BuildRequires: cmake /sbin/useradd /sbin/groupadd /bin/bash /bin/sh /bin/chown # 安装需要 # Requires: ncurses ncurses-devel

Issue importing subprocess32

╄→гoц情女王★ 提交于 2020-01-05 07:12:33
问题 I am trying to install subprocess32 with my python 2.7 installation via buildroot. It appeared to install correctly but when I import it on the embedded system I get an error: >>> import subprocess32 /usr/lib/python2.7/site-packages/subprocess32.py:472: RuntimeWarning: The _posixsubprocess module is not being used. Child process reliability may suffer if your pro gram uses threads. "program uses threads.", RuntimeWarning) Following this path I tried to import _posixsubprocess import

制作MySQL RPM安装包Spec

你离开我真会死。 提交于 2020-01-04 19:48:06
适用环境: 数据库版本:MySQL 5.7.26 操作系统:CentOS 7 制作思路: 将数据库初始化和配置工作放到安装脚本中方便定制: 1、打包MySQL应用目录 2、不自动生成配置文件 3、不自动生成数据目录 4、不自动初始化数据 Spec代码: # ========================================= # # MySQL参数配置 # mysql源码路径 # 源码包版本 %global src_base mysql %global version 5.7.26 %global src_dir %{src_base}-%{version} %global cmake_bin /home/rpmbuilder/cmake-3.16.2-Linux-x86_64/bin/cmake Name: %{src_base} Version: %{version} # 安装版本 Release: 1 # 安装包介绍 Summary: MySQL Server # 遵循协议 License: GPLv2 # 打包需要 # BuildRequires: cmake /sbin/useradd /sbin/groupadd /bin/bash /bin/sh /bin/chown # 安装需要 # Requires: ncurses ncurses-devel

How to pass extra custom ./configure autotools options to a Buildroot package?

纵然是瞬间 提交于 2020-01-02 16:54:03
问题 E.g., I want to add the options --enable-foo --enable-bar to a ./configure command. Many ./configure options can be set indirectly through BR2_ configs, but many software have so many options that it would be infeasible to have one BR2_ config for every possible ./configure option. Is there a general mechanism that works for all autotools packages? 回答1: I think there is no current general method as of 2017.02, since package/pkg-autotools.mk contains: # Configure package for target define $(2)

How to pass extra custom ./configure autotools options to a Buildroot package?

痞子三分冷 提交于 2020-01-02 16:53:17
问题 E.g., I want to add the options --enable-foo --enable-bar to a ./configure command. Many ./configure options can be set indirectly through BR2_ configs, but many software have so many options that it would be infeasible to have one BR2_ config for every possible ./configure option. Is there a general mechanism that works for all autotools packages? 回答1: I think there is no current general method as of 2017.02, since package/pkg-autotools.mk contains: # Configure package for target define $(2)

systemd/udev dependency failure when auto mounting separate partition during startup

删除回忆录丶 提交于 2020-01-01 09:05:11
问题 EDIT: This occurs when I am trying to use a separate partition with ANY mount point, not just /var . I am using Buildroot to build an embedded linux system. I am trying to use a separate partition for /var, but this occurs for ANY mount point. My init system is systemd, udev for device management. I've edited my fstab to: # <file system> <mount pt> <type> <options> <dump> <pass> /dev/root / ext2 rw,noauto 0 1 /dev/mmcblk0p4 /var ext2 defaults 0 2 proc /proc proc defaults 0 0 devpts /dev/pts

Unrecognized option: -o Could not create the Java virtual machine

≯℡__Kan透↙ 提交于 2019-12-25 02:06:47
问题 I've got an unusual build error when using Buildroot to create an image for my Phidget SBC. It's unusual because it occurs ONLY on my development laptop and NOT on my general use laptop even though I am using EXACTLY the same Builroot environment as published by Phidgets themselves. When I try to create my Buildroot image I get the following error when it attempts to compile GNU classpath: Making all in tools make[2]: Entering directory `/home/xxxx/buildroot_phidgetsbc/buildroot-phidgetsbc_1

Buildroot - System doesn't boot - /dev/ttyS0 no such file

北战南征 提交于 2019-12-25 00:52:50
问题 I m using buildroot to create a filesystem for a Raspberry Pi. I have uncompressed the filesystem image in the Root partition of my SD card but I can't boot the operative system. I get the following errors: Can't open /dev/null no such file or directory Can't open /dev/ttyS0 no such file or directory Which line of the configuration tool should I enable or modify in order to boot the system? EDIT I've followed the steps provided by Thomas Petazzoni and used a preconfigured version of buildroot

Buildroot: Build only one package as both shared and static lib, all others shared only

只愿长相守 提交于 2019-12-24 09:55:02
问题 buildroot offers to possibility to build only static, only shared, or both shared and static libs of the selected packages. The assigned configuration elements are BR2_STATIC_LIBS , BR2_STATIC_LIBS , and BR2_SHARED_STATIC_LIBS . Question: Is it possible to build both a shared and static lib for one package only , while building only shared libs for all the other packages ? The one project which I want a static lib of would be an autotools-based package. My effort: I did read the manual, but

How to install packages or natively compile package on a minimal Linux kernel compiled with Buildroot

耗尽温柔 提交于 2019-12-24 00:28:51
问题 I enconter a problem I hope to be solved quickly. I have grace to BUILDROOT compile a Linux zImage Kernel, build a rootfs, have a bootloader, so everething is right. But at the boot, the system is so minimal that i don't have got some package manager like apt-get, yum, etc.... Despite the fact i've got the network (wget is possible), I don't know how to have a simply gcc in my host (Buildroot don't permit to compile gcc anymore) or more simply a package manager. It is so boring to cross