No subject


Tue Mar 18 03:57:02 CET 2008


> Ok, maybe you should have a look again into the directory
> %KDEROOT%\manifest. The files in there state which packages you have
> installed. If you remove all files there, then emerge should behave
> differently.
> Please have a look again that the 'installed' file is empty as well.
> and then instead of 'emerge kdesdk' you can run as well
> 'emerge -v -v kdesdk'. (That switches on debug output.)
>
> SE
>

------=_Part_2619_11998816.1199839789060
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,<br><br>The file C:\kderoot\etc\portage\installed is 0 bytes long.<br>I had deleted the &#39;manifest&#39; folder, so I recreated it, empty.&nbsp; Tried the build, still the same.&nbsp; <br>I ran &#39;emerge -v -v kdesdk&#39;.&nbsp; The only thing that looks suspicious to me in the output is that there are many lines that say
<br>emerge doExec called opts: []<br>In fact there is no &#39;emerge doExec called opts:&#39; line that has anything in the square brackets [].<br>Does this help?&nbsp; I can send the full output of the &#39;emerge -v -v kdesdk&#39; command, but it&#39;s very long...
<br><br>Thanks,<br>Clint<br><br>From Saro Engels:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Ok, maybe you should have a look again into the directory
<br>%KDEROOT%\manifest. The files in there state which packages you have<br>installed. If you remove all files there, then emerge should behave<br>differently.<br>Please have a look again that the &#39;installed&#39; file is empty as well.
<br>and then instead of &#39;emerge kdesdk&#39; you can run as well<br>&#39;emerge -v -v kdesdk&#39;. (That switches on debug output.)<br><br><font color="#888888">SE<br></font></blockquote></div><br>

------=_Part_2619_11998816.1199839789060--



More information about the Kde-windows mailing list