Displaying 6 results from an estimated 6 matches for "import_object".
2017 Jul 18
2
LNT on pypy and documentation build
...cs/profiles.rst:101: WARNING: autodoc: failed to import class 'ProfileImpl' from module 'lnt.testing.profile.profile'; the following exception was raised:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/site-packages/sphinx/ext/autodoc.py", line 551, in import_object
__import__(self.modname)
File "/Users/mbraun/dev/lnt/lnt/testing/profile/__init__.py", line 3, in <module>
from profilev1impl import ProfileV1
ImportError: No module named 'profilev1impl'
/Users/mbraun/dev/lnt/docs/profiles.rst:106: WARNING: autodoc: failed to impo...
2017 Jul 18
2
LNT on pypy and documentation build
...doc: failed to
> import class 'ProfileImpl' from module 'lnt.testing.profile.profile'; the
> following exception was raised:
> > Traceback (most recent call last):
> > File "/usr/local/lib/python3.5/site-packages/sphinx/ext/autodoc.py",
> line 551, in import_object
> > __import__(self.modname)
> > File "/Users/mbraun/dev/lnt/lnt/testing/profile/__init__.py", line 3,
> in <module>
> > from profilev1impl import ProfileV1
> > ImportError: No module named 'profilev1impl'
> > /Users/mbraun/dev/lnt/doc...
2017 Jul 18
2
LNT on pypy and documentation build
...G: autodoc: failed to import class 'ProfileImpl' from module 'lnt.testing.profile.profile'; the following exception was raised:
>> > Traceback (most recent call last):
>> > File "/usr/local/lib/python3.5/site-packages/sphinx/ext/autodoc.py", line 551, in import_object
>> > __import__(self.modname)
>> > File "/Users/mbraun/dev/lnt/lnt/testing/profile/__init__.py", line 3, in <module>
>> > from profilev1impl import ProfileV1
>> > ImportError: No module named 'profilev1impl'
>> > /Users/mbr...
2015 Jul 25
0
[LLVMdev] [LLD] support for dlltool generated libs in COFF/PECOFF
...o that lld gives me
link errors and then resolve those errors to create an exe.
This is one thing that is still missing that sticks out like a sore thumb
In the actual imports of the functions the objects are very different
As you can see lib.exe generates a very simple function import object.
IMPORT_OBJECT[1-N]
-> contains an IMPORT_OBJECT_HEADER and DATA
data example -> _MessageBoxA.USER32.dll
dlltool however doesn't create an import object but infact has a complete
IMAGE_FILE
IMPORT_OBJECT[1-N]
-> contains an IMAGE_FILE_HEADER and is a full object with SECTIONS
the...
2015 Jul 24
2
[LLVMdev] [LLD] support for dlltool generated libs in COFF/PECOFF
After some more digging and creating a few testcases in lld I have narrowed
it down to
The fact that dlltool generates
Contents of section .idata$7:
0000 55534552 33322e64 6c6c0000 USER32.dll..
Where as lld expects
Contents of section .idata$6:
0000 55534552 33322e64 6c6c0000 USER32.dll..
I recreated the hello64.test using dlltool for the lib and here is the
asm dump of
2015 Jul 25
2
[LLVMdev] [LLD] support for dlltool generated libs in COFF/PECOFF
...and then resolve those errors to create an exe.
>
> This is one thing that is still missing that sticks out like a sore thumb
> In the actual imports of the functions the objects are very different
>
> As you can see lib.exe generates a very simple function import object.
>
> IMPORT_OBJECT[1-N]
> -> contains an IMPORT_OBJECT_HEADER and DATA
> data example -> _MessageBoxA.USER32.dll
>
> dlltool however doesn't create an import object but infact has a complete
> IMAGE_FILE
>
> IMPORT_OBJECT[1-N]
> -> contains an IMAGE_FILE_HEADER and i...