From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_compile/building/
Date: Sat, 8 Mar 2014 14:53:44 +0000 (UTC) [thread overview]
Message-ID: <1394221275.9a778ae5bf5369f04ab5493bfc1e6bc84b4e5b51.hwoarang@gentoo> (raw)
commit: 9a778ae5bf5369f04ab5493bfc1e6bc84b4e5b51
Author: Uwe L. Korn <uwelk <AT> xhochy <DOT> com>
AuthorDate: Fri Mar 7 19:41:15 2014 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Fri Mar 7 19:41:15 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=9a778ae5
Link to toolchain-funcs.eclass in src_compile/building
---
ebuild-writing/functions/src_compile/building/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ebuild-writing/functions/src_compile/building/text.xml b/ebuild-writing/functions/src_compile/building/text.xml
index 700f0f1..bed3dd7 100644
--- a/ebuild-writing/functions/src_compile/building/text.xml
+++ b/ebuild-writing/functions/src_compile/building/text.xml
@@ -34,7 +34,7 @@ some MIPS and SPARC systems.
<p>
Sometimes a package will try to use a bizarre compiler, or will need to be told
which compiler to use. In these situations, the <c>tc-getCC()</c> function from
-<c>toolchain-funcs.eclass</c> should be used. Other similar functions are available
+<uri link="::eclass-reference/toolchain-funcs.eclass/">toolchain-funcs.eclass</uri> should be used. Other similar functions are available
<d/> these are documented in <c>man toolchain-funcs.eclass</c>.
</p>
next reply other threads:[~2014-03-08 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 14:53 Markos Chandras [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-03 14:18 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_compile/building/ Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-06-15 8:20 Ulrich Müller
2021-06-15 8:25 Ulrich Müller
2021-08-01 2:30 Sam James
2021-08-14 1:43 Sam James
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1394221275.9a778ae5bf5369f04ab5493bfc1e6bc84b4e5b51.hwoarang@gentoo \
--to=hwoarang@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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