Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
125 commits
Select commit Hold shift + click to select a range
d960571
Starting incremental index support work
Sep 30, 2020
ac46fb2
Initial checking of v1.5 fssim code
DavidAPease Oct 1, 2020
13f43ef
Corrected typos in README files
DavidAPease Oct 1, 2020
5b6b5e4
Updates to README files
DavidAPease Oct 1, 2020
076ff6d
README.md in docs dir, small fixes to help messages
DavidAPease Oct 4, 2020
3dc47e1
typos in README
DavidAPease Oct 4, 2020
d35cd78
typos in README
DavidAPease Oct 4, 2020
b846d27
Make master branch as a tree for version 2.5 dev
Nov 6, 2020
26869c8
Update build-centos7.yml
Nov 13, 2020
2e117ad
Fix warning on message checker
Nov 13, 2020
be1b873
Fix build break in FreeBSD
piste2750 Dec 1, 2020
fffa125
Handle write-perm on LOCATE correctly (#233)
Dec 9, 2020
58cacdd
Fix check build (#238)
Jan 18, 2021
dd08870
Support HP drives on the CAM backend (#239)
piste2750 Jan 18, 2021
b2d8298
Handle the no xattr destination on ltfs_ordered_copy
softloft38p-michael Feb 3, 2021
f2769f2
Honor `--keep-tree` for single file copies (#244)
softloft38p-michael Feb 3, 2021
d874e20
Support another Quantum drive (#247)
Feb 8, 2021
3b5acac
Fix remaining capacity handling of HP LTO6 (#248)
Feb 8, 2021
aacc20c
Document required reboot for modprobe.d settings to take effect. Fixe…
softloft38p-michael Feb 11, 2021
30829ef
Fetch timeout values from drive if available (#253)
Feb 26, 2021
1fbde52
Introduce generic logselect issue I/F via VEA (#258)
Mar 10, 2021
4be4c40
Add another Quantum's LTO 6 into the list (#259)
Mar 11, 2021
0bfb629
Fix plugin load error for the itdtimg backend (#260)
Mar 13, 2021
16a08be
Introduce generic MAM fields capture I/F (#261)
Mar 13, 2021
53a9406
Fix the build break of the lin_tape backend (#263)
Mar 27, 2021
3071374
Fix the drive type of Quantum LTO6 (#267)
Apr 9, 2021
7a2b257
Remove AC_CONFIG_MACRO_DIR from configure.ac (#274)
May 6, 2021
52594c6
Update the README on master (#275)
May 6, 2021
0a51e3c
Handle 0-byte file on tape in `ltfs-ordered_copy` (#276)
May 10, 2021
a949a12
Wipe the plugin structure before loading a plugin. (#278)
xloem May 11, 2021
cb7ce47
Update ISO status
May 11, 2021
f806d70
Refresh obsoleted macros for newer autotools (#277)
rzerres May 14, 2021
55b0f8e
Refactor the XML parser to return more graceful infomation (#281)
May 17, 2021
f4cf6f3
Modify the description for the spec
May 17, 2021
b2a5b50
Fix a build break on FreeBSD (#284)
piste2750 May 20, 2021
d08cb44
Introduce Recommended access order (RAO) via EA (#288)
y-sasn May 27, 2021
54a0c5c
Refactor RAO functions (#293)
Jun 10, 2021
4eafde6
Handle Quantum type-B drive (#296)
piste2750 Jun 21, 2021
f057535
Fix bugs to fetch supported drive list (#298)
piste2750 Jun 22, 2021
ab7d0f0
Experimental support of Tandberg drives (#299)
Jun 22, 2021
0fae6d8
Correct compare length of vendor IDs (#301)
Jun 25, 2021
18ad9cd
Log the generation of index at mount/unmount (#304)
Aug 4, 2021
e1bca53
Update the status of the spec 2.5
Aug 5, 2021
4b2e744
Handle unupdated MAM tape at write perm (#307)
Aug 10, 2021
c3de5ad
Introduce the low level index tool (#309)
piste2750 Aug 19, 2021
27e5ea1
Fix fallback to pkg-config (#310)
swt2c Aug 23, 2021
33dbad1
Correct ltfs_check_medium handling of partitions ending in data+fm (#…
linnemannr Sep 6, 2021
618859c
Modify build configuration (#311)
Sep 10, 2021
22be24e
Enable code scan by CodeQL (Experimental)
Sep 28, 2021
226e76b
Update CodeQL workflow
Sep 28, 2021
60ff79f
Install prereqs at CodeQL scan
Sep 28, 2021
a172456
Use apt-get in the CodeQL job
Sep 28, 2021
b446455
Fix command error on the CodeQL job
Sep 28, 2021
c5a0982
Run apt-get on root in the CodeQL job
Sep 28, 2021
4818e0a
Add dummy icu-config for the CodeQL job
Sep 28, 2021
b5fd43a
Test for the CodeQL job
Oct 1, 2021
2d7fc01
Test for the CodeQL job #2
Oct 1, 2021
e845fef
Anyway, just need to make the tree for CodeQL
Oct 1, 2021
bc5ce0e
Add autobuild script for CodeQL analysis
Oct 1, 2021
39fdc49
Fix autobuild script for CodeQL analysis
Oct 1, 2021
60b2024
Use default built-in queries
Oct 1, 2021
9de617a
Use default built-in queries
Oct 1, 2021
55656a7
Return error when index write on DP is failed at sync (#316)
Oct 18, 2021
6cdbad0
Fix potential buffer overrun (#317)
Oct 18, 2021
4c3a760
Fix a toctou race condition (#318)
Oct 18, 2021
b193b45
Update supporting drives.
Nov 8, 2021
77e59f2
Tiny correction for sync fail (#319)
Nov 19, 2021
0a82123
Support `ltfs.hash.*` EAs (#320)
Nov 22, 2021
1713126
Fix a few vulnerabilities (#323)
Dec 17, 2021
93de9d8
Fix a potential buffer overflow (#324)
Dec 17, 2021
ae18480
Fix build break on FreeBSD (#326)
piste2750 Dec 24, 2021
3f2e5c6
Fix link failure in Debian11 (#329)
Jan 13, 2022
42c0871
Introduce Index mount mode (#330)
Jan 26, 2022
376a25b
Fix check build break on CentOS8
Feb 3, 2022
8064838
Format time enhancement on the LTO9 drive (#335)
Feb 15, 2022
a4cd6af
Export a couple of utility functions (#338)
Feb 19, 2022
98c6c6b
Move to Rocky Linux
Feb 21, 2022
ec78f5d
Fix the description of the capture index option in man page of ltfs (…
dabiged Feb 22, 2022
e62d21c
Fix link breakages in README (#340)
Feb 28, 2022
af2aeab
Fix typos of homebrew in readme (#342)
qayshp Mar 11, 2022
ffc63ac
Fix a crash at parsing an extended attribute (#341)
Mar 8, 2022
3919f56
Silence warnings from autoconf 2.70 and higher (#344)
manu0401 Mar 25, 2022
7fe537d
Fix undefined symbol error on NetBSD/amd64 (#346)
manu0401 Mar 25, 2022
98e8854
Fix filehandle corruption on LP64 (#345)
manu0401 Mar 25, 2022
3b26f03
Return an error without issuing GRAO command in LTO9HH (#348)
Apr 6, 2022
b8e7384
Improve error position detention at WRITE PERM (#357)
Aug 10, 2022
044a0e3
Correct a message ID
Aug 10, 2022
8a0f116
Correct a message ID
Aug 10, 2022
bf58bc3
Cleanup language on READMEmd. (#362)
dabiged Oct 3, 2022
2d7d642
Modify linker flags (#366)
Nov 16, 2022
56572c5
Install config_file.h as a header (#368)
Nov 19, 2022
d7230c8
Fix a type mismatch bug in ltfs_ordered_copy (#372)
Dec 7, 2022
d8d72a7
Fix gcc error message by unexpected extra options (#375)
lshw Dec 7, 2022
2db929b
Replace specifying options for ICU from icu-config to pkg-config (#376)
lshw Dec 8, 2022
82c8d9a
Make it work for HP Ultrium 3000 on FreeBSD (#379)
micronn Dec 25, 2022
f95a9a4
Add a few headers to be installed (#386)
Mar 13, 2023
b80b20c
Added warning to show fuse main error codes
May 19, 2023
cccf09e
Solving syntax error
May 19, 2023
7edac12
Changed message of warning
amissael95 May 26, 2023
a1f435f
Reverting change on ltfs_parse_options
Jun 19, 2023
9fcc77e
Reverting change
Jun 19, 2023
efb2eb8
Merge branch 'fuse-main-log-addition' of https://github.com/amissael9…
Jun 19, 2023
178a782
Handle one-shot false `good` against TUR at failover process (#410)
Jun 21, 2023
6e4f79f
Add support for FreeBSD to ltfs_ordered_copy (#380)
micronn Jun 23, 2023
2e41bf5
Merge pull request #404 from amissael95/fuse-main-log-addition
juliocelon Jun 26, 2023
2897a5a
bugfix: cannot mount LTFS tapes under Rocky Linux with lin_tape drive…
richard42 Jun 27, 2023
66f0b28
Treat extended attribute ltfs.mediaPool.name like a virtual extended …
richard42 Jun 29, 2023
a7916bf
Recursive protection to _take_dump() (#412)
ochomenosocho Jul 17, 2023
7681d4d
Fix a memory leak at `tape_read_attr()` (#415)
Aug 24, 2023
b9cf767
Rebranding from Spectrum Archive to Storage Archive and adding copyri…
juliocelon Aug 31, 2023
18ae70c
Linux Jaguar 7 Tape and TS1170 Drive Support (#423)
jgreen24 Aug 25, 2023
82024a9
Fix `ltfs -o device_list` exit code (#429)
diamant3 Nov 27, 2023
f36304e
Jag7 fix (#435)
jgreen24 Nov 27, 2023
5175c4c
Create hba_report.md
May 17, 2024
972c610
Update hba_report.md
May 17, 2024
cbed7ef
freebsd: add missing semicolon in cam_tc (#426)
kev009 May 22, 2024
102dcb4
Fix the build break on FreeBSD 12 (#396)
Krishhhnaa May 22, 2024
22edc44
Introduce the structures for incremental index for format spec 2.5 (#…
May 22, 2024
d19dfcf
Fix potential use after free issues (#462)
May 23, 2024
06367df
Change the `sync` behavior to fit the LTFS format Spec 2.5 (#461)
May 24, 2024
8c8f6cc
Introduce incremental index write down in XML format (#466)
Jun 21, 2024
29b6f34
Remove CentOS7 and RHEL7 Build for Travis in master branch (#477)
juliocelon Jul 31, 2024
2c0cd5a
Changed skip flags when calling _ltfs_search_index_wp (#493)
amissael95 Jan 30, 2025
10769a2
Update CONTRIBUTING.md
XV02 May 28, 2025
b2c1479
Resolve merge conflicts with origin v2.4.8-windows-support
XV02 Mar 18, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
71 changes: 71 additions & 0 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,3 +27,74 @@ __Some things that will increase the chance that your pull request is accepted__

* Follow our [coding style guide](../docs/CODE_OF_CONDUCT.md).
* Write a good commit message.

# Branch Naming Conventions
The structure and design conventions are based mainly on the “Conventional Branch” concept and the team’s current work process.

## Purpose
1. Purpose-driven Branch Names: Each branch name clearly indicates its purpose, making it easy for all developers to understand what the branch is for.
2. Integration with CI/CD: By using consistent branch names, it can help automated systems (like Continuous Integration/Continuous Deployment pipelines) to trigger specific actions based on the branch type.
3. Better type and version control: Branches are related to a specific type of change in the code and the version that is being worked on, allowing for a much better backtracking.

## Basic Rules
- Naming structure:
`<type>/<description>`
- Naming prefixes (Types):
- feature/: For new features (e.g., feature/add-login-page).
- fix/: For general fixes or code correcting.
- update/: For code upgrade or non-breaking code refactoring.
- chore/: For non-code tasks like dependency, docs updates (e.g., chore/update-dependencies).
- release/: For branches preparing a release (e.g., release/v1.2.0).
- Use Lowercase Alphanumeric and Hyphens: Always use lowercase letters (a-z), numbers (0-9), and hyphens to separate words. Avoid special characters, underscores, or spaces.
- No Consecutive or Trailing Hyphens: Ensure that hyphens are used singly, with no consecutive hyphens (feature/new--login) or at the end (feature/new-login-).
- Keep It Clear and Concise: The branch name should be descriptive yet concise, clearly indicating the purpose of the work.
- Include Ticket Numbers: If applicable, include the ticket number from your project management tool to make tracking easier. For example, for a ticket issue-123, the branch name could be feature/issue-123-new-login.

## General Project Structure
```
main
├── release/v1.x.x
│ ├── feature/lorem-ipsum
│ └── fix/ipsum-dolor
├── release/v2.x.x
│ └── chore/dolor-sit
└── release/v3.x.x
├── update/sit-amet
├── feature/amet-consectetur
└── chore/consectetur-adipiscing
```
- main: This branch should only contain working versions completely tested and only receive pull requests from finalized release branches. All new release/ branches must come from this one.
- release: The creation of these branches should be done from the last version of main when created. Only this branches can make pull requests to main.
- Other branches: All working branches should come from a release branch. These are the only ones that should receive direct commits from changes made by development staff. These branches should only do PR to the active release branch.

# Commits Naming Conventions
The structure and design conventions are based mainly on the “Conventional Branch” concept and the team’s current work process.

## Purpose
1. Automatically generating CHANGELOGs: When the commits are concise, and precise changelogs can be automated or semi-automated from the commit history.
2. Communicating the nature of changes to everyone: Being able to understand the type of changing by just looking at a name and understanding the basics of a commit just by the title is useful in analysis and backtrack situations.
3. Building code habits and good practices: Maintaining structured commits also leads to more precise coding practices and coherent code changes.

## Basic Rules
- Naming structure:
```
<type>: <description>

[optional body]
```
- Naming prefixes (Types):
- fix: A commit of the type fix patches a bug in your codebase.
- feat: A commit of the type feat introduces a new feature to the codebase
- <type>!: A commit that appends a ! after the type introduces a breaking change. A breaking change can be part of commits of any type.
- update: A commit of type update changes existing code or refactors functions without changing functionality of adding features in your codebase.
- build: A commit of type build changes build process in your codebase.
- docs: A commit of type docs is for creation or updating documentation in your codebase.
- chore: A commit of type chore is for every other minor task in your codebase.
- Commits must be prefixed with a type, which consists of a noun, feat, fix, etc., followed by the optional !, and required terminal colon and space.
- A description must immediately follow the colon and space after the type prefix. The description is a short summary of the code changes, e.g., fix: array parsing issue when multiple spaces were contained in string.
- A longer commit body may be provided after the short description, providing additional contextual information about the code changes. The body must begin one blank line after the description.
- A commit body is free-form and may consist of any number of newline separated paragraphs.

# Bibliography
[1] “Conventional Branch,” Conventional Branch, 2025. https://conventional-branch.github.io/ (accessed 2025).</br>
[2] “Conventional Commits,” Conventional Commits. https://www.conventionalcommits.org/en/v1.0.0/ (accessed 2025).
15 changes: 15 additions & 0 deletions .github/ISSUE_TEMPLATE/hba_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
name: HBA report
about: Report a HBA that is working on the specific enviroment
assignees: piste-jp-ibm
lebels: HBA Report
title: HBA list request

---

**Fill in the informatio of HBA and OS**

| HBA type | Vendor | I/F type (FC, SAS etc) | OS | LTFS version or commit hash | Note |
| -------- | ------ | ---------------------- | --- | --------------------------- | ---- |
| | | | | | |

125 changes: 106 additions & 19 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,13 @@
![GH Action status](https://github.com/LinearTapeFileSystem/ltfs/workflows/CentOS7%20Build%20Job/badge.svg?branch=master)
[![BSD License](http://img.shields.io/badge/license-BSD-blue.svg?style=flat)](LICENSE)

# Linear Tape File System (LTFS)
# About this branch

Linear Tape File System (LTFS) is a filesystem to mount a LTFS formatted tape in a tape drive. Once LTFS mounts a LTFS formatted tape as filesystem, user can access to the tape via filesystem API.
This is the `master` branch of the LTFS project. At this time, this branch is used for version 2.5 development. So it wouldn't be stable a little. Please consider to follow the tree on `v2.4-stable` branch if you want to use stable codes.

# What is the Linear Tape File System (LTFS)

The Linear Tape File System (LTFS) is a filesystem to mount a LTFS formatted tape in a tape drive. Once LTFS mounts a LTFS formatted tape as filesystem, user can access to the tape via filesystem API.

Objective of this project is being the reference implementation of the LTFS format Specifications in [SNIA](https://www.snia.org/tech_activities/standards/curr_standards/ltfs).

Expand Down Expand Up @@ -103,9 +107,91 @@ These instructions will get you a copy of the project up and running on your loc
| Quantum | LTO8 (Only Half Height) | T.B.D. |
| Quantum | LTO9 (Only Half Height) | T.B.D. |

## Installing
## LTFS Format Specifications

LTFS Format Specification is specified data placement, shape of index and names of extended attributes for LTFS. This specification is defined in [SNIA](https://www.snia.org/tech_activities/standards/curr_standards/ltfs) first and then it is forwarded to [ISO](https://www.iso.org/home.html) as ISO/IEC 20919 from version 2.2.

The table below show status of the LTFS format Specification

| Version | Status of SNIA | Status of ISO |
|:-------:|:---------------------------------------------------------------------------------------------------------------------:|:--------------------------------------------------------------------:|
| 2.2 | [Published](http://snia.org/sites/default/files/LTFS_Format_2.2.0_Technical_Position.pdf) | [Published as `20919:2016`](https://www.iso.org/standard/69458.html) |
| 2.3.1 | [Published](https://www.snia.org/sites/default/files/technical_work/LTFS/LTFS_Format_2.3.1_TechPosition.PDF) | - |
| 2.4 | [Published](https://www.snia.org/sites/default/files/technical_work/LTFS/LTFS_Format_2.4.0_TechPosition.pdf) | - |
| 2.5.1 | [Published](https://www.snia.org/sites/default/files/technical-work/ltfs/release/SNIA-LTFS-Format-2-5-1-Standard.pdf) | [Published as `20919:2021`](https://www.iso.org/standard/80598.html) |

# How to use the LTFS (Quick start)

This section is for a person who already has a machine with the LTFS installed. Instructions on how to use the LTFS is also available on [Wiki](https://github.com/LinearTapeFileSystem/ltfs/wiki).

## Step1: List tape drives

`# ltfs -o device_list`

The output is as follows. You have 3 drives in this example and you can use "Device Name" field, like `/dev/sg43` in this case, as the argument of ltfs command to mount the tape drive.

```
50c4 LTFS14000I LTFS starting, LTFS version 2.4.0.0 (10022), log level 2.
50c4 LTFS14058I LTFS Format Specification version 2.4.0.
50c4 LTFS14104I Launched by "/home/piste/ltfsoss/bin/ltfs -o device_list".
50c4 LTFS14105I This binary is built for Linux (x86_64).
50c4 LTFS14106I GCC version is 4.8.5 20150623 (Red Hat 4.8.5-11).
50c4 LTFS17087I Kernel version: Linux version 3.10.0-514.10.2.el7.x86_64 (mockbuild@x86-039.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Mon Feb 20 02:37:52 EST 2017 i386.
50c4 LTFS17089I Distribution: NAME="Red Hat Enterprise Linux Server".
50c4 LTFS17089I Distribution: Red Hat Enterprise Linux Server release 7.3 (Maipo).
50c4 LTFS17089I Distribution: Red Hat Enterprise Linux Server release 7.3 (Maipo).
50c4 LTFS17085I Plugin: Loading "sg" tape backend.
Tape Device list:.
Device Name = /dev/sg43, Vender ID = IBM , Product ID = ULTRIUM-TD5 , Serial Number = 9A700L0077, Product Name = [ULTRIUM-TD5] .
Device Name = /dev/sg38, Vender ID = IBM , Product ID = ULT3580-TD6 , Serial Number = 00013B0119, Product Name = [ULT3580-TD6] .
Device Name = /dev/sg37, Vender ID = IBM , Product ID = ULT3580-TD7 , Serial Number = 00078D00C2, Product Name = [ULT3580-TD7] .
```

## Step2: Format a tape

As described in the LTFS format specifications, LTFS uses the partition feature of the tape drive. This means you can't use a tape just after you purchase a tape. You need format the tape before using it on LTFS.

To format a tape, you can use `mkltfs` command like

`# mkltfs -d 9A700L0077`

In this case, `mkltfs` tries to format a tape in the tape drive `9A700L0077`. You can use the device name `/dev/sg43` instead.

## Step3: Mount a tape through a tape drive

After you prepared a formatted tape, you can mount it through a tape drive like

`# ltfs -o devname=9A700L0077 /ltfs`

In this command, the ltfs command will try to mount the tape in the tape drive `9A700L0077` to `/ltfs` directory. Of course, you can use a device name `/dev/sg43` instead.

If the mount process is successfully done, you can access to the LTFS tape through `/ltfs` directory.

You must not touch any `st` devices while ltfs is mounting a tape.

## Step4: Unmount the tape drive

You can use following command when you want to unmount the tape. The ltfs command try to write the current meta-data to the tape and close the tape cleanly.

`# umount /ltfs`

One thing you need to pay attention to here is, that the unmount command continues to work in the background after it returns. It just initiates a trigger to notify the the ltfs command of the unmount request. Actual unmount is completed when the ltfs command is finished.

## The `ltfsee_ordered_copy` utility

The [`ltfsee_ordered_copy`](https://github.com/LinearTapeFileSystem/ltfs/wiki/ltfs_ordered_copy) is a program to copy files from source to destination with LTFS order optimization.

It is written in python and it can work with both python2 and python3 (Python 2.7 or later is strongly recommended). You need to install the `pyxattr` module for both python2 and python3.

# Building the LTFS from this GitHub project

These instructions will get a copy of the project up and running on your local machine for development and testing purposes.

## Prerequisites for build

Please refer [this page](https://github.com/LinearTapeFileSystem/ltfs/wiki/Build-Environments).

### Build and install on Linux
## Build and install on Linux

```
./autogen.sh
Expand All @@ -120,7 +206,7 @@ In some systems, you might need `sudo ldconfig -v` after `make install` to load

#### Parameter settings of the sg driver

LTFS uses the sg driver by default. You can improve reliability to change parameters of the sg driver below.
### Buildable Linux distributions

```
def_reserved_size=1048576
Expand Down Expand Up @@ -217,9 +303,9 @@ Currently, automatic build checking is working on GitHub Actions and Travis CI.

For Ubuntu20.04 and Debian10, dummy `icu-config` is needed in the build machine. See Issue [#153](https://github.com/LinearTapeFileSystem/ltfs/issues/153).

### Build and install on OSX (macOS)
## Build and install on OSX (macOS)

#### Recent Homedrew system setup
### Recent Homebrew system setup

Before build on macOS, you need to configure the environment like below.

Expand All @@ -230,15 +316,15 @@ export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig:/usr/local/opt/libxml
export PATH="$PATH:$ICU_PATH:$LIBXML2_PATH"
```

#### Old Homedrew system setup
### Old Homebrew system setup
Before build on OSX (macOS), some include path adjustment is required.

```
brew link --force icu4c
brew link --force libxml2
```

#### Building LTFS
### Building LTFS
On OSX (macOS), snmp cannot be supported, you need to disable it on configure script. And may be, you need to specify LDFLAGS while running configure script to link some required frameworks, CoreFundation and IOKit.

```
Expand All @@ -250,13 +336,13 @@ make install

`./configure --help` shows various options for build and install.

#### Buildable systems
#### Buildable macOS systems

| OS | Xcode | Package system | Status |
|:-: |:-: |:-: |:-: |
| macOS 10.14.6 | 11.3 | Homebrew | Probably OK |

### Build and install on FreeBSD
## Build and install on FreeBSD

Note that on FreeBSD, the usual 3rd party man directory is /usr/local/man. Configure defaults to using /usr/local/share/man. So, override it on the command line to avoid having man pages put in the wrong place.

Expand All @@ -269,9 +355,10 @@ make install

#### Buildable versions

| Version | Arch | Status |
|:-: |:-: |:-: |
| 11 | x86_64 | OK |
| Version | Arch | Status |
|:-------:|:-------:|:------------------------------:|
| 11 | x86\_64 | OK - Not checked automatically |
| 12 | x86\_64 | OK - Not checked automatically |

### Build and install on NetBSD

Expand All @@ -284,11 +371,11 @@ make install

#### Buildable versions

| Version | Arch | Status |
|:-: |:-: |:-: |
| 8.1 | amd64 | OK |
| 8.0 | i386 | OK |
| 7.2 | amd64 | OK |
| Version | Arch | Status |
|:-------:|:-----:|:------------------------------:|
| 8.1 | amd64 | OK - Not checked automatically |
| 8.0 | i386 | OK - Not checked automatically |
| 7.2 | amd64 | OK - Not checked automatically |

## Contributing

Expand Down
6 changes: 3 additions & 3 deletions autogen.sh
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,6 @@ else
libtoolize
fi

autoconf
autoheader
automake --add-missing --copy
autoconf || echo "Ignore warning"
autoheader || echo "Ignore warning"
automake --add-missing --copy || echo "Ignore warning"
Loading
Loading