Zen

Source string Source string

188/10000 · 188

The string is read only.

English Actions
`%build` contains a shell script for the required build steps, such as compiling sources to binaries. Since banner's buildsystem is https://www.gnu.org/software/automake/manual/html_node/Autotools-Introduction.html[Autotools], building it involves running `configure` and `make`. Macros `%configure` and `%make_build` invoke these commands using Fedora's compilation flags and other configuration.
`%install` contains a shell script to copy the results from `%build` into an initially empty _build root_ directory. As banner is using Autotools, macro `%make_install` is used.
`%files` lists the content of the resulting package. Mostly, the files come from the build root created in the `%install`, but documentation and license files can also be added directly from the sources. This section is left empty for now, to be filled later.
The `+%changelog+` documents the changes in each new package version and release. Changelog data can be displayed by `+rpm --query --changelog PACKAGE_NAME+`, which can be useful, for instance, to find out if specific bug and security patches are included. Its value,`+%autochangelog+`, also comes from `rpmautospec`. It populates the changelog from Git commit messages. As we do not have a Git repository, the changelog will be empty.
Lines which are not needed can be commented out with the hash `#`.
You can find more information in the RPM Reference Manual's section https://rpm-software-management.github.io/rpm/manual/spec.html[Spec file format].
Downloading source
We need the source code defined by the `Source` tag, often referred to as the _upstream_ source. This is most easily achieved by using the `spectool` command:
$ spectool -g banner.spec
You should now have the file listed in `Source` in your working directory:
$ ls *.tar.gz
banner-1.3.6.tar.gz
Building the Package
We are ready for the first run to build source, binary and debugging packages. This, and many other tasks, are done with the `fedpkg` tool. The production builds for Fedora are built in the https://koji.fedoraproject.org[Koji] build system, which in turn uses https://rpm-software-management.github.io/mock/[Mock] to manage isolated build environments. To get as close to a production build as is locally possible, we use the `fedpkg mockbuild` command which also invokes Mock:
$ fedpkg --release f{MAJOROSVER} mockbuild
The build environment created by Mock is very basic. It does not include a C compiler by default, so the build will fail. The reason is explained in the output:
checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/banner-6':
configure: error: C compiler cannot create executables
See `config.log' for more details
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.R4Tf16 (%build)
Bad exit status from /var/tmp/rpm-tmp.R4Tf16 (%build)
Additional build tools are defined by adding `BuildRequires:` rows to the specfile. In Fedora, GCC is the standard compiler, so we need to add a row for `gcc`. Autotools also uses `make`, so a row should be added for it, too. Add these lines after `Source`:
BuildRequires: gcc
BuildRequires: make
Run a mockbuild again.
Installing files
The next thing rpm will complain about are unpackaged files, i.e. the files that would be installed in the system, but were not declared as belonging to the package. We need to declare them in the `%files` section. Fixing these errors is an iterative process. After declaring a missing file in the specfile, run `fedpkg` again, then declare the next missing file and so on.
We will go through the file list one by one.
Executable
Installed (but unpackaged) file(s) found:
/usr/bin/banner
This is the executable binary program. `/usr/bin`, like many other system directories, have a xref:packaging-guidelines::RPMMacros.adoc#macros_installation[default rpm macro] defined. The macros should always be used when available, so the executable is listed in `%files` as follows:
%files
%{_bindir}/banner
Man pages
Installed (but unpackaged) file(s) found:
/usr/share/man/man1/banner.1.gz
The Packaging Guidelines have a dedicated section for xref:packaging-guidelines::index.adoc#_manpages[Manpages]. Following its instructions, manpages are list as follows:
%{_mandir}/man1/banner.1.*

Loading…

User avatar None

String added in the repository
checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/banner-6':
configure: error: C compiler cannot create executables
See `config.log' for more details
checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/banner-6':
configure: error: C compiler cannot create executables
See `config.log' for more details
6 months ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Multiple failing checks

Following checks are failing:
Unchanged translation: Spanish, Chinese (Simplified Han script)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: delimited block -
Flags
no-wrap, placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./@]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?", read-only
Source string location
./pages/Packaging_Tutorial_1_banner.adoc:198
String age
6 months ago
Last updated
6 months ago
Source string age
6 months ago
Translation file
pot/master/pages/Packaging_Tutorial_1_banner.pot, string 47