1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
All you need to know when hacking (modifying) GNU libsigsegv or when building
it off the Git repository.
Requirements
============
You will need reasonably recent versions of the build tools:
* A C compiler. Such as GNU GCC.
+ Homepage:
https://gcc.gnu.org/
* GNU automake
+ Homepage:
https://www.gnu.org/software/automake/
* GNU autoconf
+ Homepage:
https://www.gnu.org/software/autoconf/
* GNU m4
+ Homepage:
https://www.gnu.org/software/m4/
* Perl
+ Homepage:
https://www.perl.org/
* Either an internet connection or a recent copy of GNU gnulib.
+ Homepage:
https://www.gnu.org/software/gnulib/
And, of course, the packages listed in the DEPENDENCIES file.
Building off the Git repository
===============================
Access to the Git repository is described at
https://savannah.gnu.org/git/?group=libsigsegv .
After fetching the sources from the Git repository, peek at the comments in
autogen.sh, then run
./autopull.sh
./autogen.sh
Then you can proceed with "./configure" as usual.
Each time you want to update the source, do not only "git pull". Instead do
git pull && ./autopull.sh
./autogen.sh
Continuous integration
======================
There are two continuous integrations that regularly build and test
libsigsegv:
* On a Linux/glibc system only:
https://gitlab.com/gnu-libsigsegv/ci-distcheck/pipelines
https://gitlab.com/gnu-libsigsegv/ci-distcheck/-/jobs?scope=finished
This one will catch only the most blatant mistakes.
* On many platforms:
https://github.com/gnu-libsigsegv/ci-check/actions
This one catches platform-specific bugs.
|
