Greetings, Ulli Horlacher!
> On Thu 2018-08-30 (15:55), Ulli Horlacher wrote:
>> On Thu 2018-08-30 (11:43), Andrey Repin wrote:
>>
>> > > This script would run setup-x86_64.exe which asks a lot of questions
>> > > (mirror site, proxy, installation directory, etc) in the first run.
>> > > This
Ulli Horlacher writes:
> This script would run setup-x86_64.exe which asks a lot of questions
> (mirror site, proxy, installation directory, etc) in the first run.
> This will overcharge my users!
Well, after all the hints you've already got, how about you actually
look at what setup.exe does
On Thu 2018-08-30 (15:55), Ulli Horlacher wrote:
> On Thu 2018-08-30 (11:43), Andrey Repin wrote:
>
> > > This script would run setup-x86_64.exe which asks a lot of questions
> > > (mirror site, proxy, installation directory, etc) in the first run.
> > > This will overcharge my users!
> >
> >
On Thu 2018-08-30 (11:43), Andrey Repin wrote:
> > This script would run setup-x86_64.exe which asks a lot of questions
> > (mirror site, proxy, installation directory, etc) in the first run.
> > This will overcharge my users!
>
> setup --help
There is no command line option for "Choose A
Greetings, Ulli Horlacher!
> On Sat 2018-07-14 (16:31), Achim Gratz wrote:
>> > I have several 100 users, none of them is able to install cygwin and
>> > the packages they need the official way, they are way to *CENSORED* for
>> > this job :-}
>>
>> If they can follow your current instructions,
Am 30.08.2018 um 08:40 schrieb Ulli Horlacher:
On Sat 2018-07-14 (16:31), Achim Gratz wrote:
I have several 100 users, none of them is able to install cygwin and
the packages they need the official way, they are way to *CENSORED* for
this job :-}
If they can follow your current instructions,
On Sat 2018-07-14 (16:31), Achim Gratz wrote:
> > I have several 100 users, none of them is able to install cygwin and
> > the packages they need the official way, they are way to *CENSORED* for
> > this job :-}
>
> If they can follow your current instructions, they can surely start some
>
Greetings, Ulli Horlacher!
> On Sat 2018-07-14 (16:31), Achim Gratz wrote:
>> >> You have to install Cygwin, not "transfer".
>> >
>> > I have several 100 users, none of them is able to install cygwin and
>> > the packages they need the official way, they are way to *CENSORED* for
>> > this job
On Sat 2018-07-14 (16:31), Achim Gratz wrote:
> >> You have to install Cygwin, not "transfer".
> >
> > I have several 100 users, none of them is able to install cygwin and
> > the packages they need the official way, they are way to *CENSORED* for
> > this job :-}
>
> If they can follow your
Ulli Horlacher writes:
>> You have to install Cygwin, not "transfer".
>
> I have several 100 users, none of them is able to install cygwin and
> the packages they need the official way, they are way to *CENSORED* for
> this job :-}
If they can follow your current instructions, they can surely
On Mon 2018-07-09 (05:18), Andrey Repin wrote:
> > SIGH. I was hoping a 32 bit cygwin with 32 bit self compiled programs will
> > run on 64 bit Windows, too. But I was wrong.
> > Meanwhile I have 4 VMs:
> > Windows 32 bit with 32 bit cygwin
> > Windows 32 bit with 32 bit cygwin for compiling
> >
On 2018-07-08 20:18, Andrey Repin wrote:
>> On Fri 2018-06-08 (19:41), Andrey Repin wrote:
> 2.) Do a Cygwin build and copy cygwin1.dll
I already have a /usr/bin/cygwin1.dll on the Windows 8 target system.
>>> It's a wrong architecture. You need a 32-bit one for your 32-bit program.
Greetings, Ulli Horlacher!
> On Fri 2018-06-08 (19:41), Andrey Repin wrote:
>> >> 2.) Do a Cygwin build and copy cygwin1.dll
>>
>> > I already have a /usr/bin/cygwin1.dll on the Windows 8 target system.
>>
>> It's a wrong architecture. You need a 32-bit one for your 32-bit program.
>>
>> > Do
On Fri 2018-06-08 (19:41), Andrey Repin wrote:
> >> 2.) Do a Cygwin build and copy cygwin1.dll
>
> > I already have a /usr/bin/cygwin1.dll on the Windows 8 target system.
>
> It's a wrong architecture. You need a 32-bit one for your 32-bit program.
>
> > Do I have to replace it?
>
> No.
>
Ulli Horlacher writes:
> I have compiled the application with gcc from cygwin.
You've compiled with the native compiler on a 32bit Cygwin, producing a
32bit Cygwin executable.
> It runs without problems on Windows 7 32 bit but on Windows 8 64 bit it
> does not output ANYTHING. No (error)
On Fri, Jun 8, 2018 at 3:45 PM, Ulli Horlacher wrote:
>
> There is no way to run a 32 bit cygwin binary on a 64 bit Windows system?
There is, but you need a 32-bit Cygwin for that (which can be
installed on 64-bit windows).
Csaba
--
You can get very substantial performance improvements
by not
On 2018-06-08 07:42, Ulli Horlacher wrote:
> On Wed 2018-06-06 (16:12), cyg Simple wrote:
>>> On Windows 7 32 bit I have compiled some binaries by myself.
>> Help us help you by giving us how you compiled these and with what set
>> of tools.
> jed comes with a BIG makefile.
> When I start it, it
Greetings, Ulli Horlacher!
>> 2.) Do a Cygwin build and copy cygwin1.dll
> I already have a /usr/bin/cygwin1.dll on the Windows 8 target system.
It's a wrong architecture. You need a 32-bit one for your 32-bit program.
> Do I have to replace it?
No.
Just build a 64-bit version of your
Greetings, Ulli Horlacher!
>> -^^
>> THIS isn't 32bit Cygwin.
>>
>> You cannot run a 32bit Cygwin application under 64bit Cygwin.
> This WAS my initial question!
> There is no way to run a 32 bit cygwin binary ob a 64 bit Windows
Keep the responses on list please.
On 6/8/2018 9:45 AM, Ulli Horlacher wrote:
> On Fri 2018-06-08 (09:37), cyg Simple wrote:
>> On 6/8/2018 9:30 AM, Ulli Horlacher wrote:
>>
>> [-- TOFU entsorgt --]
>>
>> -^^
>>
On Fri 2018-06-08 (09:34), cyg Simple wrote:
> On 6/8/2018 9:19 AM, Ulli Horlacher wrote:
>
> >
> > I have compiled the application with gcc from cygwin.
> > It runs without problems on Windows 7 32 bit but on Windows 8 64 bit it
> > does not output ANYTHING. No (error) message, nothing.
> >
>
Dear Ulli,
> There is no way to run a 32 bit cygwin binary ob a 64 bit Windows system?
You can easily install 32 bit Cygwin on 64 bit Windows (as I mentioned before).
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99
On Fri 2018-06-08 (13:43), Soegtrop, Michael wrote:
> are you sure you want a cygwin build? I thought you are doing a MinGW
> build (since Cygwin1.ddl was missing from ldd).
What is MinGW?
> 1.) Do a MinGW cross compile in case you don't need any Cygwin
> infrastructure (bash, ...) or fully
On Fri 2018-06-08 (09:37), cyg Simple wrote:
> On 6/8/2018 9:30 AM, Ulli Horlacher wrote:
>
> [-- TOFU entsorgt --]
>
> -^^
> THIS isn't 32bit Cygwin.
>
> You cannot run a 32bit Cygwin application under 64bit
Dear Ulli,
are you sure you want a cygwin build? I thought you are doing a MinGW build
(since Cygwin1.ddl was missing from ldd).
There are 3 possible ways:
1.) Do a MinGW cross compile in case you don't need any Cygwin infrastructure
(bash, ...) or fully posix compliant C environment
2.) Do
On Fri 2018-06-08 (15:30), Ulli Horlacher wrote:
> Transfered to Windows 8 32 bit:
Sorry, typo! It is Windows 8 64 bit!
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de
Allmandring 30a
On Wed 2018-06-06 (16:12), cyg Simple wrote:
> > On Windows 7 32 bit I have compiled some binaries by myself.
>
> Help us help you by giving us how you compiled these and with what set
> of tools.
jed comes with a BIG makefile.
When I start it, it outputs:
/sw/src/jed-0.99.20-116: make
cd src;
On 6/8/2018 9:30 AM, Ulli Horlacher wrote:
> On Thu 2018-06-07 (01:04), Andrey Repin wrote:
>
>> Then I'm at a loss to explain the behavior. If he ran ldd on the same system
>> he had built it (and where it is running properly), then there's
>> environmental
>> conditions involved.
>
> Windows
On 6/8/2018 9:19 AM, Ulli Horlacher wrote:
>
> I have compiled the application with gcc from cygwin.
> It runs without problems on Windows 7 32 bit but on Windows 8 64 bit it
> does not output ANYTHING. No (error) message, nothing.
>
You CANNOT move a 32bit Cygwin application to a 64bit Cygwin
On Thu 2018-06-07 (01:04), Andrey Repin wrote:
> Then I'm at a loss to explain the behavior. If he ran ldd on the same system
> he had built it (and where it is running properly), then there's environmental
> conditions involved.
Windows 7 32 bit build system:
Dear Uli,
in case you are not comfortable using gdb, Sysinternals ProcMon (can be
downloaded for free from Microsoft) will give you information about what
happens during process startup.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg,
On Wed 2018-06-06 (20:49), Andrey Repin wrote:
> Greetings, Soegtrop, Michael!
>
> > Dear Ulli,
>
> > for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are
> > doing MinGW builds)
>
> It did not include cygwin1.dll because he ran ldd on a system, where that
> library was
Greetings, cyg Simple!
>>> for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are
>>> doing MinGW builds)
>>
>> It did not include cygwin1.dll because he ran ldd on a system, where that
>> library was missing. May be you are right and he compiled it using
>> cross-compiler.
>>
On 6/6/2018 1:49 PM, Andrey Repin wrote:
> Greetings, Soegtrop, Michael!
>
>> Dear Ulli,
>
>> for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are
>> doing MinGW builds)
>
> It did not include cygwin1.dll because he ran ldd on a system, where that
> library was missing. May
On 6/6/2018 7:50 AM, Ulli Horlacher wrote:
>
> On Windows 7 32 bit I have compiled some binaries by myself.
Help us help you by giving us how you compiled these and with what set
of tools.
> I can run them there but not on a Windows 8 64 bit: no (error) message,
> nothing happens.
>
In what
Greetings, Soegtrop, Michael!
> Dear Ulli,
> for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are
> doing MinGW builds)
It did not include cygwin1.dll because he ran ldd on a system, where that
library was missing. May be you are right and he compiled it using
Greetings, Ulli Horlacher!
> On Wed 2018-06-06 (19:02), Andrey Repin wrote:
>> > On Windows 7 32 bit I have compiled some binaries by myself.
>> > I can run them there but not on a Windows 8 64 bit: no (error) message,
>> > nothing happens.
>>
>>
>> > Do I have to install some 32 bit libs?
>>
On Wed 2018-06-06 (19:02), Andrey Repin wrote:
> > On Windows 7 32 bit I have compiled some binaries by myself.
> > I can run them there but not on a Windows 8 64 bit: no (error) message,
> > nothing happens.
>
>
> > Do I have to install some 32 bit libs?
>
> Of course. Did you read the
Dear Ulli,
sorry, I just saw that you did compile on a 32 bit Windows, so you had a 32 bit
Cygwin - strange. What I can tell is that compiling a 32 bit app on a 32 bit
Cygwin on a 64 bit Windows works and that such an app runs fine on 32 bit and
64 bit Windows. I test this regularly. I can't
Dear Ulli,
for MinGW (your ldd dump didn't include Cygwin dlls, so I assume you are doing
MinGW builds) I would recommend to compile 32 bit binaries using a 32 bit
Cygwin (which can be installed on 64 bit machines).
The reason is that the Windows file system has some hacks. Some DLLs are
Greetings, Ulli Horlacher!
> On Windows 7 32 bit I have compiled some binaries by myself.
> I can run them there but not on a Windows 8 64 bit: no (error) message,
> nothing happens.
> admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a
> CYGWIN_NT-6.3 WIN-7T5P92ALEEB
On 2018-06-06 13:50, Ulli Horlacher was heard to say:
On Windows 7 32 bit I have compiled some binaries by myself.
I can run them there but not on a Windows 8 64 bit: no (error) message,
nothing happens.
admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a
CYGWIN_NT-6.3
On Windows 7 32 bit I have compiled some binaries by myself.
I can run them there but not on a Windows 8 64 bit: no (error) message,
nothing happens.
admin@WIN-7T5P92ALEEB:/sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a
CYGWIN_NT-6.3 WIN-7T5P92ALEEB 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64
43 matches
Mail list logo
