mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <>
Cc: Alexander Dahl <>
Subject: Re: [ptxdist] [APPLIED] doc: Fix a typo
Date: Wed, 16 Jun 2021 12:35:54 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Thanks, applied as 2a66f94f3e114696ee9bdbcf171cc0c3f7f9311c.


[sent from post-receive hook]

On Wed, 16 Jun 2021 12:35:53 +0200, Alexander Dahl <> wrote:
> Found with `codespell -i 3 -w doc/*.rst`
> Signed-off-by: Alexander Dahl <>
> Message-Id: <>
> Signed-off-by: Michael Olbrich <>
> diff --git a/doc/dev_add_new_pkgs.rst b/doc/dev_add_new_pkgs.rst
> index 4ae2765c2ce9..0dbc7a266ea8 100644
> --- a/doc/dev_add_new_pkgs.rst
> +++ b/doc/dev_add_new_pkgs.rst
> @@ -960,7 +960,7 @@ In our example there is a hidden dependency to the math library
>  ``libm``. Our new package was built successfully, because the linker was
>  able to link our binaries against the ``libm`` from the toolchain. But
>  in this case the ``libm`` must also be available in the target’s root
> -filesystem to fulfil the run-time dependency: We have to force PTXdist to
> +filesystem to fulfill the run-time dependency: We have to force PTXdist to
>  install ``libm``. ``libm`` is part of the *glibc* package, but is not
>  installed by default (to keep the root filesystem small). So, it **does
>  not** help to select the ``GLIBC`` symbol, to get a ``libm`` at run-time.

ptxdist mailing list
To unsubscribe, send a mail with subject "unsubscribe" to

      parent reply	other threads:[~2021-06-16 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  6:50 [ptxdist] [PATCH 0/2] Fix typos Alexander Dahl
2021-06-08  6:50 ` [ptxdist] [PATCH 1/2] Fix typos in .in rules Alexander Dahl
2021-06-08 16:26   ` Roland Hieber
2021-06-16 10:35   ` [ptxdist] [APPLIED] " Michael Olbrich
2021-06-08  6:50 ` [ptxdist] [PATCH 2/2] doc: Fix a typo Alexander Dahl
2021-06-08 16:27   ` Roland Hieber
2021-06-08 16:45     ` Alexander Dahl
2021-06-11  9:26       ` Michael Olbrich
2021-06-16 10:35   ` Michael Olbrich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox