[MacPorts] #39135: libstdcxx @4.8-20130411_0: i386 build failure on 10.8.3

[MacPorts]

#39135: libstdcxx @4.8-20130411_0: i386 build failure on 10.8.3
--------------------------+-------------------
  Reporter:  d.schreij@…  |      Owner:  mww@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.1.3
Resolution:               |   Keywords:
      Port:  libstdcxx    |
--------------------------+-------------------

Comment (by d.schreij@…):

 Replying to [comment:9 larryv@…]:
 > The clang++ invocations are not respecting `build_arch`, which is why
 “the architecture being linked” is x86_64.
 > {{{
 > :info:build /usr/bin/clang++   -pipe -O2 -DIN_GCC   -fno-exceptions
 -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-
 strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long
 -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H
 -DGENERATOR_FILE -L/opt/local/lib -o build/genhooks \
 > :info:build       build/genhooks.o build/errors.o ../build-i386-apple-
 darwin12/libiberty/libiberty.a
 > :info:build ld: warning: ignoring file ../build-i386-apple-
 darwin12/libiberty/libiberty.a, file was built for archive which is not
 the architecture being linked (x86_64): ../build-i386-apple-
 darwin12/libiberty/libiberty.a
 > }}}

 I had that feeling. Can I pass some flags to the build command, or does
 this have to be solved inside macports?

-- 
Ticket URL: <https://trac.macports.org/ticket/39135#comment:11>
MacPorts <http://www.macports.org/>
Ports system for OS X