This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: compiling DDD


On Thu, 4 Dec 2003, Richard Campbell wrote:
> Arnaud Desitter wrote:
> >Richard Campbell wrote:
> >> Now, I guess, to try and walk back all of the automatic steps to figure
> >> out why ddd ended up linking against that libimp-cygXm-2.a file.
> >>
> >Credit or blame libtool for that.
> >
What version of libtool is ddd-3.3.8 using?
Does re-libtoolizing fix it?

When these two questions are answered, it is probably time to move this to
cygwin@cygwin.com or libtool@gnu.org where the Cygwin libtool experts are.

> Specifically, the following two settings:
>
> # Whether or not to build static libraries.
> build_old_libs=yes
>
> # Create a temporary old-style archive to link instead of a shared archive.
> old_archive_from_expsyms_cmds="\$DLLTOOL --as=\$AS --dllname \$soname --def
> \$output_objdir/\$soname-def --output-lib \$output_objdir/\$newlib"
>
> If commented out, everything works cleanly.
>
> Now, the bizarre part of the generated libtool is the following:
>
> # Whether or not to build shared libraries.
> build_libtool_libs=yes
>
> # Whether or not to build static libraries.
> build_old_libs=yes
>
> Why would you have both "shared" and "static" turned on?
>
To have the option of either, obviously.  Some packages default this way
as a courtesy.

Static libs are useful when profiling, distributing binaries without
worrying about associated libs, etc.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]