My personal experience is, always create the distribution on old Linux
with older compiler to keep the maximal compatibility.
Since usually the GCC will pick libstdc++ from system, so if user runs the
distribution on even older Linux, 100% sure the error raises. On
CentOS/Redhat we do have the de
I've had to deal with this in the past.
For glibc, it's more tricky since when you compile on a newer
distribution, it will automatically use the newer version of some
symbols. Some functions have had breaking changes and to keep
compatibility, they kept all the different version in the binary
> On Jan 26, 2017, at 1:45 PM, Gonzalo Garramuño wrote:
>
>
>
> El 26/01/2017 a las 18:35, Michael Ellery escribió:
>> In what way is the stdlib incompatible? Does it have bugs, or is this more a
>> matter of cpp standard support?
> I should have been more clear. Sorry. The incompatabiliti
El 26/01/2017 a las 18:35, Michael Ellery escribió:
In what way is the stdlib incompatible? Does it have bugs, or is this more a
matter of cpp standard support?
I should have been more clear. Sorry. The incompatabilities happen at
linker time, with complaints such as:
exrstdattr: /lib64/
> On Jan 26, 2017, at 1:23 PM, Gonzalo Garramuño wrote:
>
> I currently own an Ubuntu Xenial 14.04.1 LTS box in which I do all my work.
> I distribute a binary image viewer. However, recently one of my users
> tried to run the viewer on a CentOS 7 distro and found out that that distro
>
I currently own an Ubuntu Xenial 14.04.1 LTS box in which I do all my
work.I distribute a binary image viewer. However, recently one of
my users tried to run the viewer on a CentOS 7 distro and found out that
that distro libc and libstdc++ are older and incompatible.
I would like to comp
> On Jan 26, 2017, at 1:23 AM, David Jobet wrote:
>
> Hello,
>
> suppose I want to use protobuf and integrate it in my project with
> externalproject_add. (actually, I just have precompiled binaries and libs +
> header files, I don't have the full sources)
> Once the project has been 'built'
You'll also want to build your own project with ExternalProject, and use
the DEPENDS option to control build order. This ensures that all
dependencies are fully installed before your own project is even
configured. The project with all the ExternalProject calls is typically
called a superbuild, and
I'll have a play with that later. Thanks again for all your help.
Doug.
On 25 January 2017 at 16:02, Michael Ellery wrote:
>
> > On Jan 24, 2017, at 11:22 PM, doug livesey wrote:
> >
> > Is there any way that I can make the files webpack compiles into
> dependencies for the Webpack task? So
Hello,
suppose I want to use protobuf and integrate it in my project with
externalproject_add. (actually, I just have precompiled binaries and libs +
header files, I don't have the full sources)
Once the project has been 'built' (actually, installed by a custom rpm-like
tool to a shared path),
Hello,
I actually gave it a try : it works fine so long versions are hardcoded
somewhere in the CMakeLists.txt and it make things really simpler.
But it does not work when version is extracted from git repository.
I came to realize I can extract this version number at build time (using
add_cust
11 matches
Mail list logo
