Date: Mon, 9 Sep 2002 13:52:37 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: martin.kahlert@infineon.com Cc: freebsd-questions@FreeBSD.org Subject: Re: first icc did not start, now it does not stop... Message-ID: <20020909135237.4094feff.Alexander@Leidinger.net> In-Reply-To: <20020909085912.A10105@keksy.muc.infineon.com> References: <20020903081616.A12893@keksy.muc.infineon.com> <20020903151528.GB77952@xor.obsecurity.org> <20020903185957.301810ec.Alexander@Leidinger.net> <20020904083415.A5569@keksy.muc.infineon.com> <20020904161734.2f264cd1.Alexander@Leidinger.net> <20020909085912.A10105@keksy.muc.infineon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Sep 2002 08:59:12 +0200 Martin Kahlert
<martin.kahlert@infineon.com> wrote:
> > > I do not understand, how Linux compatibility works in FreeBSD:
> > > How does the runtime linker know that the executable is a Linux
> > > executable and translate /lib/libc* into /compat/linux/libc*?
> >
> > man brandelf
> And vi `which icc` ;-) This explicitly sets PATH/LD_LIBRARY_PATH.
Only if you have an empty one, else it prepends the bin and lib dir to
the existing value.
> > > Alexander, did you set LM_LICENSE_FILE to anything?
> >
> > No. Just put it into /usr/local/intel/licenses/, mine is name
> > l_cpp_<some_numbers>.lic. 'file' says it's a 'RiscOS PackdDir
> > archive'.
> Mine is a simple ASCII text file.
Mine too, but file thinks it's an RiscOS PackdDir archive.
> Did you add an additional SERVER and/or DAEMON line to the license
> file? If not, how do you start lmgrd.intel?
No, I haven't, and I don't start lmgrd.intel. I just installed my port
and run icc (with the apropriate license).
> > > BTW: What is FreeBSD's equivalent command to Linux's strace -f?
> > man ktrace
> Thanks a lot. BTW: What do the 'NAMI' lines mean? Looks like name info
> but from what?
Files to open (not neccessary by open(2)).
> Here is what i tried:
> - I exported LD_LIBRRAY_PATH/PATH as in the icc shell script.
> - i started
> ktrace -d -i iccbin -E t.c
> kdump > dmp
>
> I append the file dmp. As far as i can tell, the compiler never reads
> t.c! It loops somewhere before that.
I think it opens it from /tmp.
> I checked something else:
> gcc -c t.c
> icc -o t t.o
> This works fine.
Your test also works fine here with icc.
> The problem seems to be the C preprocessor.
> But as my t.c file does not even need it, it is not a header problem.
> mcpcom just continues looping :-(
I don't have a glue what to check now... maybe recompiling the
world/kernel without additional optimizations if you use further
optimization flags in /etc/make.conf, or compiling it with optimizations
if it is compiled with the default options.
I assume you reinstalled the new linux-base (7.1) with a clean
/compat/linux. If you haven't done that, you should deinstall every
linux port and make sure, your /compat/linux is empty.
Bye,
Alexander.
--
Secret hacker rule #11: hackers read manuals.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020909135237.4094feff.Alexander>