Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Issue preparing a buildroot
Date: Tue, 12 Dec 2006 15:09:25 +0000 (UTC)	[thread overview]
Message-ID: <loom.20061212T155919-203@post.gmane.org> (raw)
In-Reply-To: 1165919607.6628.4.camel@petitemort.i.digital-scurf.org

Daniel Silverstone <dsilvers@...> writes:

> Does anyone here have experience of getting buildroot going on an
> Ubuntu/edgy system, or even experience of resolving such an error?
> 
....
/space/dsilvers/dev-simtec/buildroot-curl-support/
 toolchain_build_i686/uClibc_dev//usr/include/bits/local_lim.h:36:26:
> error: linux/limits.h: No such file or directory
> 
> I hope you can help,
> 
> Thank,
> 
> D.
> 
Well it's often possible to temporarily 'fix' such issues by means of a
symbolic link to the right place; as long as it's limited in scope,
the use of an 'external' limits.h file shouldn't break anything ....?!

I would have thought there was an add-in package that would supply
the missing headers - surely we are not in Windows "hide system files"
territory ?

I don't know whether Ubuntu is missing the entire /linux subdirectory
or just the limits.h file, but just add the minimum required to get past
this obstacle, i.e. don't link to the /linux directory if you can help it,
just create an empty one (if missing) and add a symlink to the
existing limits.h file.

In this way the possible side-effects of using a 'foreign' file are
reduced, and you use as much as possible from the correct toolchain.

The above is *not* from direct Ubuntu experience, but I have made
'enabling' fixups in the manner described to get things to build
before now.

Regards,
Mike

  reply	other threads:[~2006-12-12 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 10:33 [Buildroot] Issue preparing a buildroot Daniel Silverstone
2006-12-12 15:09 ` MikeW [this message]
2006-12-12 15:23   ` Daniel Silverstone
2006-12-12 17:05     ` MikeW

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=loom.20061212T155919-203@post.gmane.org \
    --to=mw_phil@yahoo.co.uk \
    --cc=buildroot@busybox.net \
    /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