Open bezborodow opened 8 months ago
sudo dnf install autoconf automake
Using autoscan to Create `configure.ac'
autoscan
# Manually check configure.scan.
mv configure.scan configure.ac
autoreconf -i
Now I am getting:
[dbezborodov@damo-hm0 cidrl]$ ./config.status
config.status: error: cannot find input file: `Makefile.in'
From fedpkg --release f38 mockbuild
, got:
...
configure: error: cannot find required auxiliary files: compile missing install-sh
...
Could not execute mockbuild: Failed to execute command.
So, git add install-sh
also.
configure: error: cannot find required auxiliary files: compile missing
Hmmm, rabbit hole... https://stackoverflow.com/questions/3290908/which-files-generated-by-autotools-should-i-keep-in-version-control-repository
Maybe get Fedora packager to run autoreconf for me? Or do some sort of Git hook?
Can it be defined in the spec file to run autoreconf?
It seems like Autoconf stuff should be in the archive. Since I am using GitHub to host release files based on tags, I might need to check the autoconf generated files into version control (something I wish to avoid.) Then... unless the packager can include it for me somehow (without building on the end users machine obviously) or if Github has a hook to include files into the release archive (unlikely?)
Or host my releases somewhere else?
What on Earth?
configure: error: in `/builddir/build/BUILD/cidrl-1.0.0':
configure: error: C compiler cannot create executables
Packaging Tutorial:
Fedora Accounts System
Installing Packager Tools.
sudo dnf install fedora-packager fedora-review
sudo usermod -a -G mock <your_local_username>
Koji uses Kerberos for authentication.
Acquire Kerberos ticket:
fkinit -u <fedora-username>
Say hello:
koji moshimoshi
Renew with:
kinit -R
Spec file: ee6d598
Download source:
spectool -g cidrl.spec
(this is based on the Git tag in the version.)Build the package:
fedpkg --release f38 mockbuild