public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: <bryanhundven@gmail.com>
To: "'Douglas Coup'" <dcoup@obj-sys.com>,	<crossgcc@sourceware.org>
Subject: RE: secureplt support
Date: Fri, 23 Mar 2018 17:03:00 -0000	[thread overview]
Message-ID: <047f01d3c2c8$d3b441d0$7b1cc570$@gmail.com> (raw)
In-Reply-To: <8be64ccb-0ce3-da0b-da2f-3016ec8c601b@obj-sys.com>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

Douglas,

> -----Original Message-----
> From: crossgcc-owner@sourceware.org <crossgcc-owner@sourceware.org>
> On Behalf Of Douglas Coup
> Sent: Friday, March 23, 2018 9:01 AM
> To: crossgcc@sourceware.org
> Subject: secureplt support
> 
> Hi.
> 
> A potential customer has pointed out that the tool chain they use shows this
> when they enter "gcc -v":
> 
> Configured with:  ...--enable-secureplt...
> 
> In other words one of the items their tool chain is configured with is the --
> enable-secureplt setting.  Is it possible to enable this setting in a tool chain
> produced by Crosstool-NG?  I couldn't find an obvious configuration item for
> this in the menus shown by the "ct-ng menuconfig"
> command.  The tool chain needs to target 32-bit PowerPC.

Yes, actually you can add '--enable-secureplt...' to an option under: 'C compiler -> gcc extra config'.
In the .config file this option is: CT_CC_GCC_EXTRA_CONFIG_ARRAY

> Regards,
> 
> Douglas Coup

Cheers,

-Bryan

> --
> Objective Systems, Inc.
> REAL WORLD ASN.1 AND XML SOLUTIONS
> Tel: +1 (484) 875-9841
> Fax: +1 (484) 875-9830
> Toll-free: (877) 307-6855 (USA only)
> http://www.obj-sys.com

[-- Attachment #2: Type: application/pgp-signature, Size: 834 bytes --]

      reply	other threads:[~2018-03-23 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 16:01 Douglas Coup
2018-03-23 17:03 ` bryanhundven [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:
  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='047f01d3c2c8$d3b441d0$7b1cc570$@gmail.com' \
    --to=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=dcoup@obj-sys.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).