[lwip-users] Re: [lwip] File structure regarding sioslipif and eventually pppi f

[Scott Robinson]

--HcAYCG3uE/tztfnV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Funny. I was thinking of an environment where it would be self-compiling.
;-) The build environment can be the target environment.

Scott.

* Jani Monoses translated into ASCII [Tue, Oct 22, 2002 at 09:11:04AM +0000=
][<address@hidden>]
>=20
> > Personally, I think it's a logical idea. Since lwIP is targetted at emb=
edded
> > systems, I can imagine more than a few environments supportin only 8.3.=
 (or
> > less)
>=20
> Yes but the build environment is the one that should support the long nam=
es not
> the target.
>=20
> But since there are broken tools and broken OSes ;)
> [This message was sent through the lwip discussion list.]

--=20
http://quadhome.com/           - Personal webpage
tranzoa.net                    - Firewall

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s: a--- C++ UL+++ P++ L+++ E- W++ N++ o+ K++ w++=20
O M V(-) PS+ PE Y+ PGP+++ t@ 5 X- R- tv(-) b++++ DI++++ D+=20
G e* h! r* y=20
------END GEEK CODE BLOCK------

--HcAYCG3uE/tztfnV
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iEYEARECAAYFAj21TckACgkQ+1+mlYgeODcrigCeKIa0NerYrz6d84bkVxruJdqa
NocAnjBliOae25b9J19pNMBu/s5Ct6ZN
=zmUO
-----END PGP SIGNATURE-----

--HcAYCG3uE/tztfnV--
[This message was sent through the lwip discussion list.]