On 2019-04-15 16:09, Gerald Pfeifer wrote:
On Mon, 8 Apr 2019, Tijl Coosemans wrote:
This patch make 3 the default for gfortran.
s/make/makes/ but otherwise the patch looks fine.
Thank you, Tijl.
I updated lang/gcc8 (including bumping its PORTREVISION) and will
apply the same to lang/gcc8-dev
On Mon, 8 Apr 2019, Tijl Coosemans wrote:
>> This patch make 3 the default for gfortran.
> s/make/makes/ but otherwise the patch looks fine.
Thank you, Tijl.
I updated lang/gcc8 (including bumping its PORTREVISION) and will
apply the same to lang/gcc8-devel next, and then lang/gcc9-devel
so lang/
usual
>>>> way that he prefers patches submitted upstream and because I thought the
>>>> patch would not be accepted upstream he proposed an alternative solution
>>>> where gcc would always add -rpath on FreeBSD so you didn't have to
>>>> specify
On Mon, 8 Apr 2019 13:16:15 +0800 (WITA) Gerald Pfeifer
wrote:
> This patch make 3 the default for gfortran.
s/make/makes/ but otherwise the patch looks fine.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-
ternative solution
>>> where gcc would always add -rpath on FreeBSD so you didn't have to
>>> specify it on the command line. I responded this wouldn't fix the case
>>> where clang was used as a linker (e.g. to combine fortran and c++ code
>>> in one prog
>> way that he prefers patches submitted upstream and because I thought the
>> patch would not be accepted upstream he proposed an alternative solution
>> where gcc would always add -rpath on FreeBSD so you didn't have to
>> specify it on the command line. I responded
On Sun, Jul 8, 2018 at 10:01 PM Rainer Hurling wrote:
> Am 08.07.2018 um 10:20 schrieb blubee blubeeme:
> > Hello
> >
> > devel/flangclang seems to still be broken, on pkg-install I get errors
> > because flang is installed in {PREFIX}/flang instead of {PREFIX}
> >
> > Is there any particular rea
Am 08.07.2018 um 10:20 schrieb blubee blubeeme:
> Hello
>
> devel/flangclang seems to still be broken, on pkg-install I get errors
> because flang is installed in {PREFIX}/flang instead of {PREFIX}
>
> Is there any particular reason why flang-clang isn't installed in the
> standard directory?
H
Hello
devel/flangclang seems to still be broken, on pkg-install I get errors
because flang is installed in {PREFIX}/flang instead of {PREFIX}
Is there any particular reason why flang-clang isn't installed in the
standard directory?
___
freebsd-ports@fre
On 12/23/2015 09:23, Diane Bruce wrote:
> >No. The core problem is due to our version of libgcc not having quadmath
> >support.
> >
is not that simple. Please read the various threads to understand why.
What does it take to update the base libgcc to the version with quadmath
support?
This i
On 12/24/2015 18:23, Shane Ambler wrote:
Another possibility might be DragonEgg, though it doesn't appear to
have been updated for a while.
http://dragonegg.llvm.org/
I tried DragonEgg, but it is only the optimization/code generation
plugin to gcc, and gcc still writes the final binaries the
On 24/12/2015 01:04, Diane Bruce wrote:
On Wed, Dec 23, 2015 at 04:35:29AM -0800, Yuri wrote:
What is the general solution for this problem? Is there a non-gcc
version of fortran?
No there is currently no clang version of Fortran. 'flang' was a SOC project
to bring in clang s
On Wed, Dec 23, 2015 at 07:38:47AM -0800, Yuri wrote:
> On 12/23/2015 06:34, Diane Bruce wrote:
> > No. The core problem is due to our version of libgcc not having quadmath
> > support.
> >
>
> If the separate port would have been created for gcc with only fortran
>
On 12/23/2015 06:34, Diane Bruce wrote:
No. The core problem is due to our version of libgcc not having quadmath
support.
If the separate port would have been created for gcc with only fortran
in it, and it would have been compiled with clang, this would have
solved this problem.
Yuri
On Wed, Dec 23, 2015 at 04:35:29AM -0800, Yuri wrote:
> I found that ports with USES=fortran can't mix with anything in C++
> compiled with the base clang++, because USES=fortran forces the current
> gcc that links with its /usr/local/lib/libgcc_s.so.1
It's a well known bug
I found that ports with USES=fortran can't mix with anything in C++
compiled with the base clang++, because USES=fortran forces the current
gcc that links with its /usr/local/lib/libgcc_s.so.1
Getting this particular error from the python process, because one
python module has USES=fo
On 02/11/14 23:42, Benediktus Anindito wrote:
> Greetings,
>
> I'm now try to build a cluster with OpenMPI and Open GridScheduler
> (formerly Sun Grid Engine) as the job scheduler. based on OpenMPI FAQ,
> there is an option to build OpenMPI with SGE support. Since FORTRAN
>
Greetings,
I'm now try to build a cluster with OpenMPI and Open GridScheduler
(formerly Sun Grid Engine) as the job scheduler. based on OpenMPI FAQ,
there is an option to build OpenMPI with SGE support. Since FORTRAN
support is enabled by default and it depends on gcc46 and I do not use
FO
In message <201307171608.r6hg8eo2022...@mech-cluster241.men.bris.ac.uk>,
Anton
Shterenlikht writes:
> (copy to ports@ in case some users of devel/fpp are not on fortran@)
>
> devel/fpp is a Fortran pre-processor.
> It is unmaintained.
> I think fortran@ list is the mo
(copy to ports@ in case some users of devel/fpp are not on fortran@)
devel/fpp is a Fortran pre-processor.
It is unmaintained.
I think fortran@ list is the most logical maintainer.
Any objections?
Anton
P.S. I just updated devel/fpp to
conform to the latest ports framework.
The port is old
On 4/14/11, O. Hartmann wrote:
> On 04/14/11 08:32, b. f. wrote:
>> On 4/14/11, O. Hartmann wrote:
>>> On 04/13/11 20:59, b. f. wrote:
> We had hope for clang, but clang lacks in many aspects we desperately
> need - like OpenMP support.
That may change, if:
http://wiki.llvm.org/Polyhedral_opti
Intel Sandy-Bridge CPUs
and gcc46 is supoorting new facilities like that.
I think that the gcc maintainer will probably switch the default
Fortran compiler to gcc46 after gcc46 has been tested a bit longer,
and some of the remaining bugs fixed. You could of course switch the
default on your own
e CPUs
> and gcc46 is supoorting new facilities like that.
I think that the gcc maintainer will probably switch the default
Fortran compiler to gcc46 after gcc46 has been tested a bit longer,
and some of the remaining bugs fixed. You could of course switch the
default on your own machines. AVX s
6: version GLIBCXX_3.4.11
required by /usr/local/isis/3.2.1/bin/qview not found
Building the software without the ports-framework but with explicitely
set GCC/G++/GFORTRAN results in a working binary.
My question: is USE_GCC setting C++ and Fortran compilers as desired as
well as the C compiler?
You
3.4.11
> required by /usr/local/isis/3.2.1/bin/qview not found
>
> Building the software without the ports-framework but with explicitely
> set GCC/G++/GFORTRAN results in a working binary.
>
> My question: is USE_GCC setting C++ and Fortran compilers as desired as
> well as th
/usr/local/isis/3.2.1/bin/qview not found
Building the software without the ports-framework but with explicitely
set GCC/G++/GFORTRAN results in a working binary.
My question: is USE_GCC setting C++ and Fortran compilers as desired as
well as the C compiler?
Please set me CC when respondin
On Sun, Jan 25, 2009 at 8:27 PM, Garrett Cooper wrote:
> On Jan 25, 2009, at 5:18, Robert Huff wrote:
>
>> bf writes:
>>
>>> Just a note to those of you who helped to integrate the Gnome,
>>> X11, and Fortran updates in Ports: thank you very much for the
&g
On Jan 25, 2009, at 5:18, Robert Huff wrote:
bf writes:
Just a note to those of you who helped to integrate the Gnome,
X11, and Fortran updates in Ports: thank you very much for the
work that you have put in, and for your efforts to find and solve
any remaining problems.
Hear, hear.
I
bf writes:
> Just a note to those of you who helped to integrate the Gnome,
> X11, and Fortran updates in Ports: thank you very much for the
> work that you have put in, and for your efforts to find and solve
> any remaining problems.
Just a note to those of you who helped to integrate the Gnome, X11, and
Fortran updates in Ports: thank you very much for the work that you have
put in, and for your efforts to find and solve any remaining problems. I'm
looking forward to using the new software, and I'm sure that many
2007/10/27, Stephen Montgomery-Smith <[EMAIL PROTECTED]>:
>
> Harald Servat wrote:
> > Hello,
> >
> > I'm a maintainer of a port which needs a fortran compiler. Due to the
> > inclusion of GCC 4.2 as the default compiler for FreeBSD 7.0 I'm facing
Harald Servat wrote:
Hello,
I'm a maintainer of a port which needs a fortran compiler. Due to the
inclusion of GCC 4.2 as the default compiler for FreeBSD 7.0 I'm facing a
problem with the port. My FreeBSD 6.2 box can compile fine my port using
f77, however the build farms do n
Le Sam 27 oct 07 à 16:34:40 +0200, Harald Servat <[EMAIL PROTECTED]>
écrivait :
> Hello,
Hello,
> I'm a maintainer of a port which needs a fortran compiler. Due to the
> inclusion of GCC 4.2 as the default compiler for FreeBSD 7.0 I'm facing a
> problem with the
Hello,
I'm a maintainer of a port which needs a fortran compiler. Due to the
inclusion of GCC 4.2 as the default compiler for FreeBSD 7.0 I'm facing a
problem with the port. My FreeBSD 6.2 box can compile fine my port using
f77, however the build farms do not compile successfull
Harald Servat wrote:
Hello to everybody,
recently I received an automated mail about a port I'm maintaining. Such
mail includes a full report (which is good in order to review the problems
;) ) of the port build on amd64/freebsd7.
The program needs fortran compiler, and looking a
Hello to everybody,
recently I received an automated mail about a port I'm maintaining. Such
mail includes a full report (which is good in order to review the problems
;) ) of the port build on amd64/freebsd7.
The program needs fortran compiler, and looking at the report, I see that
fo
Hello to everybody,
recently I received an automated mail about a port I'm maintaining. Such
mail includes a full report (which is good in order to review the problems
;) ) of the port build on amd64/freebsd7.
The program needs fortran compiler, and looking at the report, I see that
fo
What is now the proper way to make a port use Fortran? Remember that
CURRENT now doesn't seem to have fortran installed by default, and FC is
no longer set in /usr/share/mk/sys.mk, and I am looking for something
that works in CURRENT and S
On 4 Jun, Steve Kargl wrote:
> The correct spelling of the name of the language is Fortran.
It's spelled FORTRAN if you're old enough ;-)
> The reason is simple. If you upgrade from 6-stable to 7-current
> and you do not clean out the f77 command (aka g77) then you
> ma
Hi,
On 4 Jun 2007, at 16:14, Steve Kargl wrote:
On Mon, Jun 04, 2007 at 09:43:03AM +0100, Bob Bishop wrote:
[...]A better fix would be to make ports dependent on an appropriate
compiler port, but that's a lot of work and some users will prefer
ifc anyway.
The work has already been done for m
scovered that the port uses ${FC} to find the FORTRAN compiler. I
> >>then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
> >>fort77). I don't this is appropriate since f77 has been removed from
> >>-CURRENT.
> >>
> >>I do
On Mon, Jun 04, 2007 at 01:48:01AM -0700, Garrett Cooper wrote:
> Steve Kargl wrote:
> >On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
> >
> >>I was taking a look at why math/lapack fails to build on -CURRENT and
> >>discovered that the port uses $
Hi,
On 4 Jun 2007, at 02:09, Steve Kargl wrote:
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk
Steve Kargl wrote:
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
fort77
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
> I was taking a look at why math/lapack fails to build on -CURRENT and
> discovered that the port uses ${FC} to find the FORTRAN compiler. I
> then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
> fort77). I d
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
fort77). I don't this is appropriate since f77 has been removed from
-CURRENT.
I
* currently all ports using fortran are unstable. please wait until I announce
about it
* kris will tell me how they are broken ;)
current status of migration
wait ... wait for commit approval
source ... f90/f77 sources exist
link ... only exist link against f90/f77 complied libraries
Please tell me which port uses Fortran. or link against fortran compiled
programs.
I'll fix them.
-- NAKATA, Maho ([EMAIL PROTECTED])
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubs
* currently all ports using fortran are unstable. please wait until I announce
about it
current status of migration
wait ... wait for commit approval
source ... f90/f77 sources exist
link ... only exist link against f90/f77 complied libraries
gfortran ... used compiler is gfortran42
f77
[EMAIL PROTECTED] a écrit :
> News:
>
> Kris approved that migration to gfortran
>
>>Unless the changes are too extensive, please proceed.
>
> so I'll proceed.
Hi all,
Could be this thread related to some problem I have encountered building
Scipy on my freebsd boxes (6.2) ?
On one of my free
News:
Kris approved that migration to gfortran
> Unless the changes are too extensive, please proceed.
so I'll proceed.
* currently all ports using fortran are unstable. please wait until I announce
about it
current status of migration
wait ... wait for commit approval
source ...
51 matches
Mail list logo
