Re: supporting multiple versions of GCC with a single shared object release?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The only way I know of to do this reliably is to have a C interface.
The ABI breakages are definitely a bummer.  The other option is to
have a build for each used ABI.

On Tue, Apr 14, 2009 at 3:02 PM, mario guerra <emailformario@xxxxxxxxx> wrote:
> Hello all,
>
> I work for a chip company that produces a C++ simulator for one of our
> processor cores, which we deliver as a shared object file. We've used
> GCC version 3.3.3 to build it, since that is the standard version
> deployed within our company. However, some of our customers are
> attempting to incorporate our model into third party simulation
> environments which use different versions of GCC, and this sometimes
> causes segmentation faults at run time from calls into the stdc++
> library. We're trying to find a way to support customers who may be
> using different versions of GCC without having to create a custom
> simulator build for each customer.
>
> Surely this problem has come up for others before. I'm looking for any
> suggestions as to how this problem might be solved, any ideas would be
> much appreciated.
>
> Thanks,
> Mario
>

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux