From: "Thomas Rösner" <Thomas.Roesner@digital-trauma.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] chroot can't find /bin/bash
Date: Wed, 07 Feb 2007 05:20:26 +0100 [thread overview]
Message-ID: <45C9538A.3070408@digital-trauma.de> (raw)
In-Reply-To: <a4a9bfcb0702061903h2b142166v65a67953867f0064@mail.gmail.com>
Daiajo Tibdixious schrieb:
> transcode is giving me a segmentation fault, which I reported as a bug.
> They now want a backtrace & I've roughly followed
> http://www.gentoo.org/proj/en/qa/backtraces.xml
> I used ebuild directly, ending at the install phase, as I don't want
> to overwrite the live transcode.
Would splitdebug make you happy, or making a quickpackage of the
original files, qmerging the debug ones, installing the quickpackaged
files back? The other alternative I see to get at this is a union mount
on /usr.
Regards,
Thomas
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-07 4:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 3:03 [gentoo-amd64] chroot can't find /bin/bash Daiajo Tibdixious
2007-02-07 4:20 ` Thomas Rösner [this message]
2007-02-07 5:33 ` Daiajo Tibdixious
2007-02-07 5:38 ` Daiajo Tibdixious
2007-02-07 10:14 ` Boyd Stephen Smith Jr.
2007-02-07 10:34 ` Naga
2007-02-07 10:54 ` Daiajo Tibdixious
2007-02-07 23:56 ` Marek Wróbel
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=45C9538A.3070408@digital-trauma.de \
--to=thomas.roesner@digital-trauma.de \
--cc=gentoo-amd64@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