Syslinux - Jun 2008 - Problems with newlib port

Hello,

 

I have noticed that Peter wanted to port newlib to syslinux project some
time ago. It seems that the porting was not finished. Peter mentioned
(http://syslinux.zytor.com/archives/2004-February/003168.html) that sucj
job would require a lot of efforts. At the same time newlib is usually
regarded as a "highly portable C-library". I am wondering what are the
major difficulties/problems/issues in porting newlib to com32?

 

Thanks.

 

Best,

Alex

Loginov Alexander wrote:
> Hello,
> 
> I have noticed that Peter wanted to port newlib to syslinux project some
> time ago. It seems that the porting was not finished. Peter mentioned
> (http://syslinux.zytor.com/archives/2004-February/003168.html) that sucj
> job would require a lot of efforts. At the same time newlib is usually
> regarded as a "highly portable C-library". I am wondering what
are the
> major difficulties/problems/issues in porting newlib to com32?
> 
Well, I ended up porting klibc instead.  Not because klibc is inherently 
better for the job, but simply because I know it better -- I wrote it.

Most of the issues will be the same -- in particular providing a more 
Unix-like device model -- so probably a lot of the code I've written for 
the klibc port can be reused.

	-hpa

Peter,

Is there are any disadvantages/shortcoming (in terms of functionality)
of klibc comparing to newlib? I am asking because I need a decent
C-library and syslinux for the embedded target. If those libraries are
more or less the same, I would prefer to simply use klibc.

Best,
Alex



-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On
Behalf Of H. Peter Anvin
Sent: Wednesday, June 04, 2008 12:49 PM
To: For discussion of SYSLINUX and tftp-hpa
Subject: Re: [syslinux] Problems with newlib port

Loginov Alexander wrote:
> Hello,
> 
> I have noticed that Peter wanted to port newlib to syslinux project
some
> time ago. It seems that the porting was not finished. Peter mentioned
> (http://syslinux.zytor.com/archives/2004-February/003168.html) that
sucj
> job would require a lot of efforts. At the same time newlib is usually
> regarded as a "highly portable C-library". I am wondering what
are the
> major difficulties/problems/issues in porting newlib to com32?
> 
Well, I ended up porting klibc instead.  Not because klibc is inherently

better for the job, but simply because I know it better -- I wrote it.

Most of the issues will be the same -- in particular providing a more 
Unix-like device model -- so probably a lot of the code I've written for

the klibc port can be reused.

	-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.