(I posted this message at the GNU Fortran Google group two days ago,
but no one has replied yet.)

I just installed a new version of gfortran but am getting warning and
error messages I do not understand, as shown below. What is the
problem? Thanks for your help.

H:\fortran>gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=c:/programs/gfortran/bin/../libexec/gcc/i586-pc-
mingw32/4.6.0/lto-wrapper.exe
Target: i586-pc-mingw32
Configured with: ../gcc-trunk/configure --prefix=/mingw --enable-
languages=c,fortran --with-gmp=/home/brad/gfortran/dependencies --
disable-werror --enable-threads --disable-nls --build=i586-pc-mingw32
--enable-libgomp --disable-shared --disable-win32-registry --with-
dwarf2 --disable-sjlj-exceptions --enable-lto
Thread model: win32
gcc version 4.6.0 20101201 (experimental) [trunk revision 167359]
(GCC)


H:\fortran>type xhello.f90
program xhello
implicit none
print*,"hello world!"
end program xhello


H:\fortran>gfortran xhello.f90
Warning: .drectve `-aligncomm:__gfortrani_compile_options,5'
unrecognized
Warning: .drectve `-aligncomm:__gfortrani_options,5' unrecognized
Warning: .drectve `-aligncomm:__gfortrani_unit_lock,2 ' unrecognized
Warning: .drectve `-aligncomm:__gfortrani_unit_root,2 ' unrecognized
Warning: .drectve `-aligncomm:__gfortrani_max_offset,3 ' unrecognized
Warning: .drectve `-aligncomm:__gfortrani_next_available_newunit,2'
unrecognized
Warning: .drectve `-aligncomm:___DTOR_LIST__,2 ' unrecognized
Warning: .drectve `-aligncomm:___CTOR_LIST__,2' unrecognized


In this case at least the executable a.exe is created and can be run.
In another case I get error messages when I compile:


gfortran -c xfoo.f90
C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s: Assembler messages:
C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s:4271: Error: junk at end of
line, first unrecognized character is `,'
C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s:4272: Error: junk at end of
line, first unrecognized character is `,'

> I just installed a new version of gfortran but am getting warning and
> error messages I do not understand, as shown below. What is the
> problem? Thanks for your help.

For Windows installations of gfortran, packaging choices and coherence
between compiler, linker, and mingw versions are crucial. So, where do
you downloaded the package from, and have you asked support to them? If
not, doesn't it seem like the most logical course of action?

-- 
FX

On 12/9/2010 7:39 AM, Beliavsky wrote:
> (I posted this message at the GNU Fortran Google group two days ago,
> but no one has replied yet.)
>
> I just installed a new version of gfortran but am getting warning and
> error messages I do not understand, as shown below. What is the
> problem? Thanks for your help.
>
> H:\fortran>gfortran -v
> Using built-in specs.
> COLLECT_GCC=gfortran
> COLLECT_LTO_WRAPPER=c:/programs/gfortran/bin/../libexec/gcc/i586-pc-
> mingw32/4.6.0/lto-wrapper.exe
> Target: i586-pc-mingw32
> Configured with: ../gcc-trunk/configure --prefix=/mingw --enable-
> languages=c,fortran --with-gmp=/home/brad/gfortran/dependencies --
> disable-werror --enable-threads --disable-nls --build=i586-pc-mingw32
> --enable-libgomp --disable-shared --disable-win32-registry --with-
> dwarf2 --disable-sjlj-exceptions --enable-lto
> Thread model: win32
> gcc version 4.6.0 20101201 (experimental) [trunk revision 167359]
> (GCC)
>
>
> H:\fortran>type xhello.f90
> program xhello
> implicit none
> print*,"hello world!"
> end program xhello
>
>
> H:\fortran>gfortran xhello.f90
> Warning: .drectve `-aligncomm:__gfortrani_compile_options,5'
> unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_options,5' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_unit_lock,2 ' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_unit_root,2 ' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_max_offset,3 ' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_next_available_newunit,2'
> unrecognized
> Warning: .drectve `-aligncomm:___DTOR_LIST__,2 ' unrecognized
> Warning: .drectve `-aligncomm:___CTOR_LIST__,2' unrecognized
>
>
> In this case at least the executable a.exe is created and can be run.
> In another case I get error messages when I compile:
>
>
> gfortran -c xfoo.f90
> C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s: Assembler messages:
> C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s:4271: Error: junk at end of
> line, first unrecognized character is `,'
> C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s:4272: Error: junk at end of
> line, first unrecognized character is `,'
>
>

Weird

I am the person that created that build of gfortran and I do not get 
those warnings when I compile your test program.  I have NO idea what 
would cause those messages.  Perhaps this is due to competing versions 
of the MinGW libraries with stuff you already have on your machine.  Can 
you do a clean install in a different directory, make sure your PATH 
gets updated to this new directory and then try again with the compile.

"Beliavsky" <beliavsky@aol.com> wrote in message 
news:62995c32-513d-4109-a7d3-b4d9a2c2d435@k11g2000vbf.googlegroups.com...
> (I posted this message at the GNU Fortran Google group two days ago,
> but no one has replied yet.)
>
> I just installed a new version of gfortran but am getting warning and
> error messages I do not understand, as shown below. What is the
> problem? Thanks for your help.

Looks like the version linked to from the gcc Wiki at 
http://gcc.gnu.org/wiki/GFortranBinaries
under MinGW build
-Unofficial build of current development (4.6) source. Download the latest 
installer (dated 2010-12-01).

>
> H:\fortran>gfortran -v
> Using built-in specs.
> COLLECT_GCC=gfortran
> COLLECT_LTO_WRAPPER=c:/programs/gfortran/bin/../libexec/gcc/i586-pc-
> mingw32/4.6.0/lto-wrapper.exe
> Target: i586-pc-mingw32
> Configured with: ../gcc-trunk/configure --prefix=/mingw --enable-
> languages=c,fortran --with-gmp=/home/brad/gfortran/dependencies --
> disable-werror --enable-threads --disable-nls --build=i586-pc-mingw32
> --enable-libgomp --disable-shared --disable-win32-registry --with-
> dwarf2 --disable-sjlj-exceptions --enable-lto
> Thread model: win32
> gcc version 4.6.0 20101201 (experimental) [trunk revision 167359]
> (GCC)

Same output. I'm on 32 bit Vista.

> H:\fortran>type xhello.f90
> program xhello
> implicit none
> print*,"hello world!"
> end program xhello

> H:\fortran>gfortran xhello.f90
> Warning: .drectve `-aligncomm:__gfortrani_compile_options,5'
> unrecognized
[snip]

I installed to c:\gfortran. Instead of the above I am seeing the same error 
message that appeared on the first release of the previous version dated 
2010-10-27, before its bug was fixed:

C:\Users\epc\temp>gfortran xhello.f90
gfortran: error: CreateProcess: No such file or directory

2. The binaries from www.equation.com identifiy themselves as coming from 
that web site.
3. I don't work with the MinGW distributions that have a package based 
installer similar to that of Cygwin.

---- Elliot

On 12/09/2010 05:51 PM, e p chandler wrote:
> "Beliavsky" <beliavsky@aol.com> wrote in message
>> I just installed a new version of gfortran but am getting warning and
>> error messages I do not understand, as shown below. What is the
>> problem? Thanks for your help.
>
> Looks like the version linked to from the gcc Wiki at
> http://gcc.gnu.org/wiki/GFortranBinaries

Well, the issue is simple: The linker (ld.exe) is too old. That means 
either that the wrong linker is picked up from the path or that the 
package contains an too old linker. Cf. 
http://gcc.gnu.org/ml/fortran/2010-05/msg00299.html  Regarding the 
assembler error: My bet would be that if the linker (ld.exe) is too old, 
also the the assembler (as.exe) is.

As the issue has been confirmed, I think there is a packaging error. I 
have notified Brad, who is so kind to offer the MinGW builds, which are 
linked at the gfortran wiki.

Tobias

On Dec 9, 12:15=A0pm, Tobias Burnus <bur...@net-b.de> wrote:
> On 12/09/2010 05:51 PM, e p chandler wrote:
>
> > "Beliavsky" <beliav...@aol.com> wrote in message
> >> I just installed a new version of gfortran but am getting warning and
> >> error messages I do not understand, as shown below. What is the
> >> problem? Thanks for your help.
>
> > Looks like the version linked to from the gcc Wiki at
> >http://gcc.gnu.org/wiki/GFortranBinaries
>
> Well, the issue is simple: The linker (ld.exe) is too old. That means
> either that the wrong linker is picked up from the path or that the
> package contains an too old linker. Cf.http://gcc.gnu.org/ml/fortran/2010=
-05/msg00299.html=A0Regarding the
> assembler error: My bet would be that if the linker (ld.exe) is too old,
> also the the assembler (as.exe) is.
>
> As the issue has been confirmed, I think there is a packaging error. I
> have notified Brad, who is so kind to offer the MinGW builds, which are
> linked at the gfortran wiki.
>
> Tobias

Thanks for looking into the problem. The binary from Equation.com at
ftp://ftp.equation.com/gcc/gcc-4.6-20101204-32.exe works for me.

"Tobias Burnus" <burnus@net-b.de> wrote in message 
news:4D010ECC.3050906@net-b.de...

> On 12/09/2010 05:51 PM, e p chandler wrote:

>> "Beliavsky" <beliavsky@aol.com> wrote in message

>>> I just installed a new version of gfortran but am getting warning and
>>> error messages I do not understand, as shown below. What is the
>>> problem? Thanks for your help.

>> Looks like the version linked to from the gcc Wiki at
>> http://gcc.gnu.org/wiki/GFortranBinaries

> Well, the issue is simple: The linker (ld.exe) is too old. That means 
> either that the wrong linker is picked up from the path or that the 
> package contains an too old linker. Cf. 
> http://gcc.gnu.org/ml/fortran/2010-05/msg00299.html  Regarding the 
> assembler error: My bet would be that if the linker (ld.exe) is too old, 
> also the the assembler (as.exe) is.

> As the issue has been confirmed, I think there is a packaging error. I 
> have notified Brad, who is so kind to offer the MinGW builds, which are 
> linked at the gfortran wiki.

OK, here's what I get with that build:

C:\gfortran32>cd \gfortran\clf\hello

C:\gfortran\clf\hello>type hellob.f90
program xhello
implicit none
print*,"hello world!"
end program xhello

C:\gfortran\clf\hello>gfortran hellob.f90 -ohellob
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccgt2TFJ.s: Assembler messages:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccgt2TFJ.s:12: Error: invalid instruction 
suf
fix for `push'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ccgt2TFJ.s:45: Error: invalid instruction 
suf
fix for `push'

C:\gfortran\clf\hello>gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=c:/gfortran32/bin/../libexec/gcc/i586-pc-mingw32/4.6.0/lto-w
rapper.exe
Target: i586-pc-mingw32
Configured with: 
.../gcc-trunk/configure --prefix=/mingw --enable-languages=c,for
tran --with-gmp=/home/brad/gfortran/dependencies --disable-werror --enable-threa
ds --disable-nls --build=i586-pc-mingw32 --enable-libgomp --disable-shared --dis
able-win32-registry --with-dwarf2 --disable-sjlj-exceptions --enable-lto
Thread model: win32
gcc version 4.6.0 20101201 (experimental) [trunk revision 167359] (GCC)

C:\gfortran\clf\hello>ld -v
GNU ld (GNU Binutils) 2.20.51.20101030

C:\gfortran\clf\hello>as -v
GNU assembler version 2.20.51 (x86_64-w64-mingw32) using BFD version (GNU 
Binuti
ls) 2.20.51.20101030

There seems to be a problem that perhaps a 64-bit as.exe is being
invoked whereas a 32-bit target is being built.  Here are the steps
I followed in an attempt to create a clean install of gfortran in
the presence of many other versions:

Go to gfortran wiki:
http://gcc.gnu.org/wiki/GFortran
Under Quick links, click on Binaries
Under Windows, MinGW build bullet, download latest installer.
Create new directory (I called it C:\gfortran32, if you install
over on old installation, always delete all your old gfortran
directories from that installation while being careful not to
disturb any of your directories that contain your Fortran code!)
Open up Windows Explorer (Windows+E hotkey does this)
Navigate to C:\gfortran32
Double-click on gfortran-windows.exe
Click Run, then Agree
On installation folder, click Browse
Navigate to C:\gfortran32
Click OK
In destination folder test box, delete trailing '\gfortran'
to read 'C:\gfortran32'
Click Install
After Set status says completed, click close
In Windows Explorer, navigate to C:\WINDOWS\system32
Using right mouse button, drag cmd.exe from C:\WINDOWS\system32
to C:\gfortran32 directory and drop it there
Select Create Shortcuts Here in the bos that pops up.
Right-click on the Shortcut to cmd.exe in the C:\gfortran32
directory, select properties, and under the General tab,
change the name to 'Build environment for 32-bit gfortran'
Under the Shorcut tab, change:
Target: %SystemRoot%\system32\cmd.exe /K ""C:\gfortran32\shortcut.bat""
Start in: leave blank
Shortcut key: None
Run: Normal window
Comment: Build environment for 32-bit gfortran
Under the Edit tab, select QuickEdit and Insert modes.
Click OK
Click on C:\gfortran32 directory in Windows Explorer
From menu bar, select File->New->Text document
Rename New Text Document.txt to shortcut.bat
Right-click shortcut.bat, select Edit, then paste in:

@echo off
Title Build environment for 32-bit gfortran

While still editing, go to
Start->Control Panel->System.  Select Advanced tab and the
Environmental variables button
Under user variables, select PATH variable, Edit, and Copy the
C:\gfortran32\libexec\gcc\i586-pc-mingw32\4.6.0;C:\gfortran32\bin
part that the installer placed there.  Go back to shortcut.bat,
and at the bottom, type

set path=

then paste in the path you got from Control Panel, then

';%path%'

Now for me this shortcut.bat reads:

@echo off
Title Build environment for 32-bit gfortran
set 
path=C:\gfortran32\libexec\gcc\i586-pc-mingw32\4.6.0;C:\gfortran32\bin;%path%

Make sure you hit <ENTER> at the end so shortcut.bat doesn't end in
an incomplete line.
From the menu bar, select File->Exit.\
Click Yes to save changes.
Back in control panel, delete that stuff that the installer
added to your PATH environmental variable, and if that leaves
your PATH environmental variable blank, delete it as well.
Click OK twice to save changes to your environmental variables.

Now you can start an appropriate environment for gfortran by
double-clicking the shortcut you created under Windows Explorer!

Now, it seems to me that the installer didn't give me any copies
of as.exe or ld.exe, so I tried copying the as.exe and ld.exe from
the 32-bit version of gfortran that you get from www.equation.com
to my C:\gfortran32\bin directory and it all worked!

C:\gfortran\clf\hello>type hellob.f90
program xhello
implicit none
print*,"hello world!"
end program xhello

C:\gfortran\clf\hello>gfortran hellob.f90 -ohellob

C:\gfortran\clf\hello>hellob
 hello world!

So the as.exe I was picking up previously was from the 64-bit
version of gfortran, which was the only one I suffer to leave
on my environmental variables.  Everybody gets different
error messages because the as.exe and ld.exe that gfortran
eventually finds are from different packages.  To test new
builds requires cleaning up all directories and environmental
variables because if that isn't done, any omitted files may get
filled in without your knowledge.

-- 
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end

On 12/09/2010 09:15 AM, Tobias Burnus wrote:
> On 12/09/2010 05:51 PM, e p chandler wrote:
>> "Beliavsky" <beliavsky@aol.com> wrote in message
>>> I just installed a new version of gfortran but am getting warning and
>>> error messages I do not understand, as shown below. What is the
>>> problem? Thanks for your help.
>>
>> Looks like the version linked to from the gcc Wiki at
>> http://gcc.gnu.org/wiki/GFortranBinaries
> 
> Well, the issue is simple: The linker (ld.exe) is too old. That means
> either that the wrong linker is picked up from the path or that the
> package contains an too old linker. Cf.
> http://gcc.gnu.org/ml/fortran/2010-05/msg00299.html  Regarding the
> assembler error: My bet would be that if the linker (ld.exe) is too old,
> also the the assembler (as.exe) is.
> 
> As the issue has been confirmed, I think there is a packaging error. I
> have notified Brad, who is so kind to offer the MinGW builds, which are
> linked at the gfortran wiki.
> 
> Tobias

Yes, I see the problem.  I modified the included MinGW libraries, but in
the process, deleted all of the included binaries!  Whatever old
binaries for things like ld would be used, and not the newer versions
required with the current 4.6 gfortran.   I will fix that and post a new
build soon.

On Dec 9, 12:15=A0pm, Tobias Burnus <bur...@net-b.de> wrote:
> On 12/09/2010 05:51 PM, e p chandler wrote:
>
> > "Beliavsky" <beliav...@aol.com> wrote in message
> >> I just installed a new version of gfortran but am getting warning and
> >> error messages I do not understand, as shown below. What is the
> >> problem? Thanks for your help.
>
> > Looks like the version linked to from the gcc Wiki at
> >http://gcc.gnu.org/wiki/GFortranBinaries
>
> Well, the issue is simple: The linker (ld.exe) is too old. That means
> either that the wrong linker is picked up from the path or that the
> package contains an too old linker. Cf.http://gcc.gnu.org/ml/fortran/2010=
-05/msg00299.html=A0Regarding the
> assembler error: My bet would be that if the linker (ld.exe) is too old,
> also the the assembler (as.exe) is.
>
> As the issue has been confirmed, I think there is a packaging error. I
> have notified Brad, who is so kind to offer the MinGW builds, which are
> linked at the gfortran wiki.
>
> Tobias

Thank you for pointing out the error and Brad for creating these
builds.

It looks like as.exe and ld.exe ARE the problem:

I installed g95 to c:\g95 AFTER installing gfortran to c:\gfortran.
Now programs compile and run.

The as and ld are so old, they are not there at all!

 Directory of C:\gfortran

12/09/2010  04:27 PM            34,845 uninstaller.exe
               1 File(s)         34,845 bytes

 Directory of C:\gfortran\bin

12/02/2010  07:41 PM           311,310 cpp.exe
12/02/2010  07:41 PM           310,286 gcc.exe
12/02/2010  07:41 PM            55,310 gcov.exe
12/02/2010  07:41 PM           312,334 gfortran.exe
               4 File(s)        989,240 bytes

 Directory of C:\gfortran\libexec\gcc\i586-pc-mingw32\4.6.0

12/02/2010  07:41 PM        11,659,790 cc1.exe
12/02/2010  07:41 PM           145,422 collect2.exe
12/02/2010  07:41 PM        12,112,910 f951.exe
12/02/2010  07:41 PM            53,774 lto-wrapper.exe
12/02/2010  07:41 PM        10,882,574 lto1.exe
               5 File(s)     34,854,470 bytes

 Directory of C:\gfortran\libexec\gcc\i586-pc-mingw32\4.6.0\install-
tools

12/02/2010  07:41 PM           112,142 fixincl.exe
               1 File(s)        112,142 bytes

Now I know what to look for if I see this error appear again.

---- Elliot

On Dec 9, 4:25=A0pm, baf <b...@nowhere.com> wrote:
> On 12/09/2010 09:15 AM, Tobias Burnus wrote:
>
> > On 12/09/2010 05:51 PM, e p chandler wrote:
> >> "Beliavsky" <beliav...@aol.com> wrote in message
> >>> I just installed a new version of gfortran but am getting warning and
> >>> error messages I do not understand, as shown below. What is the
> >>> problem? Thanks for your help.
>
> >> Looks like the version linked to from the gcc Wiki at
> >>http://gcc.gnu.org/wiki/GFortranBinaries
>
> > Well, the issue is simple: The linker (ld.exe) is too old. That means
> > either that the wrong linker is picked up from the path or that the
> > package contains an too old linker. Cf.
> >http://gcc.gnu.org/ml/fortran/2010-05/msg00299.html=A0Regarding the
> > assembler error: My bet would be that if the linker (ld.exe) is too old=
,
> > also the the assembler (as.exe) is.
>
> > As the issue has been confirmed, I think there is a packaging error. I
> > have notified Brad, who is so kind to offer the MinGW builds, which are
> > linked at the gfortran wiki.
>
> > Tobias
>
> Yes, I see the problem. =A0I modified the included MinGW libraries, but i=
n
> the process, deleted all of the included binaries! =A0Whatever old
> binaries for things like ld would be used, and not the newer versions
> required with the current 4.6 gfortran. =A0 I will fix that and post a ne=
w
> build soon.

Thanks. See my most recent post before this.

On 12/9/2010 7:39 AM, Beliavsky wrote:
> (I posted this message at the GNU Fortran Google group two days ago,
> but no one has replied yet.)
>
> I just installed a new version of gfortran but am getting warning and
> error messages I do not understand, as shown below. What is the
> problem? Thanks for your help.
>
> H:\fortran>gfortran -v
> Using built-in specs.
> COLLECT_GCC=gfortran
> COLLECT_LTO_WRAPPER=c:/programs/gfortran/bin/../libexec/gcc/i586-pc-
> mingw32/4.6.0/lto-wrapper.exe
> Target: i586-pc-mingw32
> Configured with: ../gcc-trunk/configure --prefix=/mingw --enable-
> languages=c,fortran --with-gmp=/home/brad/gfortran/dependencies --
> disable-werror --enable-threads --disable-nls --build=i586-pc-mingw32
> --enable-libgomp --disable-shared --disable-win32-registry --with-
> dwarf2 --disable-sjlj-exceptions --enable-lto
> Thread model: win32
> gcc version 4.6.0 20101201 (experimental) [trunk revision 167359]
> (GCC)
>
>
> H:\fortran>type xhello.f90
> program xhello
> implicit none
> print*,"hello world!"
> end program xhello
>
>
> H:\fortran>gfortran xhello.f90
> Warning: .drectve `-aligncomm:__gfortrani_compile_options,5'
> unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_options,5' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_unit_lock,2 ' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_unit_root,2 ' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_max_offset,3 ' unrecognized
> Warning: .drectve `-aligncomm:__gfortrani_next_available_newunit,2'
> unrecognized
> Warning: .drectve `-aligncomm:___DTOR_LIST__,2 ' unrecognized
> Warning: .drectve `-aligncomm:___CTOR_LIST__,2' unrecognized
>
>
> In this case at least the executable a.exe is created and can be run.
> In another case I get error messages when I compile:
>
>
> gfortran -c xfoo.f90
> C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s: Assembler messages:
> C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s:4271: Error: junk at end of
> line, first unrecognized character is `,'
> C:\DOCUME~1\vrao\LOCALS~1\Temp\ccuszuAc.s:4272: Error: junk at end of
> line, first unrecognized character is `,'
>
>
A new install file for gfortran on MinGW32 systems has been created that 
will hopefully solve this problem.  Use the link from the wiki to 
download.  The version number of the gfortran files are the same as the 
previous build, as all I did was to include the required MinGW binary 
files that are needed for a minimally useful programming environment.

Please report your success or failure with this new version in a post 
here.  Thanks.

"baf" <baf@nowhere.net> wrote in message 
news:8mdrjoF53sU1@mid.individual.net...

> A new install file for gfortran on MinGW32 systems has been created that 
> will hopefully solve this problem.  Use the link from the wiki to 
> download.  The version number of the gfortran files are the same as the 
> previous build, as all I did was to include the required MinGW binary 
> files that are needed for a minimally useful programming environment.

> Please report your success or failure with this new version in a post 
> here.  Thanks.

Cleaned up my directory structure and reinstalled from your link.
Cleaned up PATH variable after installation and started from my
gfortran32 command prompt.  Result:

C:\gfortran\clf\hello>type hellob.f90
program xhello
implicit none
print*,"hello world!"
end program xhello

C:\gfortran\clf\hello>gfortran hellob.f90 -ohellob

C:\gfortran\clf\hello>hellob
 hello world!

Now if only MinGW w64 would get a working build up...

-- 
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end

On 12/9/2010 10:51 PM, James Van Buskirk wrote:
> "baf"<baf@nowhere.net>  wrote in message
> news:8mdrjoF53sU1@mid.individual.net...
>
>> A new install file for gfortran on MinGW32 systems has been created that
>> will hopefully solve this problem.  Use the link from the wiki to
>> download.  The version number of the gfortran files are the same as the
>> previous build, as all I did was to include the required MinGW binary
>> files that are needed for a minimally useful programming environment.
>
>> Please report your success or failure with this new version in a post
>> here.  Thanks.
>
> Cleaned up my directory structure and reinstalled from your link.
> Cleaned up PATH variable after installation and started from my
> gfortran32 command prompt.  Result:
>
> C:\gfortran\clf\hello>type hellob.f90
> program xhello
> implicit none
> print*,"hello world!"
> end program xhello
>
> C:\gfortran\clf\hello>gfortran hellob.f90 -ohellob
>
> C:\gfortran\clf\hello>hellob
>   hello world!
>
> Now if only MinGW w64 would get a working build up...
>

Great!  Thanks for that report.  Next up is getting a build with 
libquadmath working without any fuss by the user.  It appears that the 
patches necessary for a successful build should be available pretty 
soon.  Once the patches are ready, I will try to create a new build and 
will post a note on clf.

"baf" <baf@nowhere.net> wrote in message 
news:8mdrjoF53sU1@mid.individual.net...
> On 12/9/2010 7:39 AM, Beliavsky wrote:
>> (I posted this message at the GNU Fortran Google group two days ago,
>> but no one has replied yet.)
>>
>> I just installed a new version of gfortran but am getting warning and
>> error messages I do not understand, as shown below. What is the
>> problem? Thanks for your help.
[snip]
>> Thread model: win32
>> gcc version 4.6.0 20101201 (experimental) [trunk revision 167359]
>> (GCC)
[snip]
> A new install file for gfortran on MinGW32 systems has been created that 
> will hopefully solve this problem.  Use the link from the wiki to 
> download.  The version number of the gfortran files are the same as the 
> previous build, as all I did was to include the required MinGW binary 
> files that are needed for a minimally useful programming environment.
>
> Please report your success or failure with this new version in a post 
> here.  Thanks.
>

Success. Thanks.

C:\Users\epc\temp>gfortran -v
....
Thread model: win32
gcc version 4.6.0 20101201 (experimental) [trunk revision 167359] (GCC)

C:\Users\epc\temp>gfortran x.f90 -o xf

C:\Users\epc\temp>gcc x.c -o xc
x.c:1:19: fatal error: stdio.h: No such file or directory
compilation terminated.

C:\Users\epc\temp>set cpath=c:\gfortran\include

C:\Users\epc\temp>gcc x.c -o xc

C:\Users\epc\temp>xf
 hello, world

C:\Users\epc\temp>xc
hello, world

Compared to the 2010-06-20 version, these files are not in \bin:

elfedit.exe
strings.exe
strip.exe
unix2dos.exe
windmc.exe
windres.exe

Needing to set cpath to compile a C program when installed to \gfortran is 
not new behavior.

-- Elliot

On 10/12/2010 8:02 a.m., James Van Buskirk wrote:
....
> There seems to be a problem that perhaps a 64-bit as.exe is being
> invoked whereas a 32-bit target is being built.  Here are the steps
> I followed in an attempt to create a clean install of gfortran in
> the presence of many other versions:
>
> Go to gfortran wiki:
  < a few lines snipped >

Well that seems simple enough.  ;-)