From: "Spen" <spen@spen-soft.co.uk>
To: <wilfried.fauvel@laposte.net>, "'insight'" <insight@sourceware.org>
Subject: RE: FW: Can't build Insight with Cygwin
Date: Fri, 23 Dec 2005 16:24:00 -0000 [thread overview]
Message-ID: <20051223162400.Fn-htgRsibiuEIu1GMUgrDUPcKBKLVg69FWYZGku704@z> (raw)
In-Reply-To: <IRYDUJ$B2C0C533974F3ED2202F24737A38F95E@laposte.net>
Just to let you know that it does build under cygwin. I only make one patch
to enable building under the follow config.
Cygwin: 1.5.18
GCC 3.4.4
The patch can be found here:
http://sourceware.org/ml/insight/2005-q3/msg00021.html
I did run into one build problem after updating other cygwin pakages,
reinstalling gcc fixed the problems, could be with a try.
Regards
Spen
-----Original Message-----
From: insight-owner@sourceware.org [mailto:insight-owner@sourceware.org] On
Behalf Of wilfried.fauvel@laposte.net
Sent: 23 December 2005 13:38
To: insight
Subject: Re:FW: Can't build Insight with Cygwin
Hi,
I think you can use the patch command
(http://www.gnu.org/software/patch/patch.html) with the .diff file, I have
made it manually : you only have to open the three files listed ("RCS
file:") in the .diff file, and replace the - lines by the + lines at the
corresponding patterns.
I have tested to build on another config (with the same cygwin version :
1.5.18(0.132/4/2), and the same sources), and it seems to crash still ...
Good luck.
> Hi
>
> Thanks, Wilfred! This at least confirms my view that there did not
> seem to be any regular way this source could build. If I read it
> right, Dave Korn has confirmed that the Win32Dll.c code relies on an
> idiosyncrasy of an earlier version of gcc. Wilfred, can you post a
> patch? I have read Dave Korn's fix but as I have always studiously
> avoided assembler I just don't understand what to do to implement it!
>
> BTW: Keith, I have used the latest cygwin download which I think is
> gcc 3.4... (see Dave Korn's post). I am interested in Insight under
> Windows because I have used MSVC in the past (great debugger!) but
> want to migrate to gnu for cross-platform reasons. There's a lot of
> IDEs available for gcc but debugging support is generally poor. Hence the
interest in Insight.
> Keith, I guess the cygwin compiler on your Win2K box is an old version...
>
> Finally, I tried building with mingw 3.4.4 and the offending section
> in tcl/win seems to build OK!! But mingw breaks on the ./bfd
sub-directory.
> Output below. Any ideas on this one? This looks like something has
> coughed in the make file - again, I've studiously avoided using make...
>
>
> Peter
>
> ######################################################################
> ######
> #############################
> >
> > make[2]: Entering directory `/c/insight-6.4/bfd'
> > Making info in doc
> > make[3]: Entering directory `/c/insight-6.4/bfd/doc'
> > restore=: && backupdir=".am$$" && \
> > am__cwd=`pwd` && cd ../.././bfd/doc && \ rm -rf $backupdir && mkdir
> > $backupdir && \ for f in ../.././bfd/doc/bfd.info
> > ../.././bfd/doc/bfd.info-[0-9] ../.././bfd/doc/bfd.info-[0-9][0-9]
> > ../.././bfd/doc/bfd.i[0-9] ../.././bfd/doc/bfd.i[0-9][0-9]; do \ if
> > test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ done; \
> > cd "$am__cwd"; \ if makeinfo --split-size=5000000
> > --split-size=5000000 -I ../.././bfd/doc \ -o
> > ../.././bfd/doc/bfd.info ../.././bfd/doc/bfd.texinfo; \ then \ rc=0;
> > \ cd ../.././bfd/doc; \ else \ rc=$?; \ cd ../.././bfd/doc && \
> > $restore $backupdir/* `echo "./../.././bfd/doc/bfd.info" | sed
> > 's|[^/]*$||'`; \ fi; \ rm -rf $backupdir; exit $rc section
> > mapping'.ss reference to nonexistent node `mmo a New Hash Table
> > Type'.ference to nonexistent node `Deriving
> > makeinfo: Removing output file `../.././bfd/doc/bfd.info' due to
> > errors; use --force to preserve.
> > make[3]: *** [../.././bfd/doc/bfd.info] Error 2
> > make[3]: Leaving directory `/c/insight-6.4/bfd/doc'
> > make[2]: *** [info-recursive] Error 1
> > make[2]: Leaving directory `/c/insight-6.4/bfd'
> > make[1]: *** [all-bfd] Error 2
> > make[1]: Leaving directory `/c/insight-6.4'
> > make: *** [all] Error 2
> >
>
Accédez au courrier électronique de La Poste : www.laposte.net ; Jusqu'au 25
décembre, participez au grand jeu du Calendrier de l'Avent et
gagnez tous les jours de nombreux lots, + de 300 cadeaux en jeu !
next prev parent reply other threads:[~2005-12-23 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 16:17 wilfried.fauvel
2005-12-23 16:21 ` FW: " Peter Rockett
2005-12-23 16:24 ` Spen [this message]
[not found] <200512231852.jBNIq9cM007525@mx1.redhat.com>
2005-12-23 23:19 ` Keith Seitz
2005-12-24 0:55 ` Peter Rockett
2005-12-24 18:00 ` Spen
[not found] <cmu-lmtpd-20522-1135363936-1@impala>
2005-12-23 22:58 ` Peter Rockett
[not found] <cmu-lmtpd-21756-1135354673-4@impala>
2005-12-23 18:52 ` Peter Rockett
2005-12-23 21:41 ` Peter Rockett
2005-12-24 14:00 ` Keith Seitz
2005-12-23 21:47 ` Spen
[not found] <200512231618.jBNGI4BD085002@mail.cso.atmel.com>
2005-12-23 18:10 ` Eric Weddington
-- strict thread matches above, loose matches on Subject: below --
2005-12-23 16:09 Peter Rockett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051223162400.Fn-htgRsibiuEIu1GMUgrDUPcKBKLVg69FWYZGku704@z \
--to=spen@spen-soft.co.uk \
--cc=insight@sourceware.org \
--cc=wilfried.fauvel@laposte.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).