Re: [Astlinux-users] Compile problems with i686 as the TargetArchitecture Variant

[Sebastian A. <sp...@sy...>]

Glad to hear it.  Did you specify a VIA device or a Generic i586 device
though?
=20
P. S.  I finally got 0.4 branch and trunk to finish the make process.
*relief* :-)
=20
Sebastian


  _____ =20

From: ast...@li...
[mailto:ast...@li...] On Behalf Of
olivier.taylor
Sent: 18 January 2007 19:22
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Compile problems with i686 as the
TargetArchitecture Variant


Sebastian,

I have an HP 5500 thin client (Via chip) running perfectly here with the
I586 build, just Fyi.

Olivier

Sebastian Auriol a =E9crit :=20

Kristian,



Thanks for the feedback and links. I have switched to i586 and Generic =
i586

device for now and it seems to be going OK, except that I ran out of =
disk

space at one point and I was missing uudecode. I had to basically start

again after the disk space problem: cp -r dl dl-bak ; make clean ; make

distclean ; rm -f -r toolchain_build_i586 ; svn update ; make

If I didn't delete toolchain_build_i586 it would just immediately bomb

again.



ftp://ftp.samba.org/ isn't working today but I found the file at

http://samba.org/ftp/ppp/ppp-2.4.3.tar.gz (btw, there is a newer version

available too). I copied the file into the dl directory manually, but it =
is

still retrying via FTP (try: 4) and the timeouts are extremely long. Is

there anyway to cancel the getter_script.sh without cancelling the make? =
The

server has spent so long getting to this point I don't want to have to =
start

it again.



Having said that, I would be willing to try VIA with i586. Is this =
likely to

work then? What are the differences between Generic i586 and VIA builds?

Presumably it will overwrite build_i586/root so I'd want to back that =
up...



I saw your svn changes. :)



Is trunk nearly ready for a release? Or more importantly for me right =
now,

should it be stable?



Thanks for your help. This is my first time trying to compile AstLinux. =
I

need to add support, i.e. drivers, for a device that is not supported in =
the

standard build. How do I go about doing this? Presumably I can do it =
after

the main make has finished...



Sebastian





-----Original Message-----

From: ast...@li...

[mailto:ast...@li...] On Behalf Of =
Kristian

Kielhofner

Sent: 18 January 2007 15:52

To: AstLinux Users Mailing List

Subject: Re: [Astlinux-users] Compile problems with i686 as the

TargetArchitecture Variant



On 1/18/07, Sebastian Auriol  <mailto:sp...@sy...>
<sp...@sy...> wrote:

 =20

Well trying to compile with i386/i686/Generic i586 doesn't work either =
(on

0.4 and trunk), with the same problems, so it looks like the i686 =
variant

may be the problem.  I'm going to try again now using i586 as the =
variant

for 0.4 branch and trunk...



Sebastian





   =20



Sebastian,



  Thank you for your comments.  A couple of things:



1) Almost all VIA processors have known problems when running with

"i686" compiled code:



http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html

http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx



  There are other examples all over the place.  On the VIA, stick with =
i586.



2) In general, if you select a specific device under AstLinux target

devices, you really shouldn't just change the processor architecture.

If you want to do this, create a new target device that will select

your intended target CPU.  Those devices are there (and work with 586)

because they are a specific piece of hardware with a known

configuration.



3) "make clean" is broken all over the place.  Myself and the other

devs know this.  I have submitted a patch to both 0.4 and trunk to fix

the few problems that you pointed out but there are certainly other

problems with make clean.



4) These days, almost all development is done in trunk.  0.4 isn't

updated and fixed nearly as often (your mISDN CVS problem, etc).



 =20