I built google perftools 2.0 in Macbook pro (OS X 10.6.8), and tried
to build my application with -lprofile as a linker option. There's a
warning message saying "ld: warning: ignoring file /Developer/SDKs/
MacOSX10.5.sdk/usr/local/lib/libprofiler.dylib, file was built for
unsupported file format which is not the architecture being linked
(i386)
".
I checked the perftools configure.log, and saw the line "uname -m =
i386". Seems it configured the system right.
In my linux machine, I saw no problem like this.
Any insights?
On Thu, May 3, 2012 at 2:22 AM, Kevin Ma <k...@webrtc.org> wrote:
> I built google perftools 2.0 in Macbook pro (OS X 10.6.8), and tried
> to build my application with -lprofile as a linker option. There's a
> warning message saying "ld: warning: ignoring file /Developer/SDKs/
> MacOSX10.5.sdk/usr/local/lib/libprofiler.dylib, file was built for
> unsupported file format which is not the architecture being linked
> (i386)
> ".
> I checked the perftools configure.log, and saw the line "uname -m =
> i386". Seems it configured the system right.
> In my linux machine, I saw no problem like this.
> Any insights?
> --
> You received this message because you are subscribed to the Google Groups "google-perftools" group.
> To post to this group, send email to google-perftools@googlegroups.com.
> To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-perftools?hl=en.
I think so. The library at that location is the same binary as what I
built from the source (/opt/gperftools-2.0/.libs/libprofiler.0.dylib).
I also tried to replace the link option "-lprofiler" with "/opt/
gperftools-2.0/.libs/libprofiler.dylib" directly and got the same
warning.
On May 3, 5:04 am, David Chappelle <chapp...@gmail.com> wrote:
> Are you sure that the linker is finding the right library? The file it
> is complaining about seems to be in a non-standard location.
> On Thu, May 3, 2012 at 2:22 AM, Kevin Ma <k...@webrtc.org> wrote:
> > I built google perftools 2.0 in Macbook pro (OS X 10.6.8), and tried
> > to build my application with -lprofile as a linker option. There's a
> > warning message saying "ld: warning: ignoring file /Developer/SDKs/
> > MacOSX10.5.sdk/usr/local/lib/libprofiler.dylib, file was built for
> > unsupported file format which is not the architecture being linked
> > (i386)
> > ".
> > I checked the perftools configure.log, and saw the line "uname -m =
> > i386". Seems it configured the system right.
> > In my linux machine, I saw no problem like this.
> > Any insights?
> > --
> > You received this message because you are subscribed to the Google Groups "google-perftools" group.
> > To post to this group, send email to google-perftools@googlegroups.com.
> > To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/google-perftools?hl=en.
The only other thing I can think of is to make sure that the same
compiler is being used to build both gperftools and the executable
that you are building. Other than that you can try statically linking.
On Thu, May 3, 2012 at 1:06 PM, Kevin Ma <k...@webrtc.org> wrote:
> I think so. The library at that location is the same binary as what I
> built from the source (/opt/gperftools-2.0/.libs/libprofiler.0.dylib).
> I also tried to replace the link option "-lprofiler" with "/opt/
> gperftools-2.0/.libs/libprofiler.dylib" directly and got the same
> warning.
> On May 3, 5:04 am, David Chappelle <chapp...@gmail.com> wrote:
>> Are you sure that the linker is finding the right library? The file it
>> is complaining about seems to be in a non-standard location.
>> On Thu, May 3, 2012 at 2:22 AM, Kevin Ma <k...@webrtc.org> wrote:
>> > I built google perftools 2.0 in Macbook pro (OS X 10.6.8), and tried
>> > to build my application with -lprofile as a linker option. There's a
>> > warning message saying "ld: warning: ignoring file /Developer/SDKs/
>> > MacOSX10.5.sdk/usr/local/lib/libprofiler.dylib, file was built for
>> > unsupported file format which is not the architecture being linked
>> > (i386)
>> > ".
>> > I checked the perftools configure.log, and saw the line "uname -m =
>> > i386". Seems it configured the system right.
>> > In my linux machine, I saw no problem like this.
>> > Any insights?
>> > --
>> > You received this message because you are subscribed to the Google Groups "google-perftools" group.
>> > To post to this group, send email to google-perftools@googlegroups.com.
>> > To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
>> > For more options, visit this group athttp://groups.google.com/group/google-perftools?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "google-perftools" group.
> To post to this group, send email to google-perftools@googlegroups.com.
> To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-perftools?hl=en.
Also wanted to point out this article which seems to implicate that
the target architecture that gperftools is selecting is incorrect. You
can control this with extra arguments to configure.
On Thu, May 3, 2012 at 1:23 PM, David Chappelle <chapp...@gmail.com> wrote:
> The only other thing I can think of is to make sure that the same
> compiler is being used to build both gperftools and the executable
> that you are building. Other than that you can try statically linking.
> On Thu, May 3, 2012 at 1:06 PM, Kevin Ma <k...@webrtc.org> wrote:
>> I think so. The library at that location is the same binary as what I
>> built from the source (/opt/gperftools-2.0/.libs/libprofiler.0.dylib).
>> I also tried to replace the link option "-lprofiler" with "/opt/
>> gperftools-2.0/.libs/libprofiler.dylib" directly and got the same
>> warning.
>> On May 3, 5:04 am, David Chappelle <chapp...@gmail.com> wrote:
>>> Are you sure that the linker is finding the right library? The file it
>>> is complaining about seems to be in a non-standard location.
>>> On Thu, May 3, 2012 at 2:22 AM, Kevin Ma <k...@webrtc.org> wrote:
>>> > I built google perftools 2.0 in Macbook pro (OS X 10.6.8), and tried
>>> > to build my application with -lprofile as a linker option. There's a
>>> > warning message saying "ld: warning: ignoring file /Developer/SDKs/
>>> > MacOSX10.5.sdk/usr/local/lib/libprofiler.dylib, file was built for
>>> > unsupported file format which is not the architecture being linked
>>> > (i386)
>>> > ".
>>> > I checked the perftools configure.log, and saw the line "uname -m =
>>> > i386". Seems it configured the system right.
>>> > In my linux machine, I saw no problem like this.
>>> > Any insights?
>>> > --
>>> > You received this message because you are subscribed to the Google Groups "google-perftools" group.
>>> > To post to this group, send email to google-perftools@googlegroups.com.
>>> > To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
>>> > For more options, visit this group athttp://groups.google.com/group/google-perftools?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups "google-perftools" group.
>> To post to this group, send email to google-perftools@googlegroups.com.
>> To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/google-perftools?hl=en.
> Also wanted to point out this article which seems to implicate that
> the target architecture that gperftools is selecting is incorrect. You
> can control this with extra arguments to configure.
> On Thu, May 3, 2012 at 1:23 PM, David Chappelle <chapp...@gmail.com> wrote:
> > The only other thing I can think of is to make sure that the same
> > compiler is being used to build both gperftools and the executable
> > that you are building. Other than that you can try statically linking.
> > On Thu, May 3, 2012 at 1:06 PM, Kevin Ma <k...@webrtc.org> wrote:
> >> I think so. The library at that location is the same binary as what I
> >> built from the source (/opt/gperftools-2.0/.libs/libprofiler.0.dylib).
> >> I also tried to replace the link option "-lprofiler" with "/opt/
> >> gperftools-2.0/.libs/libprofiler.dylib" directly and got the same
> >> warning.
> >> On May 3, 5:04 am, David Chappelle <chapp...@gmail.com> wrote:
> >>> Are you sure that the linker is finding the right library? The file it
> >>> is complaining about seems to be in a non-standard location.
> >>> On Thu, May 3, 2012 at 2:22 AM, Kevin Ma <k...@webrtc.org> wrote:
> >>> > I built google perftools 2.0 in Macbook pro (OS X 10.6.8), and tried
> >>> > to build my application with -lprofile as a linker option. There's a
> >>> > warning message saying "ld: warning: ignoring file /Developer/SDKs/
> >>> > MacOSX10.5.sdk/usr/local/lib/libprofiler.dylib, file was built for
> >>> > unsupported file format which is not the architecture being linked
> >>> > (i386)
> >>> > ".
> >>> > I checked the perftools configure.log, and saw the line "uname -m =
> >>> > i386". Seems it configured the system right.
> >>> > In my linux machine, I saw no problem like this.
> >>> > Any insights?
> >>> > --
> >>> > You received this message because you are subscribed to the Google Groups "google-perftools" group.
> >>> > To post to this group, send email to google-perftools@googlegroups.com.
> >>> > To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
> >>> > For more options, visit this group athttp://groups.google.com/group/google-perftools?hl=en.
> >> --
> >> You received this message because you are subscribed to the Google Groups "google-perftools" group.
> >> To post to this group, send email to google-perftools@googlegroups.com.
> >> To unsubscribe from this group, send email to google-perftools+unsubscribe@googlegroups.com.
> >> For more options, visit this group athttp://groups.google.com/group/google-perftools?hl=en.
