ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Ethereal-dev: Re: [Ethereal-dev] Long command-line when building ethereal on Solaris

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date: Sun, 27 May 2001 02:17:11 -0500
On Sat, May 26, 2001 at 09:31:19PM -0700, Guy Harris wrote:
> On Sat, May 26, 2001 at 11:16:14PM -0500, ethereal-dev@xxxxxxxxxxxxxxxxxx wrote:
> > I tried building ethereal 0.8.18 on Solaris with a long --prefix and
> > the compile barfed when building ethereal. With the -L paths and all
> > the package-* files, the command-line limit was exceeded.
> 
> The one-megabyte (unless they've reduced it in SunOS 5.x) limit in the
> kernel was exceeded?  Or was this a limit in, say, the C shell?  (The
> Bourne and Korn shells don't have a wired in limit of the sort that the
> C shell does.)  Or one in "make"?

Ok, turns out to be a limitation of sed. The problem arrises in
the following libtool section:

  # Now compile the dynamic symbol file.
  $show "(cd $output_objdir && $CC -c$no_builtin_flag$pic_flag_for_symtable \"$dlsyms\")"
  $run eval '(cd $output_objdir && $CC -c$no_builtin_flag$pic_flag_for_symtable "$dlsyms")' || exit $?

  # Clean up the generated files.
  $show "$rm $output_objdir/$dlsyms $nlist ${nlist}S ${nlist}T"
  $run $rm "$output_objdir/$dlsyms" "$nlist" "${nlist}S" "${nlist}T"

  # Transform the symbol file into the correct name.
  compile_command=`$echo "X$compile_command" | $Xsed -e "s%@SYMFILE@%$output_objdir/${outputname}S.${objext}%"`
  finalize_command=`$echo "X$finalize_command" | $Xsed -e "s%@SYMFILE@%$output_objdir/${outputname}S.${objext}%"`
  ;;

I get:
  Output line too long.
  Output line too long.

for the assignment to compile_command.

I created a /bin/sh script that made only the assignment to
compile_command and duplicated the failure. Using GNU sed worked fine
with my sample script.

-- 
albert chin (china@xxxxxxxxxxxxxxxxxx)