glen martin wrote:
> I'm still puzzled, though, that I can call chown by hand and it
> works fine. That
> is, I type
>chown portage:portage /tmp/foo
> which works. but the emerge log says
>/usr/lib/portage/bin/ebuild.sh: line 1882: 16369 Segmentation
> fault chown portage:portage "${T}/env
Benno Schulenberg wrote:
>glen martin wrote:
>
>
>>This is an EPIA PD6000, which like the ME6000 uses the Samuel 2
>>processor. So I used those CFLAGS with other tweaks mentioned on
>>the same page.
>>
>>CFLAGS="-march=i586 -m3dnow -Os -pipe -fomit-frame-pointer -mmmx"
>>
>>
>
>What happens
glen martin wrote:
> This is an EPIA PD6000, which like the ME6000 uses the Samuel 2
> processor. So I used those CFLAGS with other tweaks mentioned on
> the same page.
>
> CFLAGS="-march=i586 -m3dnow -Os -pipe -fomit-frame-pointer -mmmx"
What happens if you recompile coreutils (containing chown a
On Wed, 2005-05-18 at 20:10 +0200, Benno Schulenberg wrote:
> glen martin wrote:
> > /usr/lib/portage/bin/ebuild.sh: line 1882: 16369 Segmentation
> > fault chown portage:portage "${T}/environment" >&/dev/null
> > /usr/lib/portage/bin/ebuild.sh: line 1882: 10308 Segmentation
> > fault chmod g+w "${
glen martin wrote:
> /usr/lib/portage/bin/ebuild.sh: line 1882: 16369 Segmentation
> fault chown portage:portage "${T}/environment" >&/dev/null
> /usr/lib/portage/bin/ebuild.sh: line 1882: 10308 Segmentation
> fault chmod g+w "${T}/environment" >&/dev/null
>
> FWIW, this is an x86-ish platform, EPI
I'm not sure how things got this way (something to do with not watching
emerge output closely so not knowing when the problem started
precisely). And I'm somewhat newbie, by which I don't expect any
particular allowances but you may wish to keep in mind in thinking about
what stupid mistakes I may
6 matches
Mail list logo
