public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001707] New: Compile Errors with 64bit RHE6.4
Date: Thu, 29 Nov 2012 22:20:00 -0000	[thread overview]
Message-ID: <bug-1001707-13@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001707

           Summary: Compile Errors with 64bit RHE6.4
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: HostOS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: low
         Component: ConfigTool
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: mjones@linear.com
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Compiling the ConfigTool on 64bit RHE6.4 produces errors. The errors are all
related to 64bit file handles and pointers that can't automatically cast to 32
bits.

To work around the problem, I have forced with a cast like this:

(0xFFFF & (long)myVariable)

I have not fully tested that this will work in all case. Files with this
problem are:

eCosSerial, eCosSocket, eCosTestDownloadFilter, eCosTrace, packagesdlg,
propertywin, and TestResource

There is also a problem compiling wxGTK-2.8.8 that can be solved by using this
configure command:

../configure --with-subdirs --disable-shared --disable-sockets --prefix
/opt/wxGTK-2.8.8

Using --with-subdirs makes gizmo make files so you can compile it. Compiling it
will not copy the resulting lib file, so you have to do that by hand.

There is also a problem compiling ConfigTool related to includes. By editing
the makefile.gnu file in wxwin to the following, it will compile.

EXTRACPPFLAGS=\
  -I$(TCLDIR)/include \
  -I /opt/wxGTK-2.8.8/include/wx-2.8 \
  -I /home/mike/Documents/wxGTK-2.8.8/contrib/include \
  -I
/home/mike/Documents/wxGTK-2.8.8/wx-build/lib/wx/include/gtk2-ansi-release-static-2.8
\
  -I$(INSTALLDIR)/../include \
  -I$(INSTALLDIR)/include \
  -I$(ECOSSRCDIR)/tools/configtool/common/common \
  -I$(ECOSSRCDIR)/tools/Utils/common \
  -I$(ECOSSRCDIR)/tools/ecostest/common \
  -DecUSE_EXPERIMENTAL_CODE=$(USEEXPERIMENTALCODE)
EXTRALDFLAGS=-L$(TCLDIR)/lib -L$(INSTALLDIR)/lib -L/opt/ecos/ecos-3.0/lib -lcdl
-lcyginfra -ltcl

These can probably be handled on the command line or in a better way, but at
least this hack demonstrates the problem. Not the extra include paths, and the
path to the ecos lib in EXTRALDFLAGS.

All other problems were solved with yum. I tried to compile against the latest
wxGTK, and that was such a mess that I gave up and used the 2.8.8 download.

If I encounter any crashes or misbehavior in the ConfigTool I can report back
and add to this bug.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-11-29 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 22:20 bugzilla-daemon [this message]
2012-11-30  8:59 ` [Bug 1001707] " bugzilla-daemon
2012-11-30 15:07 ` bugzilla-daemon
2012-11-29 22:20 [Bug 1001707] New: " bugzilla-daemon

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=bug-1001707-13@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@ecos.sourceware.org \
    /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).