Why does the linker fail with a number of “Output line too long.” messages followed by linker errors when I try to build Wireshark?
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.
Related Questions
- Why does my build fail with an Unresolved assembly reference error when I try to document a Compact Framework application?
- When I try to build Wireshark on Windows, why does the build fail because of conflicts between winsock.h and winsock2.h?
- When I try to build Wireshark on Solaris, why does the link fail complaining that plugin_list is undefined?
