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] New profile, gcc-13.2.1_p20240210 fails to build. ATTN: Peter Humphrey.
Date: Sat, 23 Mar 2024 16:28:27 -0500	[thread overview]
Message-ID: <dc9cdce6-dda3-c6e4-8066-dba8d2d1cfa9@gmail.com> (raw)
In-Reply-To: <12406261.O9o76ZdvQC@rogueboard>

Michael wrote:
> On Saturday, 23 March 2024 20:45:03 GMT Dale wrote:
>> Howdy,
>>
>> I'm doing this in a chroot.  This is *not* my live system.  This is the
>> mount info, in case it matters. 
>>
>> <<<SNIP>>>
>>
>>
>> I saw where Peter mentioned in another thread gcc failing with no error
>> message for him.  This could be related.  A solution to this may help
>> more than just me.  I'm not sure how to diagnose a failure when it gives
>> no real error.  Heck, having a error sometimes isn't much help.  :/  I
>> might add, the errors listed above didn't stop the compile until close
>> to the end.  It did seem to ignore them since it compiled a good while
>> afterwards.  I'm including in case those errors lead to the failure
>> later on.  They could be nothing or may be a clue. 
>>
>> Open to ideas. 
>>
>> Dale
>>
>> :-)  :-) 
> Hmm ... my gcc is failing on one of my installations, with no error ... after 
> it built successfully once already, as part of the initial toolchain update. 
> :-/
>
> OK, I'm out of ideas too.  May have to sleep on this and look at it again 
> tomorrow.  


Nice to know I'm not alone.  I forgot to mention, it wanted to update
glibc first.  The news item said NOT to let it do that and use the
--nodeps option instead.  So, the command I used had that option.  I've
since restarted it, just in case it finishes.  I'll post back if it
does.  I find it odd that it builds fine one time but fails on others. 
Strange things happen tho. 

Dale

:-)  :-) 


  reply	other threads:[~2024-03-23 21:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 20:45 [gentoo-user] New profile, gcc-13.2.1_p20240210 fails to build. ATTN: Peter Humphrey Dale
2024-03-23 20:48 ` Michael
2024-03-23 21:28   ` Dale [this message]
2024-03-23 21:33     ` Michael
2024-03-23 21:49       ` Dale
2024-03-24  9:51         ` Paul Colquhoun
2024-03-25  7:04           ` Dale
2024-03-25  9:33             ` Michael
2024-03-25 10:16             ` ralfconn
2024-03-25 14:47             ` Peter Humphrey
2024-03-26  7:30           ` Paul Colquhoun
2024-03-25 14:44 ` Peter Humphrey

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=dc9cdce6-dda3-c6e4-8066-dba8d2d1cfa9@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