As is so often the case, articulating the problem led to a
resolution; it looks like linking sys/byteorder.h to machine/endian.h
is an effective workaround.
Still working on olvwm, though; it complains, now, about conflicting
definitions of sys_errlist[] and wchar_t ... aiyah.
Hope this helps someone else, down the line.
-- richard
richard childers / kg6hac wrote:
I'm trying to compile olvwm(1), v4.4, for FreeBSD 4.6 on an i386
box.
It's looking for sys/byteorder.h and not finding it.
My research indicates that linking sys/byteorder.h to
netinet/in.h doesn't work. (It was a workaround suggested on one
of the URLs I read.)
I understand the issues being addressed here - they are
fundamental, big-endian versus little-endian architectures.
However, I do not normally have the time and leisure to explore
such interesting topics (unemployment, properly treated, can be
the equivalent of what, in more scholastic environments, are
referred to as 'going on sabbatical' :-); I am trying to make
effective use of this precious period of free study.
For what it's worth, xview and xview-ports are both installed
without problems; I have olwm(1), I just want olvwm(1), it's my
preferred 'vwm, very useful for keeping work segmented onto
different desktops according to system or window role
(development servers on *this* desktop, production servers on
*that* desktop, network analysis tools on *these* three desktops,
email over here, and HTTP clients on these four desktops at the
bottom, for instance - stretch as needed).
I'm going to use my buddy find(1) to search for files containing
strings referencing 'endian' and ending in '.h' (or '.c', to see
what's being included, if my first efforts fail), and I haven't
given up on figuring this out myself, but thought I'd inquire of
others whom might face these issues on a daily, rather than
decade-periodic, basis, in the hopes that I'd save myself a few
hours (or days), and maybe learn something, too.
Thanks in advance,
-- richard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
