How to trace down compilation issues if the compilation does not break...?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

How to trace down compilation issues if the compilation does not break...?

tuxic
Hi,

the usual event, if something comilation-related, is a list
of all files, which could be examined to find the problem
and a lot of styff put under /var/tmp/portage...

I have a problem with the Krita-installation and I think it
is a wrong way of configuration of the compilation problem.

The problem with this problem is, that the compilation process
is successful and all files will be removed from /var/tmp/portage
afterwards.

I checked the manpage of emerge to find an option to prevent the
deletion of the remainders, but found nothing.

Is there a way to keep these?

Thanks a lot in advance for any help!
Cheers!
Meino



Reply | Threaded
Open this post in threaded view
|

Re: How to trace down compilation issues if the compilation does not break...?

Rich Freeman
On Sun, Jan 6, 2019 at 10:31 AM <[hidden email]> wrote:
>
> The problem with this problem is, that the compilation process
> is successful and all files will be removed from /var/tmp/portage
> afterwards.
>

If you already have the dependencies installed all you have to do is
chdir to the directory with the ebuild and run:
ebuild krita-x.y.z.ebuild configure
You can use compile/install to step through the compile and install
steps.  In general you can just go straight to install and end up with
a complete build and install image, but it won't touch your actual
root filesystem.

Note that the ebuild tool is mainly intended for troubleshooting
ebuilds and such - it does not resolve dependencies, so you need to
take care of that before running it.

If you need to start over just run the clean command.  man ebuild...

--
Rich

Reply | Threaded
Open this post in threaded view
|

Re: How to trace down compilation issues if the compilation does not break...?

Nikos Chantziaras-2
In reply to this post by tuxic
On 06/01/2019 17:31, [hidden email] wrote:
> The problem with this problem is, that the compilation process
> is successful and all files will be removed from /var/tmp/portage
> afterwards.
>
> I checked the manpage of emerge to find an option to prevent the
> deletion of the remainders, but found nothing.

You can set FEATURES=keeptemp while emerging the package for which you
want to keep the tmp files. In your case:

   sudo FEATURES=keeptemp emerge -1 media-gfx/krita


Reply | Threaded
Open this post in threaded view
|

Re: How to trace down compilation issues if the compilation does not break...?

tuxic
On 01/07 06:38, Nikos Chantziaras wrote:

> On 06/01/2019 17:31, [hidden email] wrote:
> > The problem with this problem is, that the compilation process
> > is successful and all files will be removed from /var/tmp/portage
> > afterwards.
> >
> > I checked the manpage of emerge to find an option to prevent the
> > deletion of the remainders, but found nothing.
>
> You can set FEATURES=keeptemp while emerging the package for which you want
> to keep the tmp files. In your case:
>
>   sudo FEATURES=keeptemp emerge -1 media-gfx/krita
>
>

Hi NIKOS,

THANKS A LOT! Exactly this information it was, which I was searching
for! :)

Cheers!
Meino