John Peterson writes:
> On Tue, Jan 26, 2021 at 10:11 AM Pedro Rodrigues wrote:
>
>> Yes I let PETSc to build MPI with default options Just --download MPI.
>> Maybe that is the problem. I will try to build it as you suggest
>>
>
> OK, well if using static libs wasn't intentional, I'd suggest you
On Tue, Jan 26, 2021 at 10:11 AM Pedro Rodrigues wrote:
> Yes I let PETSc to build MPI with default options Just --download MPI.
> Maybe that is the problem. I will try to build it as you suggest
>
OK, well if using static libs wasn't intentional, I'd suggest you start
over and reconfigure/rebui
On Tue, Jan 26, 2021 at 4:50 AM Pedro Rodrigues wrote:
> Hello
>
> I tried to build under Linux but got this error message:
>
>
> /usr/bin/ld:
>
> /home/ubuntu/Dev/petsc/arch-linux2-c-debug/lib/libmpi.a(lib_libmpi_la-initthread.o):
> relocation R_X86_64_TPOFF32 against hidden symbol `MPIR_Per_thr
Hello
I tried to build under Linux but got this error message:
/usr/bin/ld:
/home/ubuntu/Dev/petsc/arch-linux2-c-debug/lib/libmpi.a(lib_libmpi_la-initthread.o):
relocation R_X86_64_TPOFF32 against hidden symbol `MPIR_Per_thread' can not
be used when making a shared object
/usr/bin/ld:
/home/ubun
On Thu, Nov 21, 2013 at 9:25 AM, Subramanya Sadasiva
wrote:
> Hi All,
> i get the following error while building libmesh with the macports version of
> gcc-4.8 on OSX 10.9 but only in the optimized version. The debug version
> compiles without any trouble. Is tehre a work around for this?
>
> n
On Thu, 21 Nov 2013, John Peterson wrote:
> On Thu, Nov 21, 2013 at 9:25 AM, Subramanya Sadasiva
> wrote:
>> /usr/include/string.h:145:1: error: 'errno_t' does not name a type
>> errno_t memset_s(void *, rsize_t, int, rsize_t)
>> __OSX_AVAILABLE_STARTING(__MAC_10_9, __IPHONE_7_0)
>
> This look
Hi All,
i get the following error while building libmesh with the macports version of
gcc-4.8 on OSX 10.9 but only in the optimized version. The debug version
compiles without any trouble. Is tehre a work around for this?
n file included from /opt/local/include/gcc48/c++/cstring:42:0,
Hi John, Your suggestion worked. Thanks, Subramanya
> Date: Thu, 21 Nov 2013 11:22:16 -0600
> From: royst...@ices.utexas.edu
> To: jwpeter...@gmail.com
> CC: pota...@outlook.com; libmesh-users@lists.sourceforge.net
> Subject: Re: [Libmesh-users] Build Error with gcc-4.8
>
&
Hi,
Reinstalling mpi did the trick...not sure what got messed up in the upgrade
to 12.04 Ubuntu.
Thanks again for the help.
Cheers,
Cory
On Wed, Sep 19, 2012 at 10:08 PM, Cory Ahrens wrote:
> Hi,
>
> Ok. Thanks for the help. I'll try our suggestions.
>
> Cheers,
>
> Cory
>
>
>
> On Wed, Sep
Hi,
Ok. Thanks for the help. I'll try our suggestions.
Cheers,
Cory
On Wed, Sep 19, 2012 at 10:05 PM, Roy Stogner wrote:
>
> On Wed, 19 Sep 2012, Cory Ahrens wrote:
>
> Both c++ and g++ worked fine on hello world, but mpicc gave the error
>>
>
> Well, at least it's not a libMesh problem! :-
On Wed, 19 Sep 2012, Cory Ahrens wrote:
> Both c++ and g++ worked fine on hello world, but mpicc gave the error
Well, at least it's not a libMesh problem! :-)
Try tracking down and reinstalling whichever package is providing your
mpicc? That's mpich-bin or openmpi-bin on Ubuntu, I presume.
--
Hi,
I finally found crt1.o also in /usr/lib/x86_64-linux-gnu
Both c++ and g++ worked fine on hello world, but mpicc gave the error
mpicc hw.c
/usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info):
relocation 0 has invalid symbol index 10
/usr/bin/ld: /usr/lib/debug/usr/lib/x86
On Wed, 19 Sep 2012, Cory Ahrens wrote:
> ld: cannot find /usr/lib/crt1.o: No such file or directory
>
> and indeed crt1.o is not there. I can't find it anywhere.
"locate crt1.o" on my Ubuntu 12.04 system finds it in
/usr/lib/x86_64-linux-gnu/
But forget weird system-specific stuff; if "gcc hw.
Hi,
If I follow the steps at
http://stackoverflow.com/questions/6656317/cant-link-a-c-program
and I get the error
ld hw.o /usr/lib/libc.so /usr/lib/crt1.o -o hw
ld: cannot find /usr/lib/crt1.o: No such file or directory
and indeed crt1.o is not there. I can't find it anywhere. However, if I
ju
Please be sure to reply-all so that others may chime in.
Check out this thread:
http://stackoverflow.com/questions/6656317/cant-link-a-c-program
Sounds like your system might've gotten FUBAR'ed. Can you build a simple
hello work program with mpicxx?
---
On Wed, Sep 19, 2012 at 7:53 PM, Cory Ahrens wrote:
>
> I find that
>
> mpicxx points to /usr/bin/mpicxx.mpich2
>
> Not sure where to go from here...
Do an mpicxx -v and then a g++ -v and make sure they output the same
compiler info.
This smells like mpicxx doesn't point to the g++ that's listed below. Can
you double check?
On Wed, Sep 19, 2012 at 6:48 PM, Cory Ahrens wrote:
> Hi,
>
> I updated by libmesh and tried to build it again but I get an error that
> the c++ compiler won't work:
>
> ~/Software/libmesh$ ./configure
>
Hi,
I updated by libmesh and tried to build it again but I get an error that
the c++ compiler won't work:
~/Software/libmesh$ ./configure
-
--- Configuring libMesh -
-
checking for a sed th
18 matches
Mail list logo
