Opened 4 years ago

Closed 18 months ago

#12130 closed enhancement (no change required)

Haiku buildtools contains old in-tree softwares

Reported by: miqlas Owned by: bonefish
Priority: normal Milestone: Unscheduled
Component: Build System Version: R1/Development
Keywords: buildtools Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Why Haiku using old-old autoconf and libtool in the buildtools ( https://git.haiku-os.org/buildtools )? I does not mean the "legacy" folder!

  • Our autoconf is 2.61, but the latest version is 2.69 (it is a 6 years long span between the two version)
  • Our libtool is 1.5.2, while the latest is 2.4.6 (almost 10 years long span)
  • Our isl is 1 year old.

I swapped these softwares to the latest version, and tried to make a test build on OSX, but i got some errors at configuring binutils (i have no problem with the original in-tree version). So it seems, there is some not-upstreamed Haiku specific patches and mods in these softwares. IT would be great to upstream these changes (if any), and update the in-tree softwares to the latest version.

Change History (2)

comment:1 Changed 4 years ago by pulkomandy

These are used only to build the buildtools, as you can check from the Haiku command line:

~> autoconf --version
autoconf (GNU Autoconf) 2.69
~> libtool --version
libtool (GNU libtool) 2.4.2

We update these only when needed by a new gcc version, I think. Since they are only used to build the compiler, it doesn't really matter to keep them up to date.

You can see the changes by looking at each specific folder: https://cgit.haiku-os.org/buildtools/log/autoconf In the case of autoconf it seems there are not a lot of changes (just a single one).

comment:2 Changed 18 months ago by waddlesplash

Resolution: no change required
Status: newclosed

So, no changes needed here then; buildtools can do what it likes.

Note: See TracTickets for help on using tickets.