headers
Dave Yeo | 11 Apr 02:04

Response files

Should GCC and emxomfld accept response files? eg gcc @file or emxomfld 
@file.
We're having a problem with Mozilla where they've changed their build 
system to link all the object files into xul.dll instead of static libs 
and the linking stage ends with g++: error trying to exec 
'emxomfld.exe': execvp: Invalid argument.
A build log is here, 
https://bug648134.bugzilla.mozilla.org/attachment.cgi?id=524988
Dave
Permalink | Reply | 1 comment |
headers
Knut St. Osmundsen | 11 Apr 10:28
Favicon

Re: Response files

Hi Dave,

  looks like g++ accepts it alright but doesn't use a response file  
when invoking the linker. Someone else was running into the same  
problem see http://svn.netlabs.org/libc/ticket/216 - once I've fixed  
that Paul will have to pick up the fixes and apply them to his gcc  
ports.  I will try find time to do that during the easter holidays or  
something, as I hope to finally push out 0.6.4 soon. :-)

Kind Regards,
  knut

On Apr 11, 2011, at 02:04, Dave Yeo wrote:

> Should GCC and emxomfld accept response files? eg gcc @file or  
> emxomfld @file.
> We're having a problem with Mozilla where they've changed their  
> build system to link all the object files into xul.dll instead of  
> static libs and the linking stage ends with g++: error trying to  
> exec 'emxomfld.exe': execvp: Invalid argument.
> A build log is here, https://bug648134.bugzilla.mozilla.org/attachment.cgi?id=524988
> Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: libc-user-unsubscribe <at> netlabs.org
> For additional commands, e-mail: libc-user-help <at> netlabs.org
>
>
Permalink | Reply | 0 comments |
headers
Steven Levine | 20 Apr 05:41
Picon
Favicon

Building libc064x - unexpected undefined externals


Hi,

I'm back to building libc064 from the branch and everything is fine until
it's time to link libc064x.dll.  This fails with are large number of
undefines of the form

weakld: error: Unresolved symbol (UNDEF) '_getlogin'.
weakld: info: The symbol is referenced by:
    I:\sla_dev2\libc-0.6-branch\emx\out\dbg\omf\libc_s.lib(glob.obj)
weakld: error: Unresolved symbol (UNDEF) '_memcmp'.

I have the fixes from ticket #222 installed.  Do I need something else?

The toolchain is gcc445 and ilink, but I'm willing to use something else
if that is required.

FWIW, my build of emxomfld from the branch seems to have issues.  When
building rsync 3.0.8, with gcc 3.5.2, emxomfld fails claiming it can't
find the symbol named ''. Reverting to an older emxomfld resolves the
error.  The failure appears to be specific to a single .o file.  There are
no problems building rsync 3.0.7 which does not differ all that much from
3.0.8.  I'll provide a testcase once I am sure it's not something wrong
with by libc build setup.

Thanks,

Steven

--

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane