I think Jim is referring to the gstreamer situation, where we decided
that we skip CentOS6 more or less for 4.2.0.And one argument was, if
they want something they should support us. This is not showing sympathy
for a small user group that uses very old software for 2 more years
until they have
What impact has Ant 1.10.x exactly on older machines?
It is no problem for me to build the Windows version with Ant 1.9.12. As
long as we use Java 8.
But again, I just did a personal build to test AOO 4.1.x with Java 8.
Nothing else.
To be more precise: I was the only one who cared. No response fr
The above made it appear that Ant 1.9.x was no longer supported plus had some
sort of security related issue making it unsuited for AOO... ie, we *needed* to
use Ant 1.10 not just that we now *can* use it.
How about showing some sympathy and understanding for those who may be stuck w/
older mac
I think this may have to do w/ the 'Implement the ability to build "UDK
versioned" libraries in gbuild'
stuff from
http://svn.apache.org/viewvc?view=revision&revision=1827456
This is breaking macOS horribly!
> On Jul 3, 2018, at 8:28 AM, Matthias Seidel
> wrote:
>
> Am 03.07.2018 um 13:
Looking over it again, it looks like the build is trying to do something wonky
with the store.map file...
> On Jul 3, 2018, at 8:28 AM, Matthias Seidel
> wrote:
>
> Am 03.07.2018 um 13:59 schrieb Jim Jagielski:
>>
>>> On Jul 3, 2018, at 7:47 AM, Matthias Seidel
>>> wrote:
>>>
>>> Hi Jim,
>>
Am 03.07.2018 um 21:45 schrieb Jim Jagielski:
>
>> On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote:
>>
>> Hi everbody.
>>
>>
>> I would like to bring a 4.1.6 Release on the way in July. Even if we manage
>> to get 4.2.0 ready it will only be a beta. And we have some stuff to get out
>> to the pe
> On Jul 1, 2018, at 11:27 AM, Peter Kovacs wrote:
>
> Hi everbody.
>
>
> I would like to bring a 4.1.6 Release on the way in July. Even if we manage
> to get 4.2.0 ready it will only be a beta. And we have some stuff to get out
> to the people.
>
> Matthias has created a suggestion for a
Hi Kay,
Am 01.07.2018 um 23:51 schrieb Kay Schenk:
> Hi *,
>
> If 4.1.6 would contain some needed security fixes, by all means, it
> needs to be released as soon as possible.
>
> Some questions --
>
> Will Java 8 then be the minimum version to use 4.1.6?
> Because Ant is only used for building, t
Am 03.07.2018 um 19:47 schrieb Jim Jagielski:
> As soon as we have a repo branch setup, I'll kick off Linux and macOS builds.
I'll do the Windows builds... ;-)
>
>> On Jul 3, 2018, at 1:11 PM, Marcus wrote:
>>
>> Am 01.07.2018 um 17:27 schrieb Peter Kovacs:
>>> I would like to bring a 4.1.6 Rele
As soon as we have a repo branch setup, I'll kick off Linux and macOS builds.
> On Jul 3, 2018, at 1:11 PM, Marcus wrote:
>
> Am 01.07.2018 um 17:27 schrieb Peter Kovacs:
>> I would like to bring a 4.1.6 Release on the way in July. Even if we manage
>> to get 4.2.0 ready it will only be a beta.
Am 01.07.2018 um 17:27 schrieb Peter Kovacs:
I would like to bring a 4.1.6 Release on the way in July. Even if we
manage to get 4.2.0 ready it will only be a beta. And we have some stuff
to get out to the people.
Matthias has created a suggestion for a 4.1.6 release on security.
Containing so
Hi Peter,
Am 01.07.2018 um 17:27 schrieb Peter Kovacs:
> Hi everbody.
>
>
> I would like to bring a 4.1.6 Release on the way in July. Even if we
> manage to get 4.2.0 ready it will only be a beta. And we have some
> stuff to get out to the people.
>
> Matthias has created a suggestion for a 4.1.6
+1. I'll start on a CentOS7 VM.
BTW, up to now I've been using VMware Fusion, but will likely start using Vbox
instead... I'm assuming most people are using that anyway and it would be nice
to be able to share the VMs with others.
> On Jul 3, 2018, at 8:30 AM, Peter Kovacs wrote:
>
> I think
I think there was no big support for supporting gstreamer 0.1.0 on 4.2.
branch. If those who need it , they should help.
Also I think it makes more sense in such a case to keep maintenance for
4.1.x branch.
That means we will have to move to centOS7 for building.
On 03.07.2018 14:00, Jim Jag
Am 03.07.2018 um 13:59 schrieb Jim Jagielski:
>
>> On Jul 3, 2018, at 7:47 AM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> "Undefined symbols for architecture x86_64:"
>>
>> This might have something to do with Damjans changes for a Windows 64-bit
>> build.
>>
>> The buildbots for Windows and
Oops. Forget that. Even CentOS6 doesn't support gstreamer-1.0.
> On Jul 3, 2018, at 6:47 AM, Jim Jagielski wrote:
>
> So have we come up w/ an agreed upon decision? Are we baselining
> gstreamer-1.0, and our community/build-systems will be based on
> CentOS6 (ie: dropping "official" support for
> On Jul 3, 2018, at 7:47 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> "Undefined symbols for architecture x86_64:"
>
> This might have something to do with Damjans changes for a Windows 64-bit
> build.
>
> The buildbots for Windows and Linux are doing fine, so it seems to be macOS
> only
Hi Jim,
"Undefined symbols for architecture x86_64:"
This might have something to do with Damjans changes for a Windows
64-bit build.
The buildbots for Windows and Linux are doing fine, so it seems to be
macOS only.
Regards,
Matthias
Am 03.07.2018 um 13:26 schrieb Jim Jagielski:
> It look
It looks like I'm having some weird build issues with
this module due to exported symbols not working out
(on macOS... haven't tried Linux yet). Any ideas??
The error is:
[ build CHK ] loaded modules: store
[ build PKG ] store_xml
mkdir -p
/Users/jim/src/asf/AOO420/main/solver/420/unxmaccx.pro/w
So have we come up w/ an agreed upon decision? Are we baselining
gstreamer-1.0, and our community/build-systems will be based on
CentOS6 (ie: dropping "official" support for CentOS5)?
If so, I can start on some 4.2.0-dev r1834788 Linux builds...
(I'm already trying macOS builds but having some we
20 matches
Mail list logo
