i383-elf-gdb build help

Dongsheng Wang dongsheng at gmail.com
Sun Oct 2 05:02:52 PDT 2011


I copied the Portfile from corss/arm-elf-gdb to start. After replaced all
"arm" with "i386", it actually worked all the way to activation. And, it
gave the following error during activation phrase. (I hade arm-elf-gdb
installed already BTW) After I deactivate arm-elf-gdb and try again.
Everything is fine.

What is the right way to fix the problem?

:error:activate Target org.macports.activate returned: Image error:
/opt/local/share/gdb/syscalls/amd64-linux.xml is being used by the active
arm-elf-gdb port.  Please deactivate this port first, or use 'port -f
activate i386-elf-gdb' to force the activation.
:debug:activate Backtrace: Image error:
/opt/local/share/gdb/syscalls/amd64-linux.xml is being used by the active
arm-elf-gdb port.  Please deactivate this port first, or use 'port -f
activate i386-elf-gdb' to force the activation.
    invoked from within
"throw registry::image-error "Image error: $file is being used by the active
[$owner name] port.  Please deactivate this port first, or use 'port -f
ac..."
    ("foreach" body line 45)
    invoked from within
"foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to install links, we test if we can lst..."
    invoked from within
"registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to instal..."
    invoked from within
"try {
        registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be ..."
    (procedure "_activate_contents" line 21)
    invoked from within
"_activate_contents $requested"
    (procedure "portimage::activate" line 57)
    invoked from within
"registry_activate $subport $version $revision $portvariants [array get
user_options]"
    (procedure "portactivate::activate_main" line 4)
    invoked from within
"$procedure $targetname"
:info:activate Warning: the following items did not execute (for
i386-elf-gdb): org.macports.activate
:notice:activate Log for i386-elf-gdb is at:
/opt/local/var/macports/logs/_Users_dwang_ports_cross_i386-elf-gdb/i386-elf-gdb/main.log


ds

On Thu, Sep 29, 2011 at 2:10 PM, Dongsheng Wang <dongsheng at gmail.com> wrote:

> Thanks, Ryan,
>
> Have never done that, but I will give it a try.
>
> ds
>
>
> On Thu, Sep 29, 2011 at 1:21 AM, Ryan Schmidt <ryandesign at macports.org>wrote:
>
>> On Sep 28, 2011, at 14:09, Dongsheng Wang wrote:
>>
>> > It seems i386-elf-gdb port is not available, so I am trying to build it
>> manually, and I got a error for make command.
>> >
>> > ====
>> >
>> > In file included from ../../gdb-7.3.1/bfd/archive.c:130:
>> > ../../gdb-7.3.1/bfd/sysdep.h:173:21: error: libintl.h: No such file or
>> directory
>> > cc1: warnings being treated as errors
>> > ../../gdb-7.3.1/bfd/archive.c: In function
>> ‘_bfd_write_archive_contents’:
>> > ../../gdb-7.3.1/bfd/archive.c:2126: warning: implicit declaration of
>> function ‘dgettext’
>> > ../../gdb-7.3.1/bfd/archive.c:2126: warning: incompatible implicit
>> declaration of built-in function ‘dgettext’
>> > ../../gdb-7.3.1/bfd/archive.c: In function
>> ‘_bfd_archive_bsd_update_armap_timestamp’:
>> > ../../gdb-7.3.1/bfd/archive.c:2414: warning: incompatible implicit
>> declaration of built-in function ‘dgettext’
>> > ../../gdb-7.3.1/bfd/archive.c:2438: warning: incompatible implicit
>> declaration of built-in function ‘dgettext’
>> > make[4]: *** [archive.lo] Error 1
>> > make[3]: *** [all-recursive] Error 1
>> > make[2]: *** [all] Error 2
>> > make[1]: *** [all-bfd] Error 2
>> > make: *** [all] Error 2
>> >
>> > ====
>> >
>> > These are the command I used.
>> >
>> >     ../gdb-7.3.1/configure --target=i386-elf --program-prefix=i386-elf-
>> --prefix=/opt/local --with-build-libsubdir=/opt/local 2>&1 | tee
>> configure.log
>> >     make 2>&1 | tee make.log
>> >
>> > I am pretty sure libintl.h is available under /opt/local/include.
>> >
>> > Can someone give me some hints what is wrong?
>>
>> Did you set CFLAGS, CPPFLAGS, CXXFLAGS, LDFLAGS, CPATH, LIBRARY_PATH the
>> same as MacPorts sets them? Consult most any port's main.log.
>>
>> Instead of trying to build by hand, you may want to try to create a
>> portfile. You can base it on the existing cross gdb ports. This way you
>> don't have to worry about manually setting the environment variables. And
>> when you succeed, the portfile will be all done and you can submit it to us
>> for inclusion.
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20111002/692de316/attachment.html>


More information about the macports-users mailing list