linker error during compilation

Blake Matheny
Tue, 4 Feb 2003 10:17:18 -0500

It would be helpful if libgcrypt had a script for collecting this type of
information. In any case, here is the relevant information:
OS             : Linux
OS RELEASE     : 2.4.18-4_72smp
HARDWARE       : i686
gcc version    : 2.96
Gnu gmake      : 3.79.1
autoconf       : 2.57
automake       : 1.6.3
ld             :

The version of ld I'm using is older. If there are restraints on the versions
of pieces of software that people need, perhaps adding some checks to
scripts/ is in order? Thanks.


Whatchu talkin' 'bout, Willis?
> On Sun, Feb 02, 2003 at 03:30:29PM -0500, Blake Matheny wrote:
> > According to the documentation that I have for my linker, it says that the
> > syntax for the VERSION command is:
> > 
> > VERSION { commands }
> > 
> > where VERSION should not be blank.
> Your report is very incomplete, and thus we don't know how to fix this
> problem.  More important than a patch is always an accurate description of
> the problem, and that includes the operating system you are using, and the
> version of the linker (and if it is the system linker or GNU ld).
> Without a VERSION, it is an anonymous version map.  This is supported by
> binutils 2.13 or later, probably also by earlier versions.  It should also
> be supported by Solaris.
> Please let us know which system and version you are using.
> Thanks,
> Marcus
> -- 
> `Rhubarb is no Egyptian god.' GNU
> Marcus Brinkmann              The Hurd

Blake Matheny           "... one of the main causes of the fall of the      Roman Empire was that, lacking zero, they had   no way to indicate successful termination of  their C programs." --Robert Firth