Re: Issue for 4.1.4 and MacOS

I got the same result as Dave. Larry On 2017-11-06, 4:12 PM Dave Fisher wrote: Good news is that the Base issue is fixed. Bad news is that the Charts saving issue has returned. Sorry. Regards, Dave On Nov 6, 2017, at 12:27 PM, Jim Jagielski wrote: Okey dokey... I *think* that having xml2

Re: Issue for 4.1.4 and MacOS

Hi Jim, I’m not seeing an improvement in the latest build you are now pushing to dist. Base works. I still get the two system.log messages. Charts are not saved even if I just do a save as. I wonder if we also need the redland/raptor update that is in trunk. I can spare a few hours tomorrow to

Re: Issue for 4.1.4 and MacOS

There is something I've seen in the OpenOffice code that may be involved in the silent failures to do something. For example, main\xmloff\source\core\xmlexp.cxx, line 759: catch( com::sun::star::uno::Exception& ) { } This will hide any and all UN

Re: Issue for 4.1.4 and MacOS

Good news is that the Base issue is fixed. Bad news is that the Charts saving issue has returned. Sorry. Regards, Dave > On Nov 6, 2017, at 12:27 PM, Jim Jagielski wrote: > > Okey dokey... I *think* that having xml2 built w/ iconv was, > in fact, the issue. Double checking as we speak. > > -

Re: Issue for 4.1.4 and MacOS

Okey dokey... I *think* that having xml2 built w/ iconv was, in fact, the issue. Double checking as we speak. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apa

Re: Issue for 4.1.4 and MacOS

A reminder of what I'm talking about: < LIBXML_CFLAGS='-I/usr/local/include/libxml2' --- > LIBXML_CFLAGS='-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/libxml2' 1289,1291c1326,1328 < LIBXML_LIBS='-L/usr/local/

Re: Issue for 4.1.4 and MacOS

Considering that it was the xml2/xslt libs that changed between the version, I am focusing my attention on that. The pervious version, that broke embedded charts but worked with the table used/linked macOS's libs. This latest version uses local libs; which looks to have fixed the embedded chart but

Re: Issue for 4.1.4 and MacOS

yep > On Nov 5, 2017, at 5:49 PM, Andrea Pescetti wrote: > > Jim Jagielski wrote: >> I am wondering if this means/requires that the build machine >> MUST be running 10.12 (Sierra). > > The original report https://bz.apache.org/ooo/show_bug.cgi?id=127580 says > that the Base bug happens with the

Re: Issue for 4.1.4 and MacOS

Jim Jagielski wrote: I am wondering if this means/requires that the build machine MUST be running 10.12 (Sierra). The original report https://bz.apache.org/ooo/show_bug.cgi?id=127580 says that the Base bug happens with the new (20171101) builds but not with the 4.1.4 builds released in Octobe

Re: Issue for 4.1.4 and MacOS

Another possible useful link: o http://support.cocoatech.com/discussions/problems/43623-crashes-under-the-new-sierra-10122-update/page/3 I am wondering if this means/requires that the b

Re: Issue for 4.1.4 and MacOS

Hi Jim, I did some googling of the error message. On this page may be a clue: https://discussions.apple.com/thread/7677685 I wonder if there is something with the internal SQL setup. I know we have developers who are working on variations and Base can handle alternatives. I am going to try a f

Re: Issue for 4.1.4 and MacOS

I can't even imagine what in the build system would cause this situation or how changes in the build system would do this. Does someone know, off the top of their head, the process/code flow which is being performed? I guess I could try to attach to the soffice process and step through, but it wou

Re: Issue for 4.1.4 and MacOS

Copying here: This is interesting... When opening the Base file I get the following in /var/log/system.log: 596:Nov 3 10:29:19 Daves-MacBook-Pro soffice[70777]: assertion failed: 16G29: libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89 597:Nov 3 10:29:22 Daves-MacBook-Pro soff

Re: Issue for 4.1.4 and MacOS

I confirmed that I have Larry’s bug. I commented in BZ. I noticed an error in /var/log/system.log > On Nov 3, 2017, at 5:48 AM, Larry Gusaas wrote: > > commented in Bugzilla > > On 2017-11-03, 6:03 AM Jim Jagielski wrote concerning "Re: Issue for 4.1.4 > and MacOS&qu

Re: Issue for 4.1.4 and MacOS

commented in Bugzilla On 2017-11-03, 6:03 AM Jim Jagielski wrote concerning "Re: Issue for 4.1.4 and MacOS": Following up in Bugz... cannot recreate. On Nov 3, 2017, at 7:45 AM, Larry Gusaas wrote: Created an issue in Bugzillahttps://bz.apache.org/ooo/show_bug.cgi?id=127580 *Is

Re: Issue for 4.1.4 and MacOS

Following up in Bugz... cannot recreate. > On Nov 3, 2017, at 7:45 AM, Larry Gusaas wrote: > > Created an issue in Bugzilla https://bz.apache.org/ooo/show_bug.cgi?id=127580 > *Issue 127580* -Fix > forIssue 127568

Re: Issue for 4.1.4 and MacOS

Created an issue in Bugzilla https://bz.apache.org/ooo/show_bug.cgi?id=127580 *Issue 127580* -Fix forIssue 127568 created a new bug in Base On 2017-11-02, 5:32 PM Larry Gusaas wrote: On 2017-11-

Re: Issue for 4.1.4 and MacOS

On 2017-11-02, 4:21 PM Dave Fisher wrote: Hi Larry, Thanks. Are you able to share the Base document and steps to reproduce? I will have to make a new document. The one I have is a community list with names, addresses, phone numbers, etc. I'll make a copy and xxx out the personal information.

Re: Issue for 4.1.4 and MacOS

Hi Larry, Thanks. Are you able to share the Base document and steps to reproduce? Are you pulling from your local address book? What version of Mac OS are you on? Would you put this information into BZ? Regards, Dave Sent from my iPhone > On Nov 2, 2017, at 1:17 PM, Larry Gusaas wrote: > >

Re: Issue for 4.1.4 and MacOS

Am 02.11.2017 um 22:48 schrieb Marcus: > Am 01.11.2017 um 22:41 schrieb Marcus: >> Am 01.11.2017 um 00:29 schrieb Matthias Seidel: >>> >>> Yes, Marcus knows best. But I think this would be the best way to >>> implement it. >> >> fix is ready and working locally. >> >> Text in the red error box: >>

Re: Issue for 4.1.4 and MacOS

Am 01.11.2017 um 22:41 schrieb Marcus: Am 01.11.2017 um 00:29 schrieb Matthias Seidel: Am 01.11.2017 um 00:22 schrieb Andrea Pescetti: Matthias Seidel wrote: Am 31.10.2017 um 23:39 schrieb Andrea Pescetti: Andrea Pescetti wrote: In terms of the update feed, we can keep on hold the update fee

Re: Issue for 4.1.4 and MacOS

Found problem in Base. I only have one Base document. When I select Tables under Database and then Addresses under Tables it does not open. Forms/Query Addresses opens. Works properly in 4.1.3 and in the released version of 4.1.4. On 2017-11-02, 12:56 PM Dave Fisher wrote: Larry can you check

Re: Issue for 4.1.4 and MacOS

On Thu, 2 Nov 2017 11:56:39 -0700 Dave Fisher wrote: > I confirmed the same yesterday. Remember The Hunting of the Snark "What I tell you three times is true"! Rory > > Larry can you check for any regressions? > > Regards, > Dave > > Sent from my iPhone > > > On Nov 2, 2017, at 11:40 AM,

Re: Issue for 4.1.4 and MacOS

I confirmed the same yesterday. Larry can you check for any regressions? Regards, Dave Sent from my iPhone > On Nov 2, 2017, at 11:40 AM, Marcus wrote: > >> Am 02.11.2017 um 19:36 schrieb Larry Gusaas: >> Tested calc in the repaired version. Charts are saving properly. > > and the 2nd confir

Re: Issue for 4.1.4 and MacOS

Am 02.11.2017 um 19:36 schrieb Larry Gusaas: Tested calc in the repaired version. Charts are saving properly. and the 2nd confirmation. That's great. :-) Marcus On 2017-11-02, 4:48 AM Jim Jagielski wrote: https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/

Re: Issue for 4.1.4 and MacOS

Tested calc in the repaired version. Charts are saving properly. On 2017-11-02, 4:48 AM Jim Jagielski wrote: https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ On Nov 1, 2017, at 6:15 PM, Rory O'Far

Re: Issue for 4.1.4 and MacOS

On 11/02/2017 08:20 AM, Rory O'Farrell wrote: Reports from the affected user are that old files (pre 4.1.4) with charts are opening correctly. Files made and/or saved with the faulty 4.1.4 release are not showing charts, as we would expect, as the charts were not stored in the files. When t

Re: Issue for 4.1.4 and MacOS

Reports from the affected user are that old files (pre 4.1.4) with charts are opening correctly. Files made and/or saved with the faulty 4.1.4 release are not showing charts, as we would expect, as the charts were not stored in the files. When these files are remade with the new version and th

Re: Issue for 4.1.4 and MacOS

On Thu, 2 Nov 2017 06:48:03 -0400 Jim Jagielski wrote: > https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ > > > > On Nov 1, 2017, at 6:15 PM, Rory O'Farrell wrote: > > > > May I have a URL for the

Re: Issue for 4.1.4 and MacOS

https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101/ > On Nov 1, 2017, at 6:15 PM, Rory O'Farrell wrote: > > May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the > repaired Mac file

Re: Issue for 4.1.4 and MacOS

Am 01.11.2017 um 23:09 schrieb Rory O'Farrell: On Wed, 1 Nov 2017 22:41:38 +0100 Marcus wrote: Am 01.11.2017 um 00:29 schrieb Matthias Seidel: Am 01.11.2017 um 00:22 schrieb Andrea Pescetti: Matthias Seidel wrote: Am 31.10.2017 um 23:39 schrieb Andrea Pescetti: Andrea Pescetti wrote: In t

Re: Issue for 4.1.4 and MacOS

May I have a URL for the repaired Mac version of 4.1.4 (or a copy of the repaired Mac file) which I can pass to the Forum user who has posted on this problem; he uses charts daily and can be relied upon to report any other problems. Rory -- Rory O'Farrell ---

Re: Issue for 4.1.4 and MacOS

On Wed, 1 Nov 2017 22:41:38 +0100 Marcus wrote: > Am 01.11.2017 um 00:29 schrieb Matthias Seidel: > > Am 01.11.2017 um 00:22 schrieb Andrea Pescetti: > >> Matthias Seidel wrote: > >>> Am 31.10.2017 um 23:39 schrieb Andrea Pescetti: > Andrea Pescetti wrote: > > In terms of the update feed

Re: Issue for 4.1.4 and MacOS

Am 01.11.2017 um 00:29 schrieb Matthias Seidel: Am 01.11.2017 um 00:22 schrieb Andrea Pescetti: Matthias Seidel wrote: Am 31.10.2017 um 23:39 schrieb Andrea Pescetti: Andrea Pescetti wrote: In terms of the update feed, we can keep on hold the update feeds for the 4.1.3 (and earlier) to 4.1.4

Re: Issue for 4.1.4 and MacOS

On 10/31/2017 11:03 AM, Jim Jagielski wrote: It would be easy to bump the build number 414m6 just for macOS. Of course, the date is also changed, even if we keep the same build number. This makes more sense to me than a complete 4.1.5 (for all?) when this build issue just applies to MacOS.  Bu

Re: Issue for 4.1.4 and MacOS

> On Nov 1, 2017, at 8:04 AM, Jim Jagielski wrote: > > I have replacement macOS builds available which solve this problem. > > There were no source code changes required: it was simply an issue > with the build environment itself. As such, these new builds have > the same version numbers, just

Re: Issue for 4.1.4 and MacOS

I have replacement macOS builds available which solve this problem. There were no source code changes required: it was simply an issue with the build environment itself. As such, these new builds have the same version numbers, just different build dates. I'd like to propose that we open up these

Re: Issue for 4.1.4 and MacOS

Am 01.11.2017 um 00:22 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Am 31.10.2017 um 23:39 schrieb Andrea Pescetti: >>> Andrea Pescetti wrote: In terms of the update feed, we can keep on hold the update feeds for the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1

Re: Issue for 4.1.4 and MacOS

Matthias Seidel wrote: Am 31.10.2017 um 23:39 schrieb Andrea Pescetti: Andrea Pescetti wrote: In terms of the update feed, we can keep on hold the update feeds for the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5 is out, we will push the update as usual. I could temporari

Re: Issue for 4.1.4 and MacOS

Am 31.10.2017 um 23:39 schrieb Andrea Pescetti: > Andrea Pescetti wrote: >> In terms of the update feed, we can keep on hold the update feeds for >> the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5 >> is out, we will push the update as usual. I could temporarily exchange all

Re: Issue for 4.1.4 and MacOS

Andrea Pescetti wrote: In terms of the update feed, we can keep on hold the update feeds for the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5 is out, we will push the update as usual. Another obvious thing we can do (if we are really sure that 4.1.4 for Mac contains a dat

Re: Issue for 4.1.4 and MacOS

Dave Fisher wrote: I would like to know what Andrea and Matthias think since they have been working with the upgrade system. This is just a bug. A bad bug, that teaches us that (let alone the source code) we should document not only the configure switches but also key details of the environm

Re: Issue for 4.1.4 and MacOS

Am 31.10.2017 um 19:46 schrieb Dave Fisher: The implication is that build id, milestone, binaries and svn version must be in sync across all of OpenOffice. which is the case already. ;-) Jim should leave the values the same as the prior release. So 75,000 plus users of Mac may be in limbo n

Re: Issue for 4.1.4 and MacOS

Hi Marcus, The implication is that build id, milestone, binaries and svn version must be in sync across all of OpenOffice. Jim should leave the values the same as the prior release. So 75,000 plus users of Mac may be in limbo not knowing about the update until 4.2 comes out. We will need to an

Re: Issue for 4.1.4 and MacOS

Am 31.10.2017 um 19:09 schrieb Jim Jagielski: Actually, it looks like buildid (9788) is likely should also be bumped, looking at the way downloads are done... Do linux and Windows would be m5(9788) and mac would be m5(9789) or m6(9789) I am *guessing* that the m# is SVN related and the buildid n

Re: Issue for 4.1.4 and MacOS

Hi Jim, Have a look at http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/generate-update-feed.sh?view=markup 80 elif [ $idx -eq 2 ]; then 81

Re: Issue for 4.1.4 and MacOS

So the only thing that will indicate the new version will be an updated date in the About page? > On Oct 31, 2017, at 2:19 PM, Rory O'Farrell wrote: > > On Tue, 31 Oct 2017 14:09:46 -0400 > Jim Jagielski mailto:j...@jagunet.com>> wrote: > >> Actually, it looks like buildid (9788) is likely >> s

Re: Issue for 4.1.4 and MacOS

On Tue, 31 Oct 2017 14:09:46 -0400 Jim Jagielski wrote: > Actually, it looks like buildid (9788) is likely > should also be bumped, looking at the way downloads > are done... Do linux and Windows would be m5(9788) > and mac would be m5(9789) or m6(9789) When a decision is reached and the new Mac

Re: Issue for 4.1.4 and MacOS

Sorry hit the command key and track pad at the same time and sent before done. > On Oct 31, 2017, at 11:10 AM, Dave Fisher wrote: > > >> On Oct 31, 2017, at 11:05 AM, Matthias Seidel > > wrote: >> >> Am 31.10.2017 um 18:52 schrieb Dave Fisher: On Oct 31,

Re: Issue for 4.1.4 and MacOS

> On Oct 31, 2017, at 11:05 AM, Matthias Seidel > wrote: > > Am 31.10.2017 um 18:52 schrieb Dave Fisher: >>> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan wrote: >>> >>> I do not know if this is the right choice, but we should include doing both >>> in our thinking. Rebuild 4.1.4 for Mac on

Re: Issue for 4.1.4 and MacOS

Actually, it looks like buildid (9788) is likely should also be bumped, looking at the way downloads are done... Do linux and Windows would be m5(9788) and mac would be m5(9789) or m6(9789) I am *guessing* that the m# is SVN related and the buildid number is courtesy build # related?? > On Oct 31,

Re: Issue for 4.1.4 and MacOS

Am 31.10.2017 um 18:52 schrieb Dave Fisher: >> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan wrote: >> >> I do not know if this is the right choice, but we should include doing both >> in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as >> possible. Meanwhile, create, test,

Re: Issue for 4.1.4 and MacOS

It would be easy to bump the build number 414m6 just for macOS. Of course, the date is also changed, even if we keep the same build number. I am up for whatever makes sense. The issue is that it's not a code "problem" at all. > On Oct 31, 2017, at 1:52 PM, Dave Fisher wrote: > > >> On Oct 31,

Re: Issue for 4.1.4 and MacOS

> On Oct 31, 2017, at 9:51 AM, Patricia Shanahan wrote: > > I do not know if this is the right choice, but we should include doing both > in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as > possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade > s

Re: Issue for 4.1.4 and MacOS

Am 31.10.2017 um 17:30 schrieb Dave Fisher: > There have been over 1,000,000 downloads of 4.1.4. How many were of the bad > Mac version? About 75,000: https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.4/binaries/stats/os?dates=2017-10-19%20to%202017-10-31 Regards, Matthias > > If

Re: Issue for 4.1.4 and MacOS

I do not know if this is the right choice, but we should include doing both in our thinking. Rebuild 4.1.4 for Mac only, test, and upload as soon as possible. Meanwhile, create, test, and vote on 4.1.5, to pick up the upgrade service. On 10/31/2017 9:30 AM, Dave Fisher wrote: There have been

Re: Issue for 4.1.4 and MacOS

There have been over 1,000,000 downloads of 4.1.4. How many were of the bad Mac version? If we replace then how would those people know to upgrade? This issue makes me think we need to have this be a new version so that we can setup the upgrade service correctly. Regards, Dave > On Oct 31, 2

Re: Issue for 4.1.4 and MacOS

Question: Assuming we have "correction" builds available, what do we do? Simply replace the online version with these? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@open

Re: Issue for 4.1.4 and MacOS

Nope. This is virgin Xcode7 $ sudo xcode-select -s /Applications/Xcode7.app > On Oct 31, 2017, at 12:02 PM, Dave Fisher wrote: > > Hi Jim, > > Any use of XcodeLegacy in your Xcode7 setup? > > Regards, > Dave > >> On Oct 31, 2017, at 8:53 AM, Jim Jagielski wrote: >> >> OK, I *think*

Re: Issue for 4.1.4 and MacOS

This is what I'm thinking... by using the system xml/xslt, instead of bundling it, we are getting some weird interactions. < LIBXML_CFLAGS='-I/usr/local/include/libxml2' --- > LIBXML_CFLAGS='-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/i

Re: Issue for 4.1.4 and MacOS

Hi Jim, Any use of XcodeLegacy in your Xcode7 setup? Regards, Dave > On Oct 31, 2017, at 8:53 AM, Jim Jagielski wrote: > > OK, I *think* I found it... it looks like it is a XML/xslt issue > where the 10.12 SDK, even though it is not used, the > XML libs from it are. > > Downgrading from Xcode

Re: Issue for 4.1.4 and MacOS

I bow to empirical facts, but I am still confused. There are several xml files in the .ods, most of which are written correctly. Why just the ones under 'Object 1'? On 10/31/2017 8:53 AM, Jim Jagielski wrote: OK, I *think* I found it... it looks like it is a XML/xslt issue where the 10.12 SDK,

Re: Issue for 4.1.4 and MacOS

OK, I *think* I found it... it looks like it is a XML/xslt issue where the 10.12 SDK, even though it is not used, the XML libs from it are. Downgrading from Xcode8 to Xcode7 looks to resolve that. Build 4.1.3 using Xcode7 worked (no corrupt). --

Re: Issue for 4.1.4 and MacOS

Looking over how 4.1.2 was built I will admit that I am totally confused. According to the config.out file it was built on an 8-core MacBook, running Mavericks (10.9) but with an Xcode that supported the 10.10 SDK... which is basically impossible. Xcode6, which is the 1st one to support the 10.10 S

Re: Issue for 4.1.4 and MacOS

Hmmm... the default memory allocator seems to have changed between 4.1.2 and 4.1.4 from internal to system. Checking... > On Oct 30, 2017, at 9:51 PM, Jim Jagielski wrote: > > That is what I am thinking... looking at the config.out > diff between 4.1.2 and 4.1.4... > >> On Oct 30, 2017, at 8:43

Re: Issue for 4.1.4 and MacOS

That is what I am thinking... looking at the config.out diff between 4.1.2 and 4.1.4... > On Oct 30, 2017, at 8:43 PM, Don Lewis wrote: > > On 30 Oct, Jim Jagielski wrote: >> So building 4.1.3 also results in the same behavior >> as 4.1.4... so it is almost assuredly a build issue. >> Assuming i

Re: Issue for 4.1.4 and MacOS

On 30 Oct, Jim Jagielski wrote: > So building 4.1.3 also results in the same behavior > as 4.1.4... so it is almost assuredly a build issue. > Assuming it is an SDK issue, I am trying to build > w/ Xcode5... Will keep everyone posted. It could also be different configuration settings for bundled v

Re: Issue for 4.1.4 and MacOS

So building 4.1.3 also results in the same behavior as 4.1.4... so it is almost assuredly a build issue. Assuming it is an SDK issue, I am trying to build w/ Xcode5... Will keep everyone posted. > On Oct 30, 2017, at 4:29 PM, Jim Jagielski wrote: > > Building from AOO413 (tag) as we speak... >

Re: Issue for 4.1.4 and MacOS

Building from AOO413 (tag) as we speak... - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Issue for 4.1.4 and MacOS

Thx! > On Oct 29, 2017, at 2:07 PM, Larry Gusaas wrote: > > On 2017-10-29, 8:05 AM Jim Jagielski wrote: >>> On Oct 28, 2017, at 1:30 PM, Patricia Shanahan wrote: >>> >>> The original bug report said "This wasn't an issue of AOO 4.1.3, but is an >>> issue of AOO 4.1.4" so we are looking for so

Re: Issue for 4.1.4 and MacOS

On 2017-10-29, 8:05 AM Jim Jagielski wrote: On Oct 28, 2017, at 1:30 PM, Patricia Shanahan wrote: The original bug report said "This wasn't an issue of AOO 4.1.3, but is an issue of AOO 4.1.4" so we are looking for something that changed. Can someone download 4.1.3 for macOS and confirm that?

Re: Issue for 4.1.4 and MacOS

> On Oct 28, 2017, at 1:30 PM, Patricia Shanahan wrote: > > The original bug report said "This wasn't an issue of AOO 4.1.3, but is an > issue of AOO 4.1.4" so we are looking for something that changed. > Can someone download 4.1.3 for macOS and confirm that? I'm out-of-pocket for a coupla da

Re: Issue for 4.1.4 and MacOS

That is a good idea... Also, IIRC, we don't have any real record of the build params used for 4.1.3 macOS. What's in there is what I uploaded, but, as mentioned, I didn't build the 4.1.3 macOS release. > On Oct 28, 2017, at 3:11 PM, Andrea Pescetti wrote: > > Dave Fisher wrote: >> We ought to fa

Re: Issue for 4.1.4 and MacOS

On 10/28/2017 12:11 PM, Andrea Pescetti wrote: Dave Fisher wrote: We ought to factor out the build tooling by comparing a build based on 4.1.3 with the bug to rule out a tooling regression. Very good suggestion. Building 4.1.3 on exactly the same system and with exactly the same config used f

Re: Issue for 4.1.4 and MacOS

> On Oct 28, 2017, at 12:11 PM, Andrea Pescetti wrote: > > Dave Fisher wrote: >> We ought to factor out the build tooling by comparing a build based on 4.1.3 >> with the bug to rule out a tooling regression. > > Very good suggestion. Building 4.1.3 on exactly the same system and with > exactl

Re: Issue for 4.1.4 and MacOS

Dave Fisher wrote: We ought to factor out the build tooling by comparing a build based on 4.1.3 with the bug to rule out a tooling regression. Very good suggestion. Building 4.1.3 on exactly the same system and with exactly the same config used for 4.1.4 will tell us whether this is related

Re: Issue for 4.1.4 and MacOS

Hi - > On Oct 28, 2017, at 10:30 AM, Patricia Shanahan wrote: > > The original bug report said "This wasn't an issue of AOO 4.1.3, but is an > issue of AOO 4.1.4" so we are looking for something that changed. > > I would have assumed that the same libraries would be used in writing the > main

Re: Issue for 4.1.4 and MacOS

The original bug report said "This wasn't an issue of AOO 4.1.3, but is an issue of AOO 4.1.4" so we are looking for something that changed. I would have assumed that the same libraries would be used in writing the main content.xml and the one in the 'Object 1' subdirectory. The main content.x

Re: Issue for 4.1.4 and MacOS

Hi - I’ve attached a diff of the differences between 4.1.3 and 4.1.4. I hope that this helps. If I had a working build I would be looking into undoing a change at a time to see which had the impact on the save of links on Mac. I am also suspicious of tooling and what caused the link xml to be c

Re: Issue for 4.1.4 and MacOS

I at first thought this might be a load problem. It is now clear it is a case of file corruption on save, only on Mac. Unfortunately, that means I am out of ideas, other than checking that your original test has been done on the file save. The fixes I know about are intended to affect file loa

Re: Issue for 4.1.4 and MacOS

Yeah, I kinda figured out what your hypothesis was... I'll need to think about this some more. > On Oct 26, 2017, at 8:34 AM, Patricia Shanahan wrote: > > OK, forget that hypothesis. You have even done the next test I would have > asked for if the line 288 breakpoint was not reached. > > I'll n

Re: Issue for 4.1.4 and MacOS

OK, forget that hypothesis. You have even done the next test I would have asked for if the line 288 breakpoint was not reached. I'll need to think up a new hypothesis. I'm planning to go groom a couple of horses this morning, but I'll work on this in the afternoon. On 10/26/2017 5:01 AM, Jim

Re: Issue for 4.1.4 and MacOS

I set breakpoints on both: (lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288 (lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate Breakpoint 4: where = libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 0x00010070a260 and when

Re: Issue for 4.1.4 and MacOS

I did a quick rebuild but with the '--with-alloc=system' line removed. No change in behavior. Will try to track down the question Patricia raised in the Bugz report. > On Oct 24, 2017, at 11:36 AM, Jim Jagielski wrote: > > Will also follow up on the Bugz report, but one change between 4.1.3 > a

Re: Issue for 4.1.4 and MacOS

Hi - I’ve been trying to get Mac builds going today. I am trying right now with trunk. I’m still stuck on configure and have an XCodeLegacy question out to Jim on another thread. checking which jpeg to use... internal checking which expat to use... internal checking which libxslt to use... exte

Re: Issue for 4.1.4 and MacOS

Even if you can't get a Mac build going in time to help with this bug, we obviously need more people building and testing on Mac. On 10/24/2017 4:01 PM, Peter kovacs wrote: I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can build. So far I failed to install the old co

Re: Issue for 4.1.4 and MacOS

I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can build. So far I failed to install the old code on it. If I can manage to build, I could dig into the problem. I have a long weekend upcoming. Hope I can allocate time. Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagi

Re: Issue for 4.1.4 and MacOS

Will also follow up on the Bugz report, but one change between 4.1.3 and 4.1.4 regarding macOS *builds* is that 4.1.4 uses '--with-alloc=system' but the 4.1.3 build does not. I will create a macOS build of AOO414 but adjust the configure script to not include that and see what effect that may have

Re: Issue for 4.1.4 and MacOS

On 10/24/2017 5:49 AM, Rory O'Farrell wrote: On Tue, 24 Oct 2017 05:35:34 -0700 Patricia Shanahan wrote: Since the issue appeared in 4.1.4, and involves document links, it might be related to my changes. I do not have a Mac, and do not have any Mac debug experience. How do people think we

Re: Issue for 4.1.4 and MacOS

On Tue, 24 Oct 2017 05:35:34 -0700 Patricia Shanahan wrote: > Since the issue appeared in 4.1.4, and involves document links, it might > be related to my changes. > > I do not have a Mac, and do not have any Mac debug experience. > > How do people think we should proceed with this? Is there a

Re: Issue for 4.1.4 and MacOS

Since the issue appeared in 4.1.4, and involves document links, it might be related to my changes. I do not have a Mac, and do not have any Mac debug experience. How do people think we should proceed with this? Is there a Mac developer who can work with me on it? On 10/24/2017 4:40 AM, Larry

Re: Issue for 4.1.4 and MacOS

On 2017-10-24, 4:19 AM FR web forum wrote: Please have a look on: https://bz.apache.org/ooo/show_bug.cgi?id=127568 I tested and confirm the problem. Posted my result on the bug report. -- _ Larry I. Gusaas Moose Jaw, Saskatchewan Canada Website: http://larry-

Issue for 4.1.4 and MacOS

Please have a look on: https://bz.apache.org/ooo/show_bug.cgi?id=127568 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org