Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Build Issue - lttng-modules - cross compiling for MIPSEL - syscall.h
Date: Mon, 18 Nov 2013 16:32:17 +0000 (UTC)	[thread overview]
Message-ID: <343869476.70337.1384792337904.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAP0pN0v_xaC8iZ=mDwGCbWtfyhGQ7TCsnBmXy+qXtTFUKjmKpQ@mail.gmail.com>

If you don't want this issue to be lost, please open a bug report against lttng-modules on bugs.lttng.org will all the relevant info (kernel version, lttng-modules version, .config, how to reproduce, bug detail) 

Thanks. 

Mathieu 

----- Original Message -----

> From: "Shreyas Joshi" <shreyasjoshi11@gmail.com>
> To: "Mathieu Desnoyers" <mathieu.desnoyers at efficios.com>
> Cc: "Ralf Baechle" <ralf at linux-mips.org>, lttng-dev at lists.lttng.org
> Sent: Wednesday, November 13, 2013 1:00:38 AM
> Subject: Re: [lttng-dev] Build Issue - lttng-modules - cross compiling for
> MIPSEL - syscall.h

> Thanks! I am using kernel version - 3.3.8-2.4. I have attached the
> configuration here.
> The lttng-module version used is 2.3.0. Please do help me.

> Thanks & regards,
> Shreyas Joshi

> On Wed, Nov 13, 2013 at 1:14 AM, Mathieu Desnoyers <
> mathieu.desnoyers at efficios.com > wrote:

> > > From: "Shreyas Joshi" < shreyasjoshi11@gmail.com >
> > 
> 
> > > To: lttng-dev at lists.lttng.org
> > 
> 
> > > Sent: Friday, November 8, 2013 2:11:55 AM
> > 
> 
> > > Subject: [lttng-dev] Build Issue - lttng-modules - cross compiling for
> > > MIPSEL
> > > - syscall.h
> > 
> 

> > > Hi,
> > 
> 

> > > As you are aware that in mips linux there is no such file called -
> > 
> 

> > > #include <asm/syscall.h>
> > 
> 

> > > If I comment this line, then it get the issue for this function -
> > 
> 

> > > error: implicit declaration of function 'syscall_get_arguments'
> > 
> 

> > > It cannot find the syscall_get_arguments. Do you support lttng-modules
> > > for
> > > mips platform?
> > 
> 
> > > Is there any patch for it? I am stuck at the moment. Any help will be
> > > much
> > > appreciated.
> > 
> 

> > Adding Ralf Baechle who contributed the MIPS system call support.
> 

> > What kernel version are you building against ? Can we have a copy of your
> > .config file ?
> 

> > What lttng-modules version are you using ?
> 

> > Thanks,
> 

> > Mathieu
> 

> > > --
> > 
> 
> > > Thanks & regards
> > 
> 

> > > Shreyas Joshi
> > 
> 

> > > _______________________________________________
> > 
> 
> > > lttng-dev mailing list
> > 
> 
> > > lttng-dev at lists.lttng.org
> > 
> 
> > > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> > 
> 

> > --
> 
> > Mathieu Desnoyers
> 
> > EfficiOS Inc.
> 
> > http://www.efficios.com
> 

> --
> Thanks & regards

> Shreyas Joshi

-- 
Mathieu Desnoyers 
EfficiOS Inc. 
http://www.efficios.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20131118/bb3139ad/attachment.html>


      reply	other threads:[~2013-11-18 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  7:11 Shreyas Joshi
2013-11-12 19:44 ` Mathieu Desnoyers
2013-11-13  6:00   ` Shreyas Joshi
2013-11-18 16:32     ` Mathieu Desnoyers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=343869476.70337.1384792337904.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox