I installed GNU sed. All of the initial "Output line too long" messages
went away, but the build still fails:
(cd doc ; \
make ../ethereal.1 )
./ethereal -G fields | /usr/bin/perl ./dfilter2pod.pl
./ethereal.pod.template >
ethereal.pod
\
--center="The Ethereal Network Analyzer" \
--release=0.9.12 \
ethereal.pod > ../ethereal.1
bash: --center=The Ethereal Network Analyzer: command not found
*** Error code 127
make: Fatal error: Command failed for target `../ethereal.1'
Current working directory /path/to/pkg/ethereal/ethereal-0.9.12/doc
*** Error code 1
make: Fatal error: Command failed for target `ethereal.1'
Current working directory /path/to/pkg/ethereal/ethereal-0.9.12
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'
Current working directory /path/to/pkg/ethereal/ethereal-0.9.12
*** Error code 1
make: Fatal error: Command failed for target `all'
Any ideas?
Matthew Foust
> ----------
> From: Richard Urwin
> Sent: Wednesday, May 14, 2003 7:25 PM
> To: Matthew.Foust; 'ethereal-dev@xxxxxxxxxxxx'
> Subject: Re: [Ethereal-dev] Build error on Solaris 8
>
> On Wednesday 14 May 2003 11:20 pm, Matthew.Foust wrote:
> > I can't figure this out. Trace of make follows. Any ideas?
> ><snip>
> > gcc -DINET6 -DSOLARIS8_INET6 "-D_U_=__attribute__((unused))" -Wall -W -g
> > -O2 -Wno-return-type -DFUNCPROTO=15 -I. -I./wiretap -I/usr/local/include
> > -I/usr/local/include/gtk-1.2 -I/usr/local/include/glib-1.2
> > -I/usr/local/lib/glib/include -I/usr/openwin/include -o .libs/ethereal
> > ...
> > packet-pflog.o
> > packet-pgm.o packe
> > gcc: packe: No such file or directory
> > *** Error code 1
> > make: Fatal error: Command failed for target `ethereal'
> > Current working directory /var/tmp/ethereal-0.9.12
> > *** Error code 1
> > make: Fatal error: Command failed for target `all-recursive'
> > Current working directory /var/tmp/ethereal-0.9.12
> > *** Error code 1
> > make: Fatal error: Command failed for target `all'
>
> http://www.ethereal.com/faq.html#q4.3
>
> Q 4.3: The link fails with a number of "Output line too long." messages
> followed by linker errors.
>
> A: The version of the sed command on your system is incapable of handling
> very
> long lines. On Solaris, for example, /usr/bin/sed has a line length limit
> too
> low to allow libtool to work; /usr/xpg4/bin/sed can handle it, as can GNU
> sed
> if you have it installed.
>
> On Solaris, changing your command search path to search /usr/xpg4/bin
> before
> /usr/bin should make the problem go away; on any platform on which you
> have
> this problem, installing GNU sed and changing your command path to search
> the
> directory in which it is installed before searching the directory with the
>
> version of sed that came with the OS should make the problem go away.
>
> --
> Richard Urwin
>
>