* [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
2009-09-08 14:32 [Bug fortran/41309] New: 4.4.1 build of fortran fails on T5140 ian dot james at bnymellon dot com
@ 2009-09-08 14:39 ` ian dot james at bnymellon dot com
2009-09-08 14:55 ` kargl at gcc dot gnu dot org
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: ian dot james at bnymellon dot com @ 2009-09-08 14:39 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from ian dot james at bnymellon dot com 2009-09-08 14:39 -------
Created an attachment (id=18542)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18542&action=view)
file generated during build failure
The same result arises during make when configure is run without further
options. The following SMC packages are installed on the system:
SMCgmp SMClgcc346 SMCliconv SMClintl SMCmake SMCmpfr SMCnetsnmp
SMCsed SMCsudo SMCtar SUNWmgts SUNWtsmc
followed by s source build and install of mpfr-2.4.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
2009-09-08 14:32 [Bug fortran/41309] New: 4.4.1 build of fortran fails on T5140 ian dot james at bnymellon dot com
2009-09-08 14:39 ` [Bug fortran/41309] " ian dot james at bnymellon dot com
@ 2009-09-08 14:55 ` kargl at gcc dot gnu dot org
2009-09-08 14:56 ` kargl at gcc dot gnu dot org
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: kargl at gcc dot gnu dot org @ 2009-09-08 14:55 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from kargl at gcc dot gnu dot org 2009-09-08 14:55 -------
(In reply to comment #1)
> Created an attachment (id=18542)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18542&action=view) [edit]
> file generated during build failure
>
> The same result arises during make when configure is run without further
> options. The following SMC packages are installed on the system:
> SMCgmp SMClgcc346 SMCliconv SMClintl SMCmake SMCmpfr SMCnetsnmp
> SMCsed SMCsudo SMCtar SUNWmgts SUNWtsmc
> followed by s source build and install of mpfr-2.4.1
>
My first and only guess is that SMCmpfr and mpfr-2.4.1 are incompatible.
For example, configure is finding the library for mpfr-2.4.1 but the
build is finding the SMCmpfr header file. Try using the --with-mpfr
configure option or remove one of the mpfr packages.
PS: I note that you don't list a GMP package, but one must be present
if you built mpfr-2.4.1. You may need/want to use the --with-gmp
option.
--
kargl at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|4.4.1 build of fortran fails|4.4.1 build of fortran fails
|on T5140 |on T5140
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
2009-09-08 14:32 [Bug fortran/41309] New: 4.4.1 build of fortran fails on T5140 ian dot james at bnymellon dot com
2009-09-08 14:39 ` [Bug fortran/41309] " ian dot james at bnymellon dot com
2009-09-08 14:55 ` kargl at gcc dot gnu dot org
@ 2009-09-08 14:56 ` kargl at gcc dot gnu dot org
2009-09-08 17:34 ` mikael at gcc dot gnu dot org
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: kargl at gcc dot gnu dot org @ 2009-09-08 14:56 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from kargl at gcc dot gnu dot org 2009-09-08 14:56 -------
(In reply to comment #2)
> (In reply to comment #1)
> > Created an attachment (id=18542)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18542&action=view) [edit]
> > file generated during build failure
> >
> > The same result arises during make when configure is run without further
> > options. The following SMC packages are installed on the system:
> > SMCgmp SMClgcc346 SMCliconv SMClintl SMCmake SMCmpfr SMCnetsnmp
> > SMCsed SMCsudo SMCtar SUNWmgts SUNWtsmc
> > followed by s source build and install of mpfr-2.4.1
> >
>
> PS: I note that you don't list a GMP package, but one must be present
> if you built mpfr-2.4.1. You may need/want to use the --with-gmp
> option.
Whoops, well you list SMCgmp, sorry I missed that one.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
2009-09-08 14:32 [Bug fortran/41309] New: 4.4.1 build of fortran fails on T5140 ian dot james at bnymellon dot com
` (2 preceding siblings ...)
2009-09-08 14:56 ` kargl at gcc dot gnu dot org
@ 2009-09-08 17:34 ` mikael at gcc dot gnu dot org
2009-09-20 21:08 ` pinskia at gcc dot gnu dot org
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: mikael at gcc dot gnu dot org @ 2009-09-08 17:34 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from mikael at gcc dot gnu dot org 2009-09-08 17:33 -------
I suggest you clear your build directory and retry from scratch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
2009-09-08 14:32 [Bug fortran/41309] New: 4.4.1 build of fortran fails on T5140 ian dot james at bnymellon dot com
` (3 preceding siblings ...)
2009-09-08 17:34 ` mikael at gcc dot gnu dot org
@ 2009-09-20 21:08 ` pinskia at gcc dot gnu dot org
2009-09-21 8:00 ` ian dot james at bnymellon dot com
2009-09-21 10:04 ` burnus at gcc dot gnu dot org
6 siblings, 0 replies; 8+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2009-09-20 21:08 UTC (permalink / raw)
To: gcc-bugs
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
2009-09-08 14:32 [Bug fortran/41309] New: 4.4.1 build of fortran fails on T5140 ian dot james at bnymellon dot com
` (4 preceding siblings ...)
2009-09-20 21:08 ` pinskia at gcc dot gnu dot org
@ 2009-09-21 8:00 ` ian dot james at bnymellon dot com
2009-09-21 10:04 ` burnus at gcc dot gnu dot org
6 siblings, 0 replies; 8+ messages in thread
From: ian dot james at bnymellon dot com @ 2009-09-21 8:00 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from ian dot james at bnymellon dot com 2009-09-21 07:59 -------
I separated the directories of Solaris packaged GNU (/usr/sfw), open built GNU
(/usr/local) and locally built GNU components (usr/gnu) components, putting the
built ones earlier in LD_LIBRARY_PATH and PATH. I then rebuilt from source
using gcc-3.4.6 the packages mpfr, gmp. Then rebuilt gcc-4.4.1 and it has
worked. Then rebuilt mpfr and gmp using gcc-4.4.1 which has all worked.
Please mark the bug as user error.
Sorry for the false alert.
--
ian dot james at bnymellon dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian dot james at bnymellon
| |dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug fortran/41309] 4.4.1 build of fortran fails on T5140
2009-09-08 14:32 [Bug fortran/41309] New: 4.4.1 build of fortran fails on T5140 ian dot james at bnymellon dot com
` (5 preceding siblings ...)
2009-09-21 8:00 ` ian dot james at bnymellon dot com
@ 2009-09-21 10:04 ` burnus at gcc dot gnu dot org
6 siblings, 0 replies; 8+ messages in thread
From: burnus at gcc dot gnu dot org @ 2009-09-21 10:04 UTC (permalink / raw)
To: gcc-bugs
------- Comment #6 from burnus at gcc dot gnu dot org 2009-09-21 10:04 -------
(In reply to comment #5)
> Please mark the bug as user error.
> Sorry for the false alert.
Great that it now works for you. (Closed as INVALID.)
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41309
^ permalink raw reply [flat|nested] 8+ messages in thread