patchGNU nano - Patches: patch #9942, Meson port of Nano

 
 

You are not allowed to post comments on this tracker with your current authentication level.

patch #9942: Meson port of Nano

Submitter:  Salamandar <salamandar>
Submitted:  Tue 16 Jun 2020 02:51:21 PM UTC
   
 
Priority:  3 - Low Status:  Need Info
Privacy:  Public Assigned to:  None
Open/Closed:  Closed Release:  None

Mon 22 Jun 2020 08:19:14 AM UTC, comment #5: 

The cryptic error cannot occur when pkg.m4 was found during the run of autogen.sh.  When configure complains about pkg.m4, you need to run autogen.sh again.  Yes, it's annoying and unobvious, but if you want to build from git... you need some stamina.

What would converting the build system to Meson bring?

Benno Schulenberg <bens>
Group administrator
Sun 21 Jun 2020 06:08:05 PM UTC, comment #4: 


>  That's the same issue: pkg.m4 not being found and thus causing a cryptic error in ./configure.


No. I solved the first issue and then this issue popped up.

Anyways, this is exactly why i said in my original post "I won't discuss again here. " ;)
I spent too much time debugging Autotools (not on Nano, I mean in general) and I just don't want to do it anymore.
Those issues happen on a Centos 7 install that I had to drop this week, so I won't even be able to reproduce.

Can this thread be about Meson and whether this can be interesting for Nano ? :)

Salamandar <salamandar>
Wed 17 Jun 2020 10:15:10 AM UTC, comment #3: 


> * pkg.m4 was not detected.


What's the output of 'aclocal --print-ac-dir'?  If the pkg.m4 is not in that directory, then where is it on your system?  If you export PKG_CONFIG_PATH="relevant directory" and then run ./autogen.sh again, does ./configure then find pkg.m4 and succeed?


> * This bug : https://savannah.gnu.org/bugs/?44630


That's the same issue: pkg.m4 not being found and thus causing a cryptic error in ./configure.


> fatal: reference is not a tree: 360979fd6fb84567e0ffc6839b0431fc00d6362f


Ah.  That is because the 'git clone' of gnulib is too shallow: --depth=123.  I had limited the depth to reduce the cloning time, but when not updating the hash for a while, the desired commit is more than 123 commits back.  :|  Increasing the depth to 234 would work in this case, but I'll make it 1234.


> Maybe lowering the required versions of autoconf/gettext would resolve the last issue, but I'm not sure that would be 100% functionnal…


The "required" versions are higher than what is actually needed.  At some point Mike used a feature of autoconf that needed the higher version, but the use of that feature has been removed again, so... take the required versions in autoconf scripts with a big grain of salt.

Benno Schulenberg <bens>
Group administrator
Wed 17 Jun 2020 08:35:17 AM UTC, comment #2: 

Hi Ben,
The 3 main issues I had were :

  • pkg.m4 was not detected. That may not have been an issue with nano's build system but with autotools itself on CentOS.



  • another issue :


autogen.sh told me :
fatal: reference is not a tree: 360979fd6fb84567e0ffc6839b0431fc00d6362f
then configure told me :
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."



I was building from git master :) Maybe lowering the required versions of autoconf/gettext would resolve the last issue, but I'm not sure that would be 100% functionnal…

Salamandar <salamandar>
Tue 16 Jun 2020 03:12:09 PM UTC, comment #1: 

Hello Félix,

What issues did you have while trying to compile nano?  And is that while compiling from a tarball or from git?  Do you have a URL of where these issues are documented/discussed?  What version of CentOS are you using?

(On one of my old machines I have to lower the required versions of gettext and autoconf to get nano to compile.  Maybe the same would be enough on your CentOS machine?)

Benno Schulenberg <bens>
Group administrator
Tue 16 Jun 2020 02:51:21 PM UTC, original submission:  

I've had a very hard time compiling a recent version of Nano on my CentOS workstation, due to multiple issues already documented/discussed that I won't discuss again here.

I did a port to Meson to finally get to compile Nano, with success.

My code is here : https://gitlab.freedesktop.org/Salamandar/nano/-/tree/meson

What do you think about it ?

I did not implement the use of gnulib for now, but if you think my changes can be integrated, maybe I'll need to work on this.

Thanks for the feedback !

Salamandar <salamandar>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by bens (Posted a comment)
  • -email is unavailable- added by salamandar (Submitted the item)
  • -email is unavailable- added by salamandar
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-10-01 bens Open/ClosedOpen Closed
    2020-06-21 bens StatusNone Need Info
    2020-06-16 salamandar Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code