From: "Arthur Schwarz" <aschwarz1309@att.net>
To: "'Arthur Schwarz'" <aschwarz1309@att.net>, <cygwin@cygwin.com>
Cc: <10walls@gmail.com>
Subject: RE: Question on gcc install
Date: Sat, 21 Jun 2014 16:44:00 -0000 [thread overview]
Message-ID: <6476C8DA293140A1A341363DB12ADC03@2600kPC> (raw)
In-Reply-To: <2E98DFC6544A4D3580A80B89062DFAAF@2600kPC>
On 6/20/2014 22:37, Arthur Schwarz wrote:
>
>> At the present time /bin/gcc.exe, etc., works. /bin/*mingw*.exe
>> either compiles but does not link, or does not compile - which seems
>> to be a
> header
>> issue. gcc -m32 does not work which may be a gcc.gnu issue.
>>
>
> Can you at least be specific about the errors? It is rather
> frustrating reading your emails, being so vague about and all. Are you
> mixing Cygwin and mingw code?
>
> Sorry. I was remiss.
>
> Execution fails on all of the mingw compilers with the same error
> message. All compilations use the same command line options.
>
> > i686-pc-mingw32-g++ -Wall -Wno-reorder -Wno-unused-value -DYYDEBUG=1
> -DDEBUG_IO -c -g -MMD -MP -MF
>
> > slip.exe
>
> /E/home/skidmarks/Projects/SLIP/slip/dist/Debug/mingw-Windows/slip.exe:
> error while loading shared libraries: libstdc++-6.dll: cannot open
> shared object file: No such file or directory
>
> RUN FAILED (exit value 127, total time: 15ms)
>
You are not supposed to run cross compiled executable files. This is not
even a linker error.
I compiled my program with each of the mingw32 compilers.
After each compilation I copied the libstdc++-6.dll into
the directory containing the compiled executable and then
ran the compiled code. After each execution I received the
same error. Are you saying that the mingw32 compiled code
is cross-compiled to a non-intel, non-windows and/or
non-cygwin architecture and that is why the code doesn't
execute? What are you supposed to do with mingw32 compiled
code instead of executing it?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-06-21 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 23:59 Arthur Schwarz
2014-06-20 0:31 ` Larry Hall (Cygwin)
2014-06-20 9:47 ` JonY
2014-06-20 14:37 ` Arthur Schwarz
2014-06-21 1:56 ` JonY
2014-06-21 16:44 ` Arthur Schwarz [this message]
2014-06-22 2:14 ` JonY
2014-06-22 4:25 ` René Berber
2014-06-22 22:08 ` JonY
-- strict thread matches above, loose matches on Subject: below --
2014-06-17 21:33 Arthur Schwarz
2014-06-17 22:21 ` JonY
2014-06-17 16:31 Arthur Schwarz
2014-06-17 18:04 ` Larry Hall (Cygwin)
2014-06-18 7:43 ` Csaba Raduly
2014-06-18 15:11 ` Arthur Schwarz
2014-06-18 22:12 ` JonY
2014-06-16 0:39 Arthur Schwarz
2014-06-16 9:30 ` Csaba Raduly
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=6476C8DA293140A1A341363DB12ADC03@2600kPC \
--to=aschwarz1309@att.net \
--cc=10walls@gmail.com \
--cc=cygwin@cygwin.com \
/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).