[systemd-devel] [PATCH] Fix systemd-stdio-bridge symlink

[Umut Tezduyar Lindskog]

On Wed, May 14, 2014 at 1:05 PM, Colin Guthrie <gmane at colin.guthr.ie> wrote:
> 'Twas brillig, and Umut Tezduyar Lindskog at 13/05/14 18:37 did gyre and
> gimble:
>>
>>
>> On Wednesday, May 7, 2014, Colin Guthrie <gmane at colin.guthr.ie
>> <mailto:gmane at colin.guthr.ie>> wrote:
>>
>>     'Twas brillig, and Umut Tezduyar Lindskog at 04/03/14 12:44 did gyre and
>>     gimble:
>>     >> Does that actually matter much? This ln usage is at build time,
>>     not install time,
>>     >> and those stable versions aren't going to upgrade to a current
>>     systemd,
>>     >> because avoiding non-minimal upgrades is the whole point of
>>     stable distro
>>     >> releases.
>>     >
>>     > As you have stated, it matters for build time and we have build
>>     machines not running the latest and greatest SW. I wouldn't be
>>     surprised if we are not alone.
>>
>>     Yeah, some of our build nodes are actually pretty old too, but that
>>     shouldn't matter really as the building happens inside a chroot with the
>>     latest packages, which includes latest ln.
>>
>>     Do you really build on an older node against older libs with older ln
>>     etc? I would have thought you'd also have some kind of chroot on these
>>     nodes when building too no?
>>
>>
>> No. We just have virtual machines with Debian Wheezy to do the build.
>
>
> Forgive my ignorance, but I'm curious as to how that works now :)

No worries.

>
> So the build runs on an older distro, but it's built *for* newer
> versions of the distro (I don't recall all the Debian names, so I'd have
> to look up exactly how old Wheezy is...) - is that correct?

We are cross compiling for our own distro. Our build machines which
execute the programs to do the build are Debian stable.

Umut

>
> Assuming that's right, how do you deal with linking against older system
> libraries etc when building the package? If you do not install all the
> new deps (and buildchain) in a chroot, how are they installed and made
> available to the compiler? Are they just installed somehow relocated and
> passed in as compile time options (i.e. overriding the pkgconfig path etc.)
>
> Thanks!
>
> Col
>
>
> --
>
> Colin Guthrie
> gmane(at)colin.guthr.ie
> http://colin.guthr.ie/
>
> Day Job:
>   Tribalogic Limited http://www.tribalogic.net/
> Open Source:
>   Mageia Contributor http://www.mageia.org/
>   PulseAudio Hacker http://www.pulseaudio.org/
>   Trac Hacker http://trac.edgewall.org/