This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: verilator on cygwin - unexplained errors


I went into perl -MCPAN -e shell, typed "install SystemC::Parser" and it
installed fine for me...

-- 
Rafael

>-----Original Message-----
>From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of
>Pinhas Krengel
>Sent: Friday, January 30, 2004 11:10 AM
>To: cygwin@cygwin.com
>Subject: Re: verilator on cygwin - unexplained errors
>
>I use the cygwin the perl that came with the cygwin package.
>Attached is the cugwin check -svr
>
>"Igor Pechtchanski" <pechtcha@cs.nyu.edu> wrote in message
>Pine.GSO.4.56.0401301342270.20527@slinky.cs.nyu.edu">news:Pine.GSO.4.56.0401301342270.20527@slinky.cs.nyu.edu...
>> On Fri, 30 Jan 2004, Pinhas Krengel wrote:
>>
>> > While tring to build one of its packeage (from CPAN) I got stange
>> > message in response to the make.
>> >
>> > the package is //www.veripool.com/systemperl.html
>> >
>> > Message is. Can somebody tell me if I am missing something in my cygwin?
>> >
>> > make[1]: Entering directory
>`/cygdrive/c/pini_prog/verilator/SystemPerl-1.147/Parser'
>> >
>gcc -c -I. -DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -DUSEIMPORTLIB -O2 -D
>VERSION=\"1.147\" -DXS_VERSION=\"1.147\"
>"-I/usr/lib/perl5/5.8.2/cygwin-thread-multi-64int/CORE" Parser.c
>> > Running Mkbootstrap for SystemC::Parser ()
>> > chmod 644 Parser.bs
>> > rm -f ../blib/arch/auto/SystemC/Parser/Parser.dll
>> > LD_RUN_PATH="" ld2 -s -L/usr/local/lib Parser.o -o
>../blib/arch/auto/SystemC/Parser/Parser.dll sclex.o scgrammer.o
>/usr/lib/perl5/5.8.2/cygwin-thread-multi-64int/CORE/libperl.dll.a
>> > gcc -shared -o
>Parser.dll -Wl,--out-implib=libParser.dll.a -Wl,--export-all-symbols -Wl,--e
>nable-auto-import -Wl,--stack,8388608 \
>> > -s -L/usr/local/lib Parser.o sclex.o scgrammer.o
>/usr/lib/perl5/5.8.2/cygwin-thread-multi-64int/CORE/libperl.dll.a
>> > Creating library file: libParser.dll.a
>> > sclex.o(.text+0x2f2b):sclex.c: undefined reference to `__imp___iob'
>> > sclex.o(.text+0x2f3e):sclex.c: undefined reference to `__imp___iob'
>> > sclex.o(.text+0x389b):sclex.c: undefined reference to `__assert'
>> > sclex.o(.text+0x43bb):sclex.c: undefined reference to `__imp___iob'
>> > sclex.o(.text+0x444e):sclex.c: undefined reference to `__isctype'
>> > sclex.o(.text+0x4476):sclex.c: undefined reference to `__isctype'
>> > sclex.o(.text+0x44bd):sclex.c: undefined reference to `__isctype'
>> > sclex.o(.text+0x44e9):sclex.c: undefined reference to `__isctype'
>> > sclex.o(.text+0x4538):sclex.c: undefined reference to `__imp___pctype'
>> > sclex.o(.text+0x4551):sclex.c: undefined reference to `__imp___pctype'
>> > sclex.o(.text+0x4569):sclex.c: undefined reference to `__imp___pctype'
>> > sclex.o(.text+0x4581):sclex.c: undefined reference to `__imp___pctype'
>> > scgrammer.o(.text+0x16d6):scgrammer.c: undefined reference to
>`__imp___iob'
>> > scgrammer.o(.text+0x16fa):scgrammer.c: undefined reference to
>`__imp___iob'
>> > scgrammer.o(.text+0x1724):scgrammer.c: undefined reference to
>`__imp___iob'
>> > scgrammer.o(.text+0x179b):scgrammer.c: undefined reference to
>`__imp___iob'
>> > scgrammer.o(.text+0x17de):scgrammer.c: undefined reference to
>`__imp___iob'
>> > scgrammer.o(.text+0x180f):scgrammer.c: more undefined references to
>`__imp___iob' follow
>> > collect2: ld returned 1 exit status
>> > perlld: *** system() failed to execute
>>   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > gcc -shared -o
>Parser.dll -Wl,--out-implib=libParser.dll.a -Wl,--export-all-symbols -Wl,--e
>nable-auto-import -Wl,--stack,8388608 \
>> > -s -L/usr/local/lib Parser.o sclex.o scgrammer.o
>/usr/lib/perl5/5.8.2/cygwin-thread-multi-64int/CORE/libperl.dll.a
>> > make[1]: *** [../blib/arch/auto/SystemC/Parser/Parser.dll] Error 1
>> > make[1]: Leaving directory
>`/cygdrive/c/pini_prog/verilator/SystemPerl-1.147/Parser'
>> > make: *** [subdirs] Error 2
>>
>> Please accompany all Cygwin problem reports with the output of "cygcheck
>> -svr", preferably run from the environment/context in which you get the
>> error.  The output should be attached, as an uncompressed text
>> *attachment*, rather than included inline, as per
>> <http://cygwin.com/problems.html>.
>>
>> The first question that comes to mind after seeing the underlined line
>> above, though, is whether you're using Cygwin's perl or if there's another
>> perl in the PATH that overrides it.
>> Igor
>> --
>> http://cs.nyu.edu/~pechtcha/
>>       |\      _,,,---,,_ pechtcha@cs.nyu.edu
>> ZZZzz /,`.-'`'    -.  ;-;;,_ igor@watson.ibm.com
>>      |,4-  ) )-,_. ,\ (  `'-' Igor Pechtchanski, Ph.D.
>>     '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
>>
>> "I have since come to realize that being between your mentor and his route
>> to the bathroom is a major career booster."  -- Patrick Naughton
>>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]