Activity
From 05/30/2023 to 06/28/2023
06/08/2023
- 07:39 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Greg Shah wrote:
> Eugenie Lyzenko wrote:
> > Greg Shah wrote:
> > > I've renamed and made edits to the wiki page ... - 05:02 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- > Seems like we need to update Redmine download directory replacing @setup_ncurses6x.sh@ with recent one from Roger.
... - 04:57 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- > > Then there's patching @terminfo@. Is that now a one-time occurrence, or does that need to stay in the @manage_ter...
- 04:54 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Eugenie Lyzenko wrote:
> Greg Shah wrote:
> > I've renamed and made edits to the wiki page ([[p2j:Patching NCURSES ... - 09:18 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Eugenie Lyzenko wrote:
> Please remove the previous problematic script file to ensure the correct one will be used.
...
06/07/2023
- 07:30 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> So sorry... I had posted the version with "cr*p" in it. The subsequent one that supports Red... - 07:12 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- So sorry... I had posted the version with "cr*p" in it. The subsequent one that supports Red Hat should work better.
... - 07:09 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Eugenie Lyzenko wrote:
> > Thanks for this question. I have updated the static ncurses inst... - 07:07 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Actually this one attached I have made updates that should work on Red Hat. I based it off the @patch_ncurses6-centos...
- 06:31 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Eugenie Lyzenko wrote:
> Thanks for this question. I have updated the static ncurses instruction section.
>
> Bot... - 05:59 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Thanks... one more docker-related question. The docker image contained some runtime support ... - 03:26 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Thanks... one more docker-related question. The docker image contained some runtime support packages:
* libncurses5-... - 02:03 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Greg Shah wrote:
> > I think we just create a new patched ncurses every time we build FWD f... - 12:51 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Greg Shah wrote:
> I think we just create a new patched ncurses every time we build FWD for Docker. It will always ... - 12:38 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Greg Shah wrote:
> I've renamed and made edits to the wiki page ([[p2j:Patching NCURSES Using Static Linking]]. I'v... - 10:16 AM Support #5167 (Closed): using static linking to eliminate the need to patch the system-wide ncurses
- I've renamed and made edits to the wiki page ([[p2j:Patching NCURSES Using Static Linking]]. I've also linked it int...
06/06/2023
- 06:36 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Branch @5167a@ was merged to trunk as revno @14616@ then it was archived.
This change will be on replica later tod... - 05:46 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Greg Shah wrote:
> You can go ahead and merge to trunk. Please provide documentation on how to use it in the merge ... - 05:39 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- You can go ahead and merge to trunk. Please provide documentation on how to use it in the merge email.
- 05:29 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- I think we just create a new patched ncurses every time we build FWD for Docker. It will always be the latest availa...
- 03:19 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Eugenie Lyzenko wrote:
> > >Or is there an ongoing need to hook @apt@ still?
> >
> > I d... - 02:23 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Eugenie Lyzenko wrote:
> >Or is there an ongoing need to hook @apt@ still?
>
> I do not know any such requirement... - 02:04 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> The container project to build FWD Docker images will need to modify the "patching" process.... - 01:39 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The container project to build FWD Docker images will need to modify the "patching" process.
Currently it unzips t... - 01:25 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Greg Shah wrote:
> > > if we are planning that everyone would abandon the arduous ncurses ... - 01:18 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Greg Shah wrote:
> > if we are planning that everyone would abandon the arduous ncurses patching
>
> To be clear... - 01:03 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- > if we are planning that everyone would abandon the arduous ncurses patching
To be clear, this doesn't avoid pat... - 11:51 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Yes, let's avoid the more complex naming. If everything is working, then we can move ahead with this branch.
- 11:34 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Greg Shah wrote:
> Roger: Please test 5167a with a real customer application using both static and non-static approa... - 11:03 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Eugenie Lyzenko wrote:
> > I think no need to have both libraries with different names. You... - 10:46 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Eugenie Lyzenko wrote:
> I think no need to have both libraries with different names. You can identify the static ve... - 10:22 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Is the testing methodology to build FWD with/without:
> [...]
> in my environment, and uti... - 10:13 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Is the testing methodology to build FWD with/without:...
- 10:07 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger Borrello wrote:
> Greg Shah wrote:
> > Roger: Please test 5167a with a real customer application using both s... - 10:05 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The @5167a@ rebased with trunk revision @14615@. The new revision is @14618@.
- 09:57 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Greg Shah wrote:
> Roger: Please test 5167a with a real customer application using both static and non-static approa... - 09:54 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- Roger: Please test 5167a with a real customer application using both static and non-static approaches.
- 09:32 AM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The @5167a@ rebased with trunk revision @14614@. The new revision is @14617@.
06/05/2023
- 04:25 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The @5167a@ rebased with trunk revision @14612@. The new revision is @14615@.
06/03/2023
- 05:23 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The @5167a@ rebased with trunk revision @14606@. The new revision is @14609@.
- 08:16 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The @5167a@ rebased with trunk revision @14605@. The new revision is @14608@.
06/02/2023
- 09:10 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The @5167a@ rebased with trunk revision @14599@. The new revision is @14602@.
05/31/2023
- 04:16 PM Support #5167: using static linking to eliminate the need to patch the system-wide ncurses
- The @5167a@ rebased with trunk revision @14594@. The new revision is @14597@.
05/30/2023
- 11:47 AM Bug #7083 (Rejected): P2J Native Build Cannot Find -ljvm Under Windows
- 10:18 AM Bug #7083: P2J Native Build Cannot Find -ljvm Under Windows
- Thank you, Eugenie, copying the file fixed it. I updated my guide as well [[p2j:Windows 11 Virtual Machine Setup with...
- 09:10 AM Bug #7083: P2J Native Build Cannot Find -ljvm Under Windows
- Galya B wrote:
> Note: The temporal solution works with an absolute path, where %JAVA_HOME% is replaced by the actua... - 08:30 AM Bug #7083: P2J Native Build Cannot Find -ljvm Under Windows
- Note: The temporal solution works with an absolute path, where %JAVA_HOME% is replaced by the actual path.
Also available in: Atom