Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 603790 - dev-lang/gnat-gcc - Cannot find $EPATCH_SOURCE! files/gnat-gcc-4.9.3-make-default-paths-match-slot.patch
Summary: dev-lang/gnat-gcc - Cannot find $EPATCH_SOURCE! files/gnat-gcc-4.9.3-make-def...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-26 20:24 UTC by Michael Mounteney
Modified: 2017-03-15 00:20 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Mounteney 2016-12-26 20:24:32 UTC
Ebuilding dev-lang/gnat-gcc fails and the command "cat $PORTAGE_TMPDIR/portage/dev-lang/gnat-gcc-4.9.3/temp/build.log" outputs:

....
[ ok ]
 *   Updating config.guess
 [ ok ]
 * Fixing misc issues in configure files

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 * 
 *   /usr/portage/dev-lang/gnat-gcc/files/gnat-gcc-4.9.3-make-default-paths-match-slot.patch
 *   ( gnat-gcc-4.9.3-make-default-paths-match-slot.patch )

 * ERROR: dev-lang/gnat-gcc-4.9.3::gentoo failed (unpack phase):
 *   Cannot find $EPATCH_SOURCE!
 * 
 * Call stack:
...

Are the maintainers of gnat-gcc replacing the ebuild without incrementing the version (sub-)number or patch level ?
Comment 1 sschneid 2017-02-14 15:21:07 UTC
ebuild dev-lang/gnat-gcc-4.9.3 failed. 

...
 *   Updating libjava/libltdl/config.guess                                                                            [ ok ]
 *   Updating libjava/classpath/config.guess                                                                          [ ok ]
 *   Updating config.guess                                                                                            [ ok ]
 * Fixing misc issues in configure files

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 * 
 *   /usr/portage/dev-lang/gnat-gcc/files/gnat-gcc-4.9.3-make-default-paths-match-slot.patch
 *   ( gnat-gcc-4.9.3-make-default-paths-match-slot.patch )

 * ERROR: dev-lang/gnat-gcc-4.9.3::gentoo failed (unpack phase):
 *   Cannot find $EPATCH_SOURCE!
 * 
 * Call stack:
 *     ebuild.sh, line  115:  Called src_unpack
...

It complains about a missing gnat-gcc-4.9.3-make-default-paths-match-slot.patch in the /usr/portage/dev-lang/gnat-gcc/files/. Its the same fail reason as mentioned in the original ticket. 

In commit "c4b4d9a83711610c09f8db31919b095a4d9628f2" this file was added to the portage repository (https://gitweb.gentoo.org/repo/gentoo.git/commit/dev-lang/gnat-gcc/files?id=c4b4d9a83711610c09f8db31919b095a4d9628f2) but in the current portage snapshot it is missing. 

I manually added the two files:

gnat-gcc-4.9.3-make-default-paths-match-slot.patch
gcc-spec-env-r1.patch

to the /usr/portage/dev-lang/gnat-gcc/files directory and rebuild the Manifest:

ebuild gnat-gcc-4.9.3.ebuild manifest

Afterwards I was able to install the gnat compiler and build a hello world program:

user@wks234 /tmp/tmp.0vkPeyDTdf $ cat hello.adb 
    with Ada.Text_IO; use Ada.Text_IO;
    procedure Hello is
    begin
       Put_Line ("Hello WORLD!");
    end Hello;
user@wks234 /tmp/tmp.0vkPeyDTdf $ gnatmake hello.adb 
gnatgcc -c hello.adb
gnatbind -x hello.ali
gnatlink hello.ali
user@wks234 /tmp/tmp.0vkPeyDTdf $ ./hello 
Hello WORLD!



Best regards...
Stephan



I
Comment 2 Michael Mounteney 2017-02-22 21:46:08 UTC
I would like to take over maintenance of this package but do need help.  I'm a programmer but have never been involved in emerge or portage beyond trivial fixes and don't know how to take a new release of FSF gnat-gcc from .tar.gz to an ebuild update.  I assume there is a canned process of some sort involving packaging and unit tests.
Comment 3 Michael Palimaka (kensington) gentoo-dev 2017-02-23 08:29:04 UTC
(In reply to Michael Mounteney from comment #2)
> I would like to take over maintenance of this package but do need help.  I'm
> a programmer but have never been involved in emerge or portage beyond
> trivial fixes and don't know how to take a new release of FSF gnat-gcc from
> .tar.gz to an ebuild update.  I assume there is a canned process of some
> sort involving packaging and unit tests.

Check out https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers and feel free to join us in #gentoo-proxy-maint on freenode.

As for adding a new version there's not really any right or wrong to do it, but it's common to copy the existing ebuild to the new version and look to see if there's any changes upstream that might need reflecting in the ebuild.
Comment 4 Michael Mounteney 2017-02-27 05:19:12 UTC
(In reply to Michael Palimaka (kensington) from comment #3)
> Check out https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers and feel
> free to join us in #gentoo-proxy-maint on freenode.
> 
> As for adding a new version there's not really any right or wrong to do it,
> but it's common to copy the existing ebuild to the new version and look to
> see if there's any changes upstream that might need reflecting in the ebuild.

I would like to help, as GCC is now at version 6.3.0 so gnat-gcc has fallen behind;  however, I'm puzzled because according to http://www.gnu.org/software/gnat/ Ada is built into the GCC suite but Gentoo packages it separately.

At the very least, surely we should release gnat-gcc-4.9.3-r1 with the two files added, as identified by Stephan, above.
Comment 5 Steve Arnold archtester gentoo-dev 2017-03-14 21:13:35 UTC
Actually I could use some help with Ada stuff, since George disappeared (but technically I think he is still active?).  I haven't mentored anyone for quite a while, and I'm on the hook for BeagleBoard mentoring this summer (so far anyway).  Feel free to pursue that and I'll help as I can.

Pushing the missing patch now, so we should start the clock on stablizing 4.9.3 since the older ones are dorked enough already (along with the old gnatbuild.eclass).

The main thing for bootstrapping a newer version is (literally) the gnatnatboot tarball since at some point older bootstrap toolchain will fail.  That said, the 4.9.3 bootstrap tarball *should* work to build 5.3/4 (but maybe not 6.x).

Easy way to test is just copy the 4.9.3 ebuild to 5.4.0 ebuild and leave BOOT_SLOT set to 4.9.
Comment 6 Steve Arnold archtester gentoo-dev 2017-03-15 00:20:18 UTC
Tested clean (needed one more patch, obviously I haven't touched this for a while).  Wait for sync, test away.  Closing...