public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jesper Skov <jskov@zoftcorp.dk>,  ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Lack of libsupc++.a on BSD
Date: Mon, 17 Nov 2008 14:17:00 -0000	[thread overview]
Message-ID: <492094D6.5040807@eCosCentric.com> (raw)
In-Reply-To: <20081116204627.GE472@lunn.ch>

Andrew Lunn wrote:
> On Sun, Nov 16, 2008 at 03:40:12PM +0100, Jesper Skov wrote:
>>I happened to find something here
>>(http://www.ecoscentric.com/ecospro/doc.cgi/html/ref/memalloc-standard-api.html)
>>that suggests
>>that using the option CYGFUN_MEMALLOC_MALLOC_CXX_OPERATORS should
>>allow me to work around this.
>>
>>But I cannot find that option anywhere. Is it in the ecospro repo only?
> 
> This is only in ecosCentric's closed source port :-( 

<ahem> That's not closed source. It's under the usual eCos licence, 
distributed as per 3(a) of the GPL.

> A shame really,
> libsupc++.a regularly causes problems for synth, so being able to get
> rid of this dependancy would be good.

Copy the relevant subset of source files from GCC's libsupc++ into the 
synth HAL (probably in a subdir), build it into its own library (compile 
-library=libsupc++-ecos.a .... ?) and use that instead of libsupc++ in the 
linker script. The synth HAL can use CDL requires on 
CYGBLD_HAL_LINKER_GROUPED_LIBS_DEFAULT to do this (a newly added option, 
part of a contribution by eCosCentric :-)).

It's probably safer in its own library due to its slightly different GPL 
exception wording at the top.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------      Opinions==mine

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-11-16 21:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 20:47 Jesper Skov
2008-11-17 12:18 ` Andrew Lunn
2008-11-17 14:17   ` Jonathan Larmour [this message]
2008-11-17 22:06     ` Jesper Skov
2008-11-17 22:18       ` [ECOS] init_priority attribute is not supported on this platform krj
2008-11-18  0:04         ` Andrew Lunn
2008-11-18  1:45           ` krj
2008-11-17 22:03   ` [ECOS] Lack of libsupc++.a on BSD Jesper Skov
2008-12-28 10:14     ` Jesper Skov

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=492094D6.5040807@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jskov@zoftcorp.dk \
    /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).