public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] audacity-2.0.5 failed to compile
Date: Wed, 02 Sep 2015 07:04:34 -0500	[thread overview]
Message-ID: <55E6E5D2.8050305@gmail.com> (raw)
In-Reply-To: <55E6E269.2030303@gmail.com>

Alan McKinnon wrote:
> On 02/09/2015 06:57, wraeth wrote:
>> On 02/09/15 14:24, thelma@sys-concept.com wrote:
>>> On 09/01/2015 08:57 PM, wraeth wrote:
>>>> On 02/09/15 12:23, Fernando Rodriguez wrote:
>>>>
>>>>> He was told what the problem was on his first post about 
>>>>> libjpeg-turbo, he didn't just ignore it but posted the wrong 
>>>>> solution with a big SOLVED on the subject that only serves to 
>>>>> mislead future users of this list. On his last post about this 
>>>>> same error (different package) I politely told him to go back
>>>>> and follow the advise on that post, again he ignored it and
>>>>> posted a bogus solution (it worked because he rebuilt tiff,
>>>>> perl had nothing to do with it). revdep-rebuild may (or may
>>>>> not) fix it now, but the right solution is to remove or fix the
>>>>> obsolete package to depend on virtual/jpeg, update world
>>>>> properly, and then revdep-rebuild to undo this mess.
>>> Apology if I didn't most enough information. I know should have
>>> post "emerge --info" but when it comes to error log.  It is very,
>>> very long and email wouldn't be able to accept it; so I cat the
>>> ending message as this is the point it stop compiling.
>> For large files, you can either paste the file to a pastebin service
>> and give us the URL, compress it with gzip or bzip2 and attach that,
>> or give us the last 250 lines or so.
>
> Every list has their own particular preference to things. Here on
> gentoo-user, since the very beginning, list users have preferred to not
> use pastebin services - they go away and the real information is forever
> lost.
>
> There's never a good reason for use needing an entire build log if it's
> big, it's fine to find the first error in the log and send from there to
> the end. Users quickly discover how to find the first error.
>


I have found that it is usually "Error 1".  That's what I put in the
Find thingy to look for IF it is not real close by.  I generally go up a
few lines and then start my copy and paste. 

I can't count how many times I have searched for a problem and run into
paste bin links that no longer work.  It is really aggravating when you
think you found something and it turns out it has disappeared.

Dale

:-)  :-) 


  reply	other threads:[~2015-09-02 12:04 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 22:04 [gentoo-user] audacity-2.0.5 failed to compile thelma
2015-09-01 22:55 ` Fernando Rodriguez
2015-09-01 23:05   ` thelma
2015-09-02  1:22     ` Alec Ten Harmsel
2015-09-02  2:23       ` Fernando Rodriguez
2015-09-02  2:57         ` wraeth
2015-09-02  4:24           ` thelma
2015-09-02  4:57             ` wraeth
2015-09-02  5:59               ` Mick
2015-09-02 11:50               ` Alan McKinnon
2015-09-02 12:04                 ` Dale [this message]
2015-09-02 20:25               ` thelma
2015-09-03 13:06                 ` Alec Ten Harmsel
2015-09-03 13:19                   ` Alan McKinnon
2015-09-03 13:56                     ` thelma
2015-09-03 14:27                       ` Alan McKinnon
2015-09-03 17:22                         ` Alec Ten Harmsel
2015-09-03 20:10                           ` Alan McKinnon
2015-09-03 18:57                         ` Fernando Rodriguez
2015-09-03 19:11                         ` thelma
2015-09-03 19:30                           ` Mick
2015-09-03 19:41                             ` thelma
2015-09-03 20:35                           ` Alan McKinnon
2015-09-04  8:34                             ` Neil Bothwick
2015-09-03 19:24                         ` Mick
2015-09-03 19:56                           ` thelma
2015-09-03 20:41                             ` Alan McKinnon
2015-09-04  8:38                             ` Neil Bothwick
2015-09-04 13:24                               ` Alan McKinnon
2015-09-04 21:31                                 ` Neil Bothwick
2015-09-04  9:42                         ` Peter Humphrey
2015-09-04 10:00                           ` Mick
2015-09-04 10:19                             ` Peter Humphrey
2015-09-04 10:31                           ` Neil Bothwick
2015-09-04 10:48                             ` Peter Humphrey
2015-09-04 13:26                           ` Alan McKinnon
2015-09-03 14:28                       ` Neil Bothwick
2015-09-03 15:26                         ` thelma
2015-09-03 15:31                           ` Alan McKinnon
2015-09-03 15:33                           ` thelma
2015-09-03 16:16                             ` Alexander Kapshuk
2015-09-03 17:22                               ` Neil Bothwick
2015-09-03 20:44                       ` Dale
2015-09-02 13:28             ` [gentoo-user] " James
2015-09-02  5:55           ` [gentoo-user] " Fernando Rodriguez
2015-09-02  9:15             ` Gevisz
2015-09-02  9:50               ` wraeth
2015-09-02 18:52       ` Andreas K. Huettel
2015-09-02 20:31         ` Alan McKinnon
2015-09-03 12:47         ` Alec Ten Harmsel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E6E5D2.8050305@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox