Re: backward/forward compability

From: Thomas Maier-Komor (maierkom_at_lpr.e-technik.no-spam.tu-muenchen.de)
Date: 11/08/05 

Date: Tue, 08 Nov 2005 13:53:11 +0100

Scott Howard wrote:
> Thomas Maier-Komor <maierkom@lpr.e-technik.tu-muenchen.de> wrote:
>
>>What would possibly be the problem of installing the old libraries to an
>>alternate root (i.e. pkgadd -R /xyz) and letting the linker pick up this
>>directory first (with the -L flag)? I cannot imagine what the problem
>
>
> Only libraries? What about headers? And the linker itself? And probably
> the compiler too. And don't forget the patches to all of the above.
>

as mentioned by Marc the newer header files might refer to new symbols
which will be detected at link time. I am not sure about compile-time
constants - so you might still be right.

> Just install a copy of the old OS and use that instead. If you're short
> on hardware you can even just multi-boot on the same system - you could
> even share the source directories.
>

What if I use Sun Studio 10 which runs and is supported on Solaris 8 to
10? Its patches are installed into the product directory and it is
also supported to be installed on a directory that is shared via NFS
and used on another Solaris release. The only thing different during the
build process (when using Sun Stuido) is the step of linking. I don't
know if the linker itself changed in the way it creates the binaries on
a newer Solaris release... Is this the case?

Could one resolve potential problems by installing the older version
of appcert and run it on the newly created executable?

Tom

Relevant Pages

  • Re: Exportability of EDA industry from North America?
    ... > if a stock RedHat 9 system really does have so much trouble installing ... RedHat never uses /usr/local/lib for its libraries, ... > standard or similar to the upstream source packages. ... that you have created in your development of gEDA, ...
    (sci.electronics.cad)
  • Re: Exportability of EDA industry from North America?
    ... > if a stock RedHat 9 system really does have so much trouble installing ... RedHat never uses /usr/local/lib for its libraries, ... > standard or similar to the upstream source packages. ... that you have created in your development of gEDA, ...
    (sci.electronics.design)
  • KDE - icons and fonts not anti-aliased
    ... from ports and the icons and fonts look jagged ... without the Xft support, when I was installing ... XFree86-libraries-4.3.0_6 XFree86-4 libraries and headers ... docbook-1.2_1 Meta-port for the different versions of the DocBook DTD ...
    (freebsd-questions)
  • KDE - icons and fonts not anti-aliased
    ... from ports and the icons and fonts look jagged ... without the Xft support, when I was installing ... XFree86-libraries-4.3.0_6 XFree86-4 libraries and headers ... docbook-1.2_1 Meta-port for the different versions of the DocBook DTD ...
    (freebsd-questions)
  • Re: Linking errors after conversion from VS2003 to VS2005
    ... and then installing VS2003 before installing VS2005. ... You should always rebuild everything with the correct headers and libraries. ... to see where the reference comes from (and actually the linker should give ... _Container_base (surprise, surprise). ...
    (microsoft.public.dotnet.languages.vc)