Heiko Wundram writes:
> On Wed, 15 Jul 2009 16:13:01 -0500, Harry Putnam
> wrote:
>>
>> So far I haven't found any instance of i486 files remaining on the
>> system... what else might evoke that output?
>
> As I said: some Python makefile retains the reference to the (former) i486
> compiler. T
On Wed, 15 Jul 2009 16:13:01 -0500, Harry Putnam
wrote:
>
> So far I haven't found any instance of i486 files remaining on the
> system... what else might evoke that output?
As I said: some Python makefile retains the reference to the (former) i486
compiler. That Makefile is used when building
Harry Putnam writes:
> Also ... anyone have another idea how to iron this out. I've done
> everything suggested here in this thread but still cannot compile
> pycairo successfully.
How about it folks... anymore suggestions on this:
emerge error:
[...]
building 'cairo._cairo' extension
creating
Volker Armin Hemmann writes:
>> That went off without error, but then going back to update world fails
>> at pycairo with same error message.
>
> you could grep for i486-pc-linux-gnu-gcc
I'm not sure what you had in mind there... or where to grep -r but a
grep -r from `/' has run for several hou
On Dienstag 14 Juli 2009, Harry Putnam wrote:
> Volker Armin Hemmann writes:
>
>
> [...]
>
> >> i486-pc-linux-gnu-gcc: No such file or directory error: command
> >> 'i486-pc-linux-gnu-gcc' failed with exit status 1
> >> [...]
> >
> > did you run fix-libtool.sh?
>
> Doing so failed to help in any w
Volker Armin Hemmann writes:
[...]
>> i486-pc-linux-gnu-gcc: No such file or directory error: command
>> 'i486-pc-linux-gnu-gcc' failed with exit status 1
>> [...]
>
> did you run fix-libtool.sh?
Doing so failed to help in any way.
root # fix_libtool_files.sh `gcc -dumpversion` --oldarch i486
6 matches
Mail list logo
