From: Tavis Ormandy <taviso@gentoo.org>
To: gentoo-core@gentoo.org
Cc: gentoo-alpha@gentoo.org, gentoo-dev@gentoo.org
Subject: [gentoo-dev] new eclass: ccc
Date: Mon, 26 May 2003 17:00:19 +0100 [thread overview]
Message-ID: <20030526160019.GA3717@sdf.lonestar.org> (raw)
Hey list, this probably isnt of much interest to non-alpha users, but i've
just committed a new eclass with functions to help make ccc compatability
easier, theres a synopsis below.
#
#### hide-restrict-arr ####
# Scan for and replace __restrict_arr with a ccc
# supported equivalent.
#
# you might see an error like this if you need this:
#
# cc: Error: regexec.c, line 209: In the definition of the function "regexec",
# the promoted type of pmatch is incompatible with the type of the corresponding
# parameter in a prior declaration. (promotmatch)
# regmatch_t pmatch[];
# ---------------^
#
#### replace-cc-hardcode ####
# Look for common cc hardcodes in Makefiles.
#
#### replace-cxx-hardcode ####
# Look for common cxx hardcodes in Makefiles.
#
#### is-ccc ####
# Returns success if dec compiler is being used.
#
# example:
#
# is-ccc && hide-restrict-arr
#
#### is-cxx ####
# Returns success if dec c++ compiler is being used.
#
#### replace-ccc-g ####
# Try to replace -g with -g3
#
#### ccc-elf-check </path/to/binary> ####
# Return success if binary was compiled with ccc
#
# example:
# if ! is-ccc; then
# ccc-elf-check /usr/lib/libglib.a && \
# append-ldflags -lots
# fi
#
# NOTE: i think the binary and shared library detection
# is pretty safe, but the archive detection may not
# be as reliable.
#### create-so </usr/lib/library.a> <library.so> ####
# Make the shared library (.so) specified from the archive (.a)
# specified. LDFLAGS will be honoured. if you need a different
# `soname` (DT_SONAME) from the shared lib filename, you will have
# to do it manually ;)
#
# example:
# is-ccc && \
# create-so /usr/lib/libcoolstuff.a libcoolstuff.so.${PV}
# dosym /usr/lib/libcoolstuff.so.${PV} /usr/lib/libcoolstuff.so
#
# NOTE: -lots will be used by default, this is ccc.eclass after all :)
# NOTE: .${PV} is optional, of course.
# NOTE: dolib.so will manage installation
#### append-ldflags <flag> ####
#### is-ldflag <flag> ####
#### filter-ldflags <flag> ####
# flag-o-matic doesnt provide LDFLAGS utilities.
# Some replacements for ccc porting. These functions
# mimic the flag-o-matic equivalents, look in there for
# documentation.
#
####
#
--
-------------------------------------
taviso@sdf.lonestar.org | finger me for my gpg key.
-------------------------------------------------------
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2003-05-26 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030526160019.GA3717@sdf.lonestar.org \
--to=taviso@gentoo.org \
--cc=gentoo-alpha@gentoo.org \
--cc=gentoo-core@gentoo.org \
--cc=gentoo-dev@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